Options
The URL of the C4C instance, mostly in the format https://myXXYYZZ.crm.ondemand.com
When no path in the given, the adapter expects the API reachable under /sap/c4c/odata-sso/v1/c4codataapi/
(https://myXXYYZZ.crm.ondemand.com/sap/c4c/odata-sso/v1/c4codataapi/)
If CPI is used and the path is altered, then give the full URL to the Auth/Metadata Endpoint, e.g. https://myXXYYZZ.crm.ondemand.com/sap/c4c/odata/cust/v1/z_marini_contact_data
The username for authentication.
The password for authentication.
The C4C module name to sync.
The function name to use - e.g. ConvertLeadToOpportunity
Default is ’’ (empty)
Can be set to technical if only Basic Auth as authentication should be used.
Default is ’’ (empty)
A global filter query to be applied when requesting changed entries.
Documentation regarding the syntax: https://help.sap.com/doc/5890d27be418427993fafa6722cdc03b/Cloud/en-US/OdataV2.pdf#page=64
Default is ’’ (empty)
For 1:1 relation fields its possible to expand the returned result with the values of the related field.
Adding a relation field here will add all the fields of the related entry prefixed with the field name to the fetched fields. Then these fields can be mapped normally.
Multiple fields can be seperated by comma.
For 1:n relations will return an json encoded array of the related entries.
It is possible to expand deep into the relation tree by separating the relation names with a slash, e.g. Contact/ContactParty.
NoteThese added fields are read-only. It’s not possible to sync them back.
If this is needed a second plan is required.
Default is false
If set to true, the marketing permission will be fetched from the C4C instance and can be updated.
Will add the fields marketingPermissionEmail, marketingPermissionPhone, marketingPermissionFax, and marketingPermissionSms.
Should only be used if the Module is configured to use the marketing permission. Adds additional requests to the C4C instance per request.
Default is false
If set to true, GUID fields will be converted to strings with dashes, e.g. 12345678123412341234123456789012 will be converted to 12345678-1234-1234-1234-123456789012.
This is useful when using relation lookups in the HubEngine, as the ObjectID saved in the relation store always has the dashes removed.
Default is empty.
If configured, this option allows you to resolve a field (e.g. ObjectID) in the target module using a value from another field in the current module. Each entry defines a lookup mapping in the format: targetField:lookupModule:lookupField:returnField.
When this is set, for each mapping:
The value of targetField in the current data row is used to query the lookupModule where lookupField equals this value.
If a matching record is found, the corresponding returnField is retrieved and written back to the targetField.
If no match is found, the field is removed from the payload, and a warning is logged.
This is useful when related objects are not directly referenced by their ObjectID, but by another unique field (e.g., external ID or name).
NoteThis adds one request per lookup per record to the C4C instance. It may impact performance when used extensively.
Example: AccountPartyUUID:CorporateAccount:ExternalID:ObjectID
In this example:
- The value of AccountPartyUUID in the current record is used to search the CorporateAccount module.
- The search filters by ExternalID matching the value.
- If a match is found, AccountPartyUUID is updated with the ObjectID of the corresponding CorporateAccount.
Some instances have issues with batch updates and take a long time to process them.
This option allows you to disable batch updates and send each update individually.
This can be useful for troubleshooting or when the batch update process is causing issues.
Please note that this may increase the number of requests to the C4C instance and impact performance.