Consider the following rules and guidelines for Salesforce Data 360 objects used as targets in mappings:
•When you create a mapping to write data to Salesforce Data 360, you can't preview data in the Target transformation. The preview results in an error.
•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 run a mapping to write data to a data lake object that already has a job ID created, the mapping fails. Before you run the mapping, you need to ensure that your data lake object is not being used in another job.