Domain catalogue Parties on Salesforce

Business contact on Salesforce

One record per person at a customer, supplier or partner, linked to the organisation they work for and the roles they hold.

SOURCES, READ IN PLACESalesforceCRMASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN BUSINESS CONTACTBusiness contactone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
The objects the domain reads in place on Salesforce, the assembly steps, and who reads the result. Writes go through REST upserts on an external id.
3
objects read in place from Salesforce
catalogue
4
attribute groups assembled
catalogue
3 days
to production-grade
estimate
1
write path, acknowledged and logged
catalogue
0
rows copied to start
product
What the domain reads

The Salesforce objects behind the golden record

Objects are read through the Salesforce APIs (REST, Bulk, Change Data Capture); the rows stay in Salesforce.

ObjectRead fromFields the domain usesFreshness
ContactContactId · FirstName · LastName · Email · Phone · Title · AccountId · HasOptedOutOfEmaillive; Change Data Capture where enabled
ActivitiesTask · EventWhoId · ActivityDate · Subjectlive; Change Data Capture where enabled
Campaign membershipCampaignMemberContactId · CampaignId · Statuslive; Change Data Capture where enabled
The keys

How business contact records match, in this system's fields

e-mail addressphone (standardised)name and employer (fuzzy)portal user id

The first object above carries the strong keys; the standardised attributes come from the same rows. A shared mailbox address is a weak key; the rules treat info@ and orders@ as organisation attributes, so two people stay apart on it.

What is written back

Through the interfaces Salesforce supports

Writes are upserts through the REST API on the external id; every call returns the record id or the error, and Lima logs both.

InterfaceUsed forResult
upsert Contact on External_Id__c through the REST API; consent fields honouredgolden values approved for write-back: identity; employer and role; consent and preferencesthe id or error Salesforce returns, stored beside the change

Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.

Access and prerequisites

What is in place before the first build

Salesforce profiles and sharing rules are mapped to Lima policies once; a user sees here what they see in Salesforce.

Register the objects3 objects from the connector catalogue; each shows its rows at once.
Nearby

This domain on other systems, and other domains on Salesforce

Business contact on

Other domains on Salesforce

Terms on this page

Partner functionSAP's name for the role a person or organisation plays on a document.
ConsentThe recorded permission to contact a person on a channel, with its date and source.
Read in placeThe rows stay in Salesforce; Lima sends the filter and the columns and Salesforce returns the matching rows.
Questions

Does this domain copy data out of Salesforce?

The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.

What does the Salesforce team need to do?

Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Salesforce.

Can we start with reads only?

Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.