The code lists every system needs, kept once: countries and regions, Incoterms, payment terms, languages, and the crosswalk to each system's local codes.
Tables are read through the Table API and, for volume, exports; the rows stay in ServiceNow.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Choice lists | sys_choice | element · value · label | live; polled or event-driven |
| Countries | core_country | name · iso3166_2 | live; polled or event-driven |
The first object above carries the strong keys; the standardised attributes come from the same rows. A code list is a small master-data domain with the same history, rules and security as the big ones.
Writes go through the Table API or Import Sets with a coalesce field; each call returns the sys_id or the error, logged beside the change.
| Interface | Used for | Result |
|---|---|---|
sys_choice inserts through the Table API | golden values approved for write-back: code list; codes; crosswalks | the id or error ServiceNow 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.
ServiceNow roles and ACLs are mapped to Lima policies once.
Countries, regions and code lists on
Other domains on ServiceNow
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 ServiceNow.
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.
