The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Builder Central turns a requirements prompt into a working Salesforce app (opens in a new tab)

You will learn how Builder Central plans and builds a Custom Object, List View and Permission Set from a plain-language prompt, what it leaves for the Admin to finish, and how it fits beside Lightning App Builder and Flow Builder.

  1. Describe the app in a prompt
  2. Review the project plan
  3. Build in a separate workspace
  4. Publish to the org
  5. Assign the Permission Set
The order in which Builder Central moved the Bulk Delivery Management app from prompt to live use

The author tested Builder Central, a beta conversational workspace for planning, building, previewing and deploying Salesforce apps and agents from plain language. He described a spreadsheet replacement app in one prompt, naming a Custom Object and its fields, and Builder Central first produced a project plan for review before building anything in its own separate workspace.

After the initial build it suggested extra customization, such as a List View, which he accepted. He published the app, asked Builder Central to assign the Permission Set to his user, and then opened the app from the App Launcher. The build took about 12 minutes in real time, though he sped up parts of the video.

The result was not complete: the record page did not show all fields, so he adjusted it in Lightning App Builder. He argues the change matters less for saving time than for shortening the loop between requirements meetings and a working prototype, while Admins still own permissions, automation, user experience and testing. He recommends trying it in a sandbox, recreating an existing app conversationally, and checking the beta limitations.

Read the original at Salesforce Admins Blog (opens in a new tab)

Worth reading?

Six practical Validation Rule patterns to improve data quality in Salesforce (opens in a new tab)

Readers will learn six ready-to-use Validation Rule formulas that prevent common data entry mistakes, along with best practices for writing clear field-level error messages.

  1. User enters or edits a record
  2. Validation Rule formula is evaluated
  3. Bad data is blocked with a clear error
  4. Error appears at the field level
How a Validation Rule stops bad data before it is saved, using the article's approach

The article outlines six Validation Rule patterns designed to catch frequent user errors without requiring Apex or Flow. These include preventing Closed Won Opportunities from missing amounts or close dates, blocking Cases with backdated open dates beyond a seven day window, and ensuring close dates never precede creation dates.

Additional patterns address picklist state management by stopping records from reverting to New once closed, unless a custom bypass permission is granted. The piece also requires a reason field when priority changes to High status, and locks amount fields during approval reviews to prevent revenue leakage.

Beyond the formulas, the author emphasizes error message hygiene. Rules should be named clearly, descriptions filled out for audits, and errors placed at the field level rather than the page header. Messages must instruct users on the correct action instead of simply stating an invalid value. The author notes that while Validation Rules stop immediate data issues, field level required attributes or Flow notifications may be better alternatives for certain workflows.

Read the original at dev.to (opens in a new tab)

Worth reading?