Prices, discounts and surcharges as governed master data with validity, scale and precedence, tied to golden products and customers.
Objects are read through the Salesforce APIs (REST, Bulk, Change Data Capture); the rows stay in Salesforce.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Price books and entries | Pricebook2 · PricebookEntry | UnitPrice · CurrencyIsoCode · IsActive | live; Change Data Capture where enabled |
| Quotes | Quote · QuoteLineItem | QuoteId · UnitPrice · Discount | live; Change Data Capture where enabled |
The first object above carries the strong keys; the standardised attributes come from the same rows. Keys resolve to golden customers and products first, so a price for a merged customer applies to every source key.
Writes are upserts through the REST API on the external id; every call returns the record id or the error, and Lima logs both.
| Interface | Used for | Result |
|---|---|---|
PricebookEntry upserts; quote lines read for realised prices | golden values approved for write-back: condition; validity; precedence | the 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.
Salesforce profiles and sharing rules are mapped to Lima policies once; a user sees here what they see in Salesforce.
Price lists and conditions on
Other domains on 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.
Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Salesforce.
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.
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.
