Rapid Field Creator
Design, validate, and deploy batches of custom fields, complex picklists, and Field-Level Security (FLS) to any Salesforce org in seconds—without ever touching the standard Setup wizard.
⚡ 1. Overview & Architecture
In standard Salesforce Setup, adding a single custom field requires navigating through 6 distinct setup pages: Field Type, Field Details, Profile FLS, Page Layout assignments, and final Confirmation. When onboarding a new project, adding 15–30 custom fields can take hours of tedious, error-prone clicking.
Rapid Field Creator replaces that clunky workflow with a unified, high-density spreadsheet-like matrix. You define field labels, API names, data types, lengths, help texts, and picklist definitions in one view, set your FLS across Profiles and Permission Sets in 1 click, and deploy directly into your org using the Salesforce Tooling API.
How the Deployment Pipeline Operates
- Describe Cache: Inspects the target object describe definition to ensure no API name collisions exist.
- Payload Generation: Compiles valid Tooling API
CustomFieldmetadata objects with correct casing and types. - Atomic Deployment: Submits REST requests to
/services/data/v62.0/tooling/sobjects/CustomField. - Batch FLS Assignment: Creates or updates
FieldPermissionsrecords for selected Profiles and Permission Sets.
🎯 2. Target SObject Selection
Rapid Field Creator works across any object type supported by the Tooling API. In the header search bar, you can quickly filter by typing either the SObject label or API name:
| Target Object Category | Examples | Suffix / Identifier | Tooling API Support |
|---|---|---|---|
| Standard Objects | Account, Contact, Opportunity, Case, Lead |
None | Full (Custom fields created with __c) |
| Custom Objects | Invoice__c, Project_Milestone__c, Audit_Log__c |
__c |
Full custom fields supported |
| Custom Metadata Types | Integration_Setting__mdt, Feature_Flag__mdt |
__mdt |
Supported (Metadata types only allow Text, Checkbox, Long Text, Picklist, etc.) |
🛠️ 3. Supported 14 Field Types & Parameters
Every custom field type available in the Salesforce Platform is supported with strict client-side validation before the Tooling API request is sent:
| Field Type | Tooling API Type | Required Parameters | Default Constraints & Limits |
|---|---|---|---|
| Text | Text |
Length (1–255) | Optional: Unique, External ID, Case Insensitive |
| Text Area | TextArea |
None | Standard 255-character single-line text area |
| Long Text Area | LongTextArea |
Length (256–131,072), Visible Lines | Supports rich plain-text multi-line storage |
| Rich Text Area | Html |
Length (256–131,072), Visible Lines | Formatted HTML with embedded image support |
| Number | Number |
Precision (1–18), Scale (0–17) | Sum of Precision + Scale must not exceed 18 |
| Currency | Currency |
Precision (1–18), Scale (0–17) | Formatted with org currency symbol |
| Percent | Percent |
Precision (1–18), Scale (0–17) | Automated percentage multiplication handling |
| Date | Date |
None | Standard ISO-8601 calendar date (YYYY-MM-DD) |
| Date / Time | DateTime |
None | UTC timestamp with user timezone conversion |
| Checkbox | Checkbox |
Default Value (true / false) |
Boolean indicator, non-nullable in SOQL |
Email |
None | Strict RFC-compliant email address validation | |
| Phone | Phone |
None | International phone number formatting |
| URL | Url |
None | Up to 255-character web hyperlink |
| Picklist & Multi-Picklist | Picklist / MultiselectPicklist |
Values List or Global Value Set | Alphabetical sort, default value flag, strict restriction |
| Lookup Relationship | Lookup |
Reference To (Target Object), Child Relationship Name | Cascade delete constraint: Don't allow / Clear value |
📋 4. Bulk Picklists & CSV Import
Manually typing out 50 state names, 100 country codes, or industry categories in standard Salesforce Setup is painful. In Rapid Field Creator, you can define picklists in two ultra-fast ways:
Option A: Quick Multi-Line Paste
Click the picklist values editor and simply paste your values line-by-line. SF Lens Pro automatically sanitizes each entry, escapes invalid characters, and infers API names.
Option B: Bulk CSV File Import
Upload a structured CSV file with custom API names, default values, and display labels:
# Sample Picklist Import CSV (picklist-values.csv)
Label,API Name,IsDefault,IsActive
Tier 1 - Strategic,Tier_1_Strategic,true,true
Tier 2 - Enterprise,Tier_2_Enterprise,false,true
Tier 3 - Mid-Market,Tier_3_Mid_Market,false,true
Tier 4 - Emerging,Tier_4_Emerging,false,trueRegion_Codes), you can select "Use Global Value Set" to bind the new field without duplicating values across multiple objects.
🛡️ 5. Profile & Permission Set FLS Matrix
A common frustration with field creation is forgetting to assign Field-Level Security, leaving new fields invisible to users. Rapid Field Creator includes a built-in FLS matrix drawer:
1-Click FLS Quick Actions
- Grant All (Read & Edit): Enables full read and edit visibility across all active Profiles and Permission Sets.
- Admin Only: Restricts read and edit access strictly to System Administrators, leaving end-user profiles blank for staging.
- Read-Only for All: Grants read access to all users while keeping edit permissions restricted.
- Permission Set First (Spring '25 Ready): Automatically sets FLS on designated Permission Sets instead of legacy Profiles, adhering to Salesforce's latest end-of-life roadmap for profile permissions.
🚀 6. Tooling API Deployment Pipeline
Once your field definitions and FLS assignments pass client validation, clicking "Deploy Fields" triggers the deployment pipeline.
Under the hood, SF Lens Pro constructs the official Tooling API payload:
// Tooling API CustomField Payload Generated Client-Side
{
"FullName": "Opportunity.Customer_ARR__c",
"Metadata": {
"label": "Customer ARR",
"type": "Currency",
"precision": 18,
"scale": 2,
"required": false,
"inlineHelpText": "Annual recurring revenue calculated from active subscriptions.",
"description": "Created via SF Lens Pro Rapid Field Creator"
}
}During deployment, each field card displays a live status badge:
⚠️ 7. Common Deployment Errors & Solutions
"An object or field with this developer name already exists on this SObject."
Solution: The field API name is already registered (even if hidden from your page layout). Choose a distinct API name or inspect the SObject via Metadata Explorer to see deleted fields awaiting hard deletion.
"Precision must be between 1 and 18, and Scale must not exceed Precision."
Solution: Check your Number/Currency fields. If Precision is 16, Scale can be at most 2. Precision represents total digits including decimals.
"You do not have permission to modify custom fields on this object."
Solution: Ensure your logged-in user has the
Customize Application system permission enabled.
"The maximum number of custom fields for this object has been reached."
Solution: Salesforce limits custom fields per object (typically 100 for Developer Edition, 500 for Enterprise, 800 for Unlimited). Use SF Lens Pro Org Limits to audit your current allocation.
🌟 8. Pro Tips & Best Practices
Export Data Dictionary
Immediately after deployment, open the Metadata Explorer tab and click "Export Data Dictionary" to generate a complete, formatted Excel/CSV inventory of all fields.
Sandbox First
Always test complex schema refactors and picklist structures in a Scratch Org or Sandbox before deploying to Production to avoid naming conflicts with downstream packages.
External IDs for ETL
When importing legacy system keys, check "External ID" and "Unique" directly in the matrix to index the field for ultra-fast SOQL queries and UPSERT operations.
Ready to Explore More Superpowers?
Discover how SF Lens Pro gives you instant Anonymous Apex execution, deep Call Tree debug inspection, and Clayton-class code scanning.