Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Cloud MDM - Customer 360 for Salesforce
  3. Configuring the Data Cleansing Settings
  4. Managing Batch Jobs
  5. Verifying Addresses, Email Addresses, and Phone Numbers
  6. Synchronizing Salesforce Records with CC360
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Cloud MDM - Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Custom Settings
  14. Glossary

Getting Updates from the Master Org in Batch Mode

To get updates for multiple accounts or person accounts from the Master Org, you need to run a batch job from the Spoke Org.
  1. Based on the Salesforce environment that you use, perform one of the following tasks:
    • In Salesforce Classic, in the upper-right corner of the page, select your name, and click
      Developer Console
      .
    • In Lightning Experience, click the quick access menu ( The image shows the quick access menu. 
				  ), and then click
      Developer Console
      .
  2. Click
    Debug
    Open Execute Anonymous Window
    .
  3. Enter the following command to run the batch job for person accounts:
    CMDMMultiOrgsObjectSyncBatch b = new CMDMMultiOrgsObjectSyncBatch('PersonAccount'); database.executeBatch(b, batchSize);
    If you do not specify a batch size, the method uses the default batch size of 200. It is recommended to set the batch size to less than or equal to 200.
  4. Enter the following command to run the batch job for accounts:
    CMDMMultiOrgsObjectSyncBatch b = new CMDMMultiOrgsObjectSyncBatch('Account'); database.executeBatch(b, batchSize);
    If you do not specify a batch size, the method uses the default batch size of 200. It is recommended to set the batch size to less than or equal to 200.
    The batch jobs to synchronize accounts and person accounts with the Master Org cannot be run concurrently.
  5. Click
    Execute
    .
    During batch processing, if errors occur because of incorrect field types or incorrect field values, the batch job processes other records and adds information about error records to the
    External Field Update Failure Name
    table. If the subsequent batch job identifies errors for an account for which an error record already exists in the error table, the batch job overwrites the existing error record. If the batch job encounters errors during an update to an account, only one error message is added to the
    External Field Update Failure Name
    table.
    In the Master Org, if a boolean field is updated with any value other than
    True
    , the Apex API
    Boolean.ValueOf
    returns false. For example, in the Master Org, a boolean field is updated with a number
    1234
    and the value of that field in the Spoke Org is
    False
    . When you run the batch job, the Apex API
    Boolean.ValueOf
    returns the value
    False
    . As a result, the batch job does not update the boolean field in the Spoke Org because both the values are
    False
    .
A notification is posted on the chatter feed to notify users about updated accounts or person accounts.

0 COMMENTS

We’d like to hear from you!