Data Doctor offers flexible settings to customize how the application works in your Salesforce environment. This guide covers the key configuration options and best practices for setup.
To access Data Doctor settings:
Note: You need administrator permissions to modify most Data Doctor settings.
Configure which Salesforce objects Data Doctor can process. Standard objects (Account, Contact, Lead, Opportunity) are available on all plans. Custom object support requires a paid subscription.
Set the maximum number of records per object that Data Doctor can analyze. The default limit is 100,000 records per object.
Define how Data Doctor identifies duplicate records:
Configure how Data Doctor determines which record becomes the master when merging duplicates:
Specify how conflicting field values are handled during merges. Options include keeping the master record value, keeping the most recent value, or prompting the user to choose.
Configure how child records and related objects are handled when parent records are merged.
Set the number of records processed per batch for large merge jobs. Lower values reduce system load but increase processing time.
Configure maximum processing time for individual merges to prevent long-running jobs from consuming resources.
Define which users or profiles can:
Data Doctor respects Salesforce sharing rules and field-level security. Configure whether the app should run in:
No. Data Doctor comes with sensible defaults. However, customizing settings to match your organization's needs will improve the user experience.
Most settings are organization-wide, but individual users can set personal preferences for things like default filters and notification preferences.
Active merge jobs continue with the settings they started with. New settings apply to jobs initiated after the change.
Best Practice: Test configuration changes in a sandbox environment before deploying to production to ensure they work as expected.
