Handling Validation Rule Conflicts

Prev Next

Overview

Validation rules in your Salesforce org may prevent Integrous Analytics from updating Attribution and Sales Journey data. This article explains how to resolve these conflicts while maintaining your business rules.

When This Issue Occurs

If your validation rules prevent records from being saved when Integrous Analytics updates custom fields, our system cannot function properly.

Common scenarios:

  • Validation rules requiring fields on Closed Won opportunities

  • Rules preventing updates to records in specific stages

  • Complex business logic conflicting with automated processes

Why This Matters

When validation rules block Integrous Analytics from updating attribution fields, you lose critical revenue intelligence. Every lead, contact, and opportunity should have complete attribution and sales progression data, regardless of whether they meet other business criteria. For example, even if an opportunity lacks required documentation fields, it still needs accurate source attribution for marketing ROI analysis. These conflicts break attribution tracking, even though attribution should work independently of your other business processes.


What This Affects

Objects: Leads, Contacts, and Opportunities

Fields Updated:

  • Our system only updates our own fields (Attribution Engagement, Current Activation, etc.)

  • There are just two standard fields our system updates, and only when configured to do so in the Admin Console:

    • Lead Source (if Lead Source Override enabled)

    • Lead/Contact Status (if Reactivation Status configured)

    • More info


How It Works

The validation bypass feature uses a custom setting that allows our system to update attribution fields while preserving your business rules for manual users. These bypass flags are set automatically during system updates and cleared immediately after processing, so validations resume as normal for all other updates.

Available Bypass Settings:

  • integrous__BypassOpportunity__c - For Opportunity validation rules  

  • integrous__BypassLead__c - For Lead validation rules

  • integrous__BypassContact__c - For Contact validation rules


Example Use Case

Problem: Validation rule requires AE Notes on Closed Won opportunities. Integrous Analytics can't update Attribution Engagement field when opportunity closes.

Result after bypass:

  • Manual users still must enter AE Notes to close opportunities

  • Integrous Analytics can update attribution fields

  • Attribution reporting stays accurate


How to Implement It

Add a bypass condition to any validation rule that conflicts with Integrous Analytics updates. The exact line you add depends on the object:

Object

Validation Rule Condition to Add

Opportunity

NOT($Setup.integrous__BypassClientValidation__c.integrous__BypassOpportunity__c)

Lead

NOT($Setup.integrous__BypassClientValidation__c.integrous__BypassLead__c)

Contact

NOT($Setup.integrous__BypassClientValidation__c.integrous__BypassContact__c)

Example:

For example, to avoid conflicts with this Opportunity Validation Rule:

AND(
  ISPICKVAL(StageName, "Closed Won"),
  ISBLANK(AE_Notes__c)
)

Update it as follows:

AND(
  NOT($Setup.integrous__BypassClientValidation__c.integrous__BypassOpportunity__c),
  ISPICKVAL(StageName,"Closed Won"),
  ISBLANK(AE_Notes__c)
)

💡 Troubleshooting Tip

If you're inspecting the bypass fields and they appear blank, that's expected. The system only sets them briefly while it runs, then clears them to re-enable your normal validation logic.