External ID mappings

An External ID maps one remoteEaze record to the identifier expected by one Third-Party System.

External Key names the identifier, such as customer_id. External Value is the value used by the external System. Value Type records how that value should be interpreted. The remoteEaze Entity Type and record remain the local side of the mapping.

Create a mapping

1. Open Processing & Monitoring → Third Party Delivery → External IDs.
2. With Create Third Party Mapping, select the Company when shown, entity type, remoteEaze record, and destination System. The record selector uses server-side search for the selected Entity Type.
3. Enter the External Key, External Value, and its value type.
4. Select Save External ID.

Mappings are immediate configuration rather than maker-checker records. Use Update Third Party Mapping to correct a mapping and Delete Third Party Mapping to remove it.

The same External IDs section can appear on supported entity detail pages with the record locked. Permissions are still evaluated on the Mapping entity; Read access to the parent record alone does not grant Mapping maintenance.

The mapping must be unique for the relevant System, entity, key, and value contract. Confirm an external identifier before changing it because Hook payloads may rely on the mapping.

Find records in selectors

Select Company, Entity Type, and System before searching. The selector then searches the supported remoteEaze records by useful business references, such as customer number or name and account number or name. This avoids loading an entire directory into the browser.

Some configuration screens also support mappings for embedded or related records. Choose the precise Entity Type because a parent mapping does not automatically identify every child record.

Import external reference data

Where a mapping flow offers System Data, first import the supported data from the external System, then match the imported row to the remoteEaze record. This is useful when the external catalogue must be visible before a user can establish the link.

The current bulk System Data mapping flow supports Nations and Languages. Use the ordinary searchable selectors or entity-specific mapping surfaces for other supported record types.

Use mappings in Hooks

A Hook field mapping decides where an identifier appears in the request. The External ID record supplies its value. A response mapping can capture a new identifier returned by the external System. Read Third-party systems and delivery hooks for the complete request and response flow.