Table of Contents

Search

  1. Preface
  2. Introduction to Informatica 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 Customer 360 for Salesforce
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Troubleshooting
  14. Appendix A: Custom Settings
  15. Appendix B: Glossary

Asynchronous Hierarchy Processing

Asynchronous Hierarchy Processing

Customer 360 for Salesforce
asynchronously processes hierarchy operations for large hierarchies.
Large hierarchies are hierarchies with more nodes than the maximum trigger hierarchy limit. Hierarchy processes for large hierarchies would encounter Salesforce governor limits if
Customer 360 for Salesforce
processed hierarchy changes synchronously. To avoid these limits,
Customer 360 for Salesforce
uses asynchronous batch jobs to process changes to large hierarchies.
The following batch jobs process hierarchy changes asynchronously:
Asynchronous Hierarchy Process
Processes add, move, and remove operations for large hierarchies.
Asynchronous Cloning Process
Processes clone operations if the number of nodes to clone is larger than the maximum trigger hierarchy limit.
If you abort an asynchronous hierarchy batch job, you could get unexpected hierarchy results. Do not abort a hierarchy batch job.
When you delete a leaf node from a large hierarchy,
Customer 360 for Salesforce
processes the delete synchronously.
Customer 360 for Salesforce
processes all other changes to large hierarchies asynchronously.

0 COMMENTS

We’d like to hear from you!