The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Salesforce integrations fail on quota and data model, not protocol (opens in a new tab)

You will learn how the org-wide daily API allocation is calculated and why batching is a design decision rather than a tuning step.

Why read this

You will also see the Apex governor limit trap that breaks batch writes, and the external ID and upsert pattern that makes retries safe.

  • 5000: Contacts written one record per call
  • 25: Calls needed via sObject Collections at 200 per request
  • 100: SOQL query ceiling per synchronous transaction
Batching cuts the calls needed to write 5,000 Contacts by a factor of 200

The article argues that Salesforce integrations rarely fail on authentication or protocol. They fail on the daily API request allocation, which is shared across every consumer in an org, and on the data model choices that are costly to reverse once records exist. It walks through the main APIs, noting that REST and SOAP are both current, that Bulk API 2.0 is a different asynchronous programming model, and that Composite and sObject Collections cut call volume sharply because each counts as one call against the allocation.

The piece then covers the constraints that shape the architecture. The allocation is set by edition and license count, and requests fail with REQUEST_LIMIT_EXCEEDED once it is exhausted, with no grace on trial and Developer Edition orgs. Batching is presented as a design decision: a 5,000 record job costs 5,000 calls one at a time but 25 through sObject Collections. Caching reference data is also suggested. Governor limits are explained as applying to customer Apex that runs when an inbound write fires triggers, and an unbulkified trigger can exceed the 100 query ceiling on a 200 record batch.

Finally, the article addresses authentication, the Lead, Contact, Account and Person Account decisions, external IDs for idempotent upserts, partial-success handling, dead letter stores and reconciliation, and sandbox and API version pinning. It also discusses when middleware is justified and the UK GDPR obligations around controllers, processors and transfers. The cost ranges and vendor-agnostic claims are the author’s own estimates and are not independently verified.

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

Worth reading?

Building a household intake workflow from FormAssembly into Salesforce (opens in a new tab)

You will see how to model a variable-length child intake as a staging parent with a Master-Detail child Custom Object, and how to avoid the flat-file and metadata-caching faults that break such integrations.

Why read this

The reader gets a worked example of a real external form pipeline.

Denormalized parent

  • Member_1 to Member_10 columns
  • Blank fields sent as nulls
  • Submission rejected

Normalized model

  • Household_Submission__c parent
  • Household_Member__c children
  • Master-Detail relationship
The flat parent layout failed, and normalising to a Master-Detail child model fixed it

The author argues that public intake forms are better handled by a dedicated external form engine than by a Salesforce Experience Cloud site, which needs heavy configuration and guest-user sharing management. They test the new FormAssembly platform, which models data collection as an end-to-end workflow with an AI assistant, Fai, that builds the form from a plain-language specification.

For a household intake where the number of members varies, Fai offered three designs and the author chose fixed member sections with conditional visibility, so that the required sections match the declared household count. The data then goes to a staging Custom Object rather than directly to Contact or Account, to avoid creating duplicates from unverified input.

The article records two pitfalls. Denormalized numbered member columns on the parent produced null payloads that caused the submission to be rejected, so the schema was normalized to a Household_Submission__c parent and a Household_Member__c child joined by Master-Detail. A deleted lookup field also remained in the connector’s cached metadata, and updating the field mapping to the new API name resolved the error.

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

Worth reading?

Must-read

Migrating HubSpot to Salesforce: External IDs, upsert, and load order (opens in a new tab)

Readers will learn how to structure a reliable HubSpot to Salesforce data migration using External IDs, proper load ordering, and Bulk API, including strategies for handling hierarchies, deltas, and validation.

  1. Cleanse data and map picklists
  2. Dry run in sandbox with disabled automations
  3. Load records following dependency order
  4. Enable read only mode and run delta load
  5. Verify record counts and relationship integrity
Phased migration process from HubSpot to Salesforce

The article addresses the complexity of moving historical records and relationships from HubSpot to Salesforce, emphasizing that simple export import fails due to differing data models. It establishes the External ID field as the foundation for tracking records, enabling idempotent upserts, and linking related objects without relying on Salesforce generated identifiers.

It outlines a strict dependency sequence for loading records, starting with Users and Accounts before moving to Contacts, Opportunities, and Activities. Special attention is given to Account hierarchies, recommending a two pass approach to avoid parent child reference errors. The piece includes a Python example using the Bulk API to demonstrate upserting an Opportunity by matching its Account via an External ID rather than a native Salesforce identifier.

Before migration, the author stresses data cleansing, deduplication rules, and mapping picklist values like pipeline stages. A sandbox dry run is recommended to generate repeatable error reports and to temporarily disable automations such as Flow and Apex triggers that could trigger unwanted side effects during bulk loads.

The final phase uses a delta load strategy to capture changes made after the initial bulk transfer, requiring source system read only mode and timestamp tracking. Post migration validation involves comparing record counts, verifying relationship integrity, reconciling financial totals, and spot checking field values to ensure data accuracy before full team adoption.

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

Worth reading?