...
CustomMetaData Mapping | Description |
|---|---|
Object API Name | Target Standard/Custom Object to retrieve the contact person |
Object Record Id | The look-up field that will be used as a filter to for the target object for contact personto query the contact person. The value of this field is the recordId of the source record when synchronizing a xero contact. |
FirstName | The field to map the FirstName of the Contact Person Xero. |
LastName | The field to map the LastName of the Contact Person Xero |
EmailAddress | The field to map the Email of the Contact Person Xero |
IncludeInEmails | The field to map the IncludeInEmail of the Contact Person Xero |
NumberOfContacts | The limit of number of contacts to sync in Xero. We can only sync a maximum of 5 contacts. |
IsContactPerson | A boolean field in the target object that determines if a record can be sync as a contact person. |
| Info |
|---|
FirstName, LastName, EmailAddress, IncludedInEmails and IsContactPerson are fileds in the target object. These are all required setup the contact person sync in Xero. |
After you have setup the mapping, we can synch the contact person by adding the CustomMetaData mapping name that we setup in the XeroContactPersonFieldMappingName parameter in the Sync Account to Xero invocable method.
...
In this example, the object that we are synchronizing is Account (Xero Contact) and Contact (Contact Person). The {$Record.Id} here refers to the recordId of the Account. The {$Record.Id} will also be used as the same value for the AccountId below in the contact person mapping. The design principle here is that the object for contact person will always have a look-up field going back to the source object of its Xero Contact.
...
| Info |
|---|
Ensure that when synchronizing contact person in Xero, the primary person in the Xero Contact is populated. Xero will not allow the synchronization of contact person if the primary person is not populated. |