Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Cloud Customer 360
  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 Customer 360 with MDM Multidomain Edition
  12. Managing Multi-Org
  13. Custom Settings
  14. Glossary

Internal Settings for Beans

You can configure internal settings and change the default behavior of beans.
You can configure the following internal settings for beans:
Ignore Deleted Beans
The beans that have the Account Deleted, Lead Deleted, or Contact Deleted flag enabled in the bean details page are not part of the consolidation process.
If you want the deleted beans to be a part of the consolidation process, set the
Ignore Deleted Beans
internal setting value to false. Default is true.
The following sample code indicates to include the deleted beans in the consolidation process:
API_SettingsManager.updateInternalSetting('Ignore Deleted Beans','false');
Exclude Deleted Beans
When you search for records in the
Lightning
and Visualforce Scout pages, the beans that have the Account Deleted, Lead Deleted, or Contact Deleted flag enabled in the bean details page are not displayed in the search result.
If you want the deleted beans to be displayed in the search result, set the
Exclude Deleted Beans
internal setting value to false. Default is true.
The following sample code indicates to include the deleted beans in the search result:
API_SettingsManager.updateInternalSetting('Exclude Deleted Beans','false');
SkipMBCount[:<Master Bean Name>]
If you exceed the Salesforce governor limits in your organization, you cannot link the beans of other records to the master bean of an account record.
You can enable the linking of beans to the master bean if you skip validation of master beans.
To skip the validation of master bean, set the
SkipMBCount
internal setting value to true. Default is false.
The following sample code skips validation for all master beans:
API_SettingsManager.updateInternalSetting('SkipMBCount','true');
To skip the validation for a specified master bean, set the
SkipMBCount:<Master Bean Name>
internal setting value to true. Default is false.
The following sample code skips validation for a specified master bean:
API_SettingsManager.updateInternalSetting('SkipMBCount:MB-288306','true');

0 COMMENTS

We’d like to hear from you!