5 items
Bulk create Salesforce custom fields from CSV/XLSX (session-based). 🚀 FieldForge – Bulk Salesforce Field Deployment (Safe, Transparent, Developer-First) Creating custom fields in Salesforce should not feel repetitive, risky, or slow. FieldForge is a developer-focused Chrome Extension that allows you to bulk-create Salesforce custom fields from structured CSV or XLSX files — with strong validation, metadata transparency, and production safety controls built in. Whether you're building a new data model, implementing a feature branch, or preparing a large object refactor, FieldForge helps you move faster without sacrificing control. 🔧 What FieldForge Does FieldForge allows you to: • Upload a CSV or Excel file containing field definitions • Preview and edit fields in a clean, inline table UI • Validate fields locally and against the connected org • Generate Salesforce Metadata format files automatically • Deploy fields safely using the Metadata API • View generated metadata XML before deploying • Download the deploy ZIP package • Monitor deployment progress with structured logs No command line. No SFDX setup. No OAuth flows. No Connected App configuration. Just open a Salesforce org tab and start working. ⚡ Why Install FieldForge? 1️⃣ Save Hours of Manual Work Creating dozens of fields through Salesforce Setup is slow and repetitive. FieldForge lets you define your fields once in a structured file and deploy them in bulk. Perfect for: • New object builds • Large feature implementations • Data model refactors • Sandbox setup • QA org replication • Client onboarding 2️⃣ Safer Than Manual Setup FieldForge includes multiple safety layers: • Local validation (required fields, type constraints, formatting rules) • Org-side validation (object existence, field conflicts) • Production safety confirmation • Hard deploy locking (prevents double-click race conditions) • Relationship type guardrails Before anything is deployed, you see exactly what will happen. 3️⃣ Full Transparency FieldForge is not a black box. You can: • View the exact metadata XML that will be deployed • Download the generated ZIP package • Inspect logs step-by-step during deployment This makes it suitable for developers who care about correctness and clarity. 4️⃣ Built for Developers FieldForge is designed specifically for Salesforce developers: • Expandable row editing • Inline issue feedback • Object API autocomplete • Workflow stepper (Connected → Parsed → Validated → Deployed) • Dark / Light theme toggle • Clear deployment logs This is not a simplified admin tool. It is a developer productivity tool. 5️⃣ No OAuth. No Credential Storage. FieldForge does not require: • Connected Apps • OAuth token storage • Username/password storage The extension binds to the active Salesforce tab session context. This reduces setup friction and avoids credential handling complexity. 6️⃣ Production-Aware by Design If connected to a non-sandbox org, FieldForge requires explicit confirmation before deployment. You must type a confirmation phrase before proceeding. Accidental production deployments are prevented by design. 🛡 Privacy & Security FieldForge: • Does not collect personal data • Does not send your metadata to external servers • Does not store Salesforce credentials • Does not transmit your files outside your browser • Operates locally within the extension environment Metadata packaging and validation occur locally. Deployment calls go directly to your connected Salesforce org. 📦 Supported Field Types FieldForge supports common custom field types including: • Text • Number (with precision/scale validation) • Long Text Area • Picklist (with value checks) • Lookup / Master-Detail (Metadata API only) Tooling API fallback mode is available with safe restrictions. 🧠 Smart Validation FieldForge validates: • Required columns • Field API format • Type-specific constraints • Picklist structure • Number precision/scale limits • Object existence • Existing field conflicts You see issues directly in the preview table before deployment. 📊 Deployment Flow Upload CSV/XLSX Preview & edit Validate Deploy using Metadata API Monitor progress Review logs The extension polls deployment status and reports progress until complete. 🎨 Clean, Modern Interface • Dark mode default • Light theme toggle • Theme-aware buttons • Compact table layout • Expandable row editor • Structured deployment logs • Toast notifications with sanitization Built to feel like a modern developer SaaS tool — inside your browser. 🌍 Open Source FieldForge is open-source and built transparently. You can inspect the code, understand how metadata is generated, and contribute improvements. 👥 Who Is This For? FieldForge is ideal for: • Salesforce developers • Technical consultants • Implementation teams • QA engineers • Data model designers If you frequently create multiple fields at once, this tool will save you time and reduce risk. 🚀 Why FieldForge Instead of SFDX? FieldForge is not meant to replace your CI/CD pipeline. It is designed for: • Fast iteration • Sandbox prototyping • Client sessions • Proof of concept work • Visual inspection of metadata Think of it as a deployment companion — not a replacement for your DevOps process. 🔒 Safe. Transparent. Fast. FieldForge gives you the speed of bulk creation with the safety of explicit confirmation and the clarity of metadata transparency. No hidden magic. No credential storage. No remote servers. Just clean metadata deployment. Install FieldForge and build smarter.
Feb 25, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.