Consider the following rules and guidelines for Salesforce Data 360 objects used as targets in mappings:
•You can't preview data in a Target transformation.
•You can perform read and write operations on an object within a single active job at a time. Ensure that no multiple jobs are running concurrently on the same object, either within or outside Intelligent Data Management Cloud services.
•Field names in Salesforce Data 360 display with suffix __c. In the mapping, the names of the target fields are the Field API Name without the suffix __c.
•The streaming API job completes after it reads the data from source and pushes it to the target. However, the data is not loaded in the target immediately. It might take a few minutes.
•The job statistics displays the number of rows that the mapping successfully reads from the source. It does not display the success and rejected records from Salesforce Data 360.
•When you delete data using bulk API in Salesforce Data 360, ensure that you map only the primary key from your source in the mapping to the corresponding primary key of the target Salesforce records that you want to delete.
•When you create a new target using an Ingestion API Connection, use the Bulk API ingestion mode to avoid a delay in loading data into the data stream. For subsequent runs of the mapping, you can use the Streaming API.
•NULL values in the primary key field are inserted into the target object without generating an error. This is a Salesforce Data 360 limitation.