Closing the Visibility Gap
In the previous module, you successfully deployed a new custom field to Salesforce using Cursor. However, in the world of Salesforce metadata, existence does not equal visibility. If you log into your org right now, you likely won't see your field on the record page. This is because Salesforce follows a 'secure by default' model where new fields created via API/CLI often lack Field-Level Security (FLS) permissions and are not automatically assigned to Page Layouts.
Agentic Debugging vs. Manual Toggling
Instead of hunting through the Setup Menu to find the right checkbox, we use Cursor to inspect the metadata dependencies. To make a field usable, we must address two primary blockers:
- Permissions: Ensuring the Admin or SE profile has 'Edit' and 'Read' access in the Profile or Permission Set metadata.
- Layout Assignment: Identifying which specific Page Layout is being utilized by the application you are demoing (e.g., the Service Console) and programmatically inserting the field into the XML definition.
By using Cursor to 'read' the app configuration, we can determine exactly which layout needs modification without guessing or clicking through every layout in the Object Manager.