Salesforce Org Considerations

Before using Proff Connect in production, we recommend reviewing the following areas of your Salesforce org. Because Proff Connect creates and updates Account records — and optionally creates Leads — any existing configuration that controls or reacts to those operations may cause unexpected behaviour or sync failures.

ℹ️ This is not specific to Proff Connect — it applies to any managed package that creates or updates records in your org. The items below are the most common causes of unexpected errors after installation.

⚡ What Proff Connect does in your org

To understand what to review, it helps to know what Proff Connect does under the hood:

• Creates Account records (via Company Search and Bulk Create)

• Updates Account records (via single sync, Mass Update, and Real-Time Changes)

• Optionally creates Lead records

• Creates Company Insight records (a custom object included in the package)

Any Salesforce configuration that triggers on Account or Lead Create/Update will fire when Proff Connect runs — including during bulk operations like Mass Update.

⚠️ Required fields

When Proff Connect creates an Account, it populates the fields you have configured in your Object Field Mapping. Any field that is not mapped will be left empty on creation.

This means that fields marked as required at the field level in Salesforce will block record creation if they are not populated by Proff Connect. We therefore recommend not using field-level required settings for fields that Proff Connect is responsible for populating — and instead enforcing required fields through Lightning page layouts and record page configurations instead. This way, the requirement applies to users editing records manually, but does not block the integration from creating records with the data it has available.

💡 Page layout and Lightning page required field settings only apply when a user saves a record through the UI — they do not affect API or integration writes. Field-level required settings (in Object Manager) do apply to all writes including integrations, and should be used with care.

Before going live, review:

• Setup → Object Manager → Account → Fields & Relationships — check whether any fields are marked as required at the field level, and consider changing these to page layout required instead

• Your Object Field Mapping in Proff Connect — ensure all fields that are critical for your org are mapped so Proff Connect can populate them on creation

⚠️ Validation rules

Validation rules on Account (or Lead) run on every save — whether the record is created manually by a user or by an integration like Proff Connect. If a validation rule blocks a save, the Account will be logged with a DML ERROR in the sync log and the record will not be created or updated.

We recommend going through all active validation rules on Account and Lead and asking the following for each:

• Could this rule be triggered when Proff Connect creates or updates a record? For example, does it require a field that Proff does not provide?

• Should the rule apply to integration-created records at all, or is it only relevant for manual data entry?

• If the rule should not apply to Proff Connect, can it be made conditional — for example by checking the running user's profile or a bypass field?

💡 A common approach is to add a condition like $Profile.Name != 'System Administrator' or to use a custom bypass field on the object. This lets you keep the validation rule active for user-driven saves while allowing the integration to write freely.

⚠️ Flows, automations, and triggers

This is the area where we most often see unexpected side effects after go-live. We strongly recommend that you get a clear overview of all automations that run on Account and Lead Create/Update in your org — and actively decide for each one whether it should also fire when Proff Connect is the one making the change.

Automations to map out include:

• Record-triggered Flows on Account and Lead (After Save and Before Save)

• Apex triggers on Account and Lead

• Workflow Rules (legacy, but still common in older orgs)

• Process Builder processes (also legacy, gradually replaced by Flows)

For each automation, consider what it actually does and whether that action makes sense when Proff Connect is the trigger. Common examples of things that may not be desirable:

• Sending a welcome email or internal notification for every new Account created — this could fire for every single record during a Bulk Create

• Creating a follow-up Task or Event on Account Create — during a Bulk Create of 200 companies, 200 tasks would be created

• Posting to Slack or Teams on Account Update — during a Mass Update of 5,000 records, 5,000 messages would be sent

• Automatically assigning Accounts to a queue or owner based on criteria that may not apply to imported data

• Kicking off an onboarding or approval process every time an Account is created

💡 A reliable pattern is to add an entry condition to your flows that checks the Last Modified By user or profile, or to use a custom checkbox field like Created_By_Integration__c on the Account. This gives you fine-grained control over which automations fire for user-created records versus integration-created records.

For Apex triggers specifically, also verify that they are bulkification-safe — meaning they process all records in Trigger.new as a collection rather than looping and making individual SOQL or DML calls per record. Triggers that are not bulk-safe can hit Salesforce governor limits when Mass Update processes large batches.

✅ Recommended checklist

Before going live with Proff Connect in production, we recommend going through the following: