Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Salesforce objects can have Relations between them.

When creating / updating Salesforce objects with Stambia, the relation can be done with a Salesforce ID - when it is known, but it can be useful to provide an ExternalId when sending data to Salesforce.


In this example, we added a "Related_Account" field to the "t_customer" object. It is a "Lookup" field and relates to the Account object.

516 Related Account


The reversed metadata for the "t_customer" object is:

516 Metadata


In this example, the Account object is also customized: it contains a custom "ext_id" field which is declared as en ExternalId in Salesforce:

516 Account

516 Account Data


So, now we want to send "t_customer" data, providing an ext_id (values in 24, 27, 97... not the Salesforce Internal Id).

To to this, simply add the following tag to the "Related_Account__c" mapping field: FKEXTID_FIELD_NAME.ext_id__c

516 Mapping

The tag is formed of a constant prefix "FKEXTID_FIELD_NAME." followed by the API name of the External Id field in the related Object.


Your object doesn't have an External Id?
If your object relation is based on the Salesforce ID (not a custom External Id), then no need to add the tag : Salesforce will match the value with the Master object's Id.


As a result, the uploaded Salesforce object is created / udpated with the expected Relation to the Account object:

 516 result


Suggest a new Article!