Salesforce Connector > Masking tasks with Salesforce > Special handling of standard objects
  

Special handling of standard objects

If you cannot create an external ID field in a child object or a junction object, create an external ID with the insert operation. Change the task operation from insert to upsert before you run the task.
The following standard objects require special handling:
Pricebook2
Every organization contains a standard Pricebook object that you cannot alter. If the source contains the Pricebook2 object, you must copy the Pricebook2 object ID to the corresponding external ID field in the target after the task creates the external ID in the target and before you run the task.
RecordTypes
You can select the RecordTypes object only when you enable them at profile level for individual objects. Before you run the task, enable the required RecordTypes in the target profile.
AssetRecord
To create the AssetRecord object, you must add the Account object or the Contact object to the Asset object in a task or else the task fails. Since these relationships are not mandatory, there are no errors or warnings in the validation report.
PersonAccounts
You cannot edit the AccountName field directly in the PersonAccounts object. Salesforce combines the FirstName and LastName fields in the appropriate order according to the language settings that you configure and derives the AccountName field. You can view and edit the AccountName field. You cannot alter the field level security to make it a read-only field. To avoid writing to the AccountName field, apply nullification masking on the AccountName field with the PersonAccounts object.
Contracts
You cannot insert and activate the Contracts object in a single step. Insert the Contracts object with Draft status and then update with Activated status. If you attempt to insert a Contract with Activated status, you get the Invalid Status error.
Idea
Use the Idea object only for inplace masking. The Idea object has a mandatory parent relationship with the Community object. But the Community object contains read-only fields. When the target is different from the source, the task fails to insert records into the Community object.
OpportunityLineItem
In the OpportunityLineItem object, you can view and update the Unit Price and Total Price fields. When you insert a record, specify only one of the fields. Else, the task fails and generates an error. By default, both the Unit Price and Total Price fields are specified. To avoid errors, apply nullification masking on one of the fields.
User
The task can reconcile relationships for the User object in two ways. By default, the task uses the Alias field for reconciliation if the corresponding User relationships are selected in the Source page.
The other way to reconcile the relationship is to apply custom substitution masking on the Owner ID field for an object. In this case, you do not need to select User relationship in the Source page because the task overrides the default alias reconciliation. To apply custom substitution masking, perform the following steps:
  1. 1Create a dictionary file with the target and the corresponding source user IDs.
  2. 2Copy the file into the dictionary file location of the Secure Agent installation directory.
  3. 3Create a flat file connection to the dictionary file directory.
  4. 4Use the dictionary file to configure custom substitution masking on the Owner ID field.
  5. 5Provide a target user ID in the lookup error constant if the target does not contain the Owner ID same as the source.