The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Building Custom Objects and Permission Sets with the Salesforce Development Plugin for Claude Code (opens in a new tab)

You will learn how to set up the Salesforce Development Plugin in Claude Code, prepare an org with the metadata-experts and salesforce-api-context MCP Servers, and generate a Custom Object, Permission Sets and a Lightning page as metadata.

Why read this

You will also see why the older Salesforce DX MCP Server is being retired and why deployments should stay with humans.

  1. Create the DX project
  2. Build the Custom Object and fields
  3. Build the Permission Sets
  4. Build the Lightning page
  5. Package the metadata for a human to deploy
The main stages of building metadata with the plugin in the worked example

The article explains how the Salesforce Development Plugin for Claude Code differs from other tools with similar names. It groups Skills, the Salesforce CLI and hosted metadata servers into one toolset, while the Salesforce DX MCP Server reaches end-of-life on November 2, 2026, and Salesforce in Claude is aimed at end users rather than builders. The author lists the prerequisites: Node.js, Python, the Salesforce CLI and Claude Code, with a Claude plan that includes Claude Code. The org must have the MCP Servers page under Integrations and API Catalog used to enable the metadata-experts and salesforce-api-context MCP Servers.

The walkthrough then installs the plugin with the claude plugin install command and runs the setup command to check the org connection. The author builds a worked example, The General Store, using prompts that create a DX project, an Equipment Loan Custom Object with picklists, a lookup and a long text field, two Permission Sets, and a Lightning Record Page. He reviews the generated XML to confirm the read, create and edit permissions match the requirements.

The piece closes with advice on safety. It recommends building in a sandbox, Developer Edition org or Scratch Org, keeping deployments in human hands, and giving the agent specific field names and permissions because the model is trained on generic data.

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

Worth reading?

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?

Decouple dynamic business rules from Salesforce Flow using reference tables (opens in a new tab)

You will learn how to move static routing logic out of Flow elements into external reference tables, reducing deployment risk and enabling non-technical staff to manage updates.

The article argues against hardcoding business rules directly inside Flow decision nodes or Formula Fields, explaining that this practice creates maintenance debt and increases deployment risks. Instead, it recommends externalizing ever-changing logic into reference tables stored as either Custom Objects or Custom Metadata Types.

A detailed comparison outlines when to choose each storage method, noting that Custom Objects are better for frequently updated operational data managed by business users, while Custom Metadata Types suit static configuration moved through deployment pipelines. The author walks through building a territory assignment engine using a Custom Object to route Opportunities based on postal codes.

Key implementation details include optimizing the Flow for fast field updates, using a Get Records element with a CONTAINS filter, and sorting results by last modified date to handle overlapping rules safely. The piece also warns about partial string matching pitfalls and suggests padding delimiters to prevent incorrect matches.

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

Worth reading?