Custom Validation Rule Blocking LMA Change Order Activation

Problem

When attempting to activate a change order (MACD) for an existing LMA (Licensed Material Agreement) subscription, the activation fails with an error message indicating that a custom validation rule is blocking the operation.

The error typically appears in the Solution Console or during the order activation process, preventing the change order from being processed.

Example Error Message

Validation Rule Error: [Custom Rule Name] - [Specific validation message]

Root Cause

A custom validation rule has been configured on a CloudSense object (typically csord__Subscription__c, csord__Order__c, or related objects) that is evaluating to true during the change order activation process.

The validation rule logic is preventing the update or creation of records required for the change order to complete. This is often due to:
- The validation rule not accounting for change order scenarios
- Required fields not being populated during the MACD process
- Business logic in the validation rule conflicting with the change order workflow

Resolution

Step 1: Identify the Blocking Validation Rule

1. Review the full error message to identify the exact validation rule name
2. Note the object on which the validation rule is configured
3. Document the specific validation message returned

Step 2: Review the Validation Rule Logic

1. Navigate to Setup > Object Manager
2. Select the object mentioned in the error (e.g., Subscription, Order)
3. Click Validation Rules
4. Locate and open the validation rule identified in Step 1
5. Review the Error Condition Formula to understand what condition is being evaluated
6. Review the Error Message to understand what the rule is enforcing

Step 3: Determine the Appropriate Fix

Based on the validation rule logic, determine the appropriate resolution:

Option A: Update the Validation Rule to Exclude Change Orders
If the validation rule should not apply to change orders, modify the rule to exclude MACD scenarios:

1. Edit the validation rule
2. Update the Error Condition Formula to add an exception for change orders:
   AND( [existing validation logic], NOT([change order condition]) )
   Common change order conditions:
3. csord__Is_Change_Order__c = true
4. csord__Parent_Order__c != null

5. csord__Order_Type__c = 'Change Order'

6. Save the validation rule

7. Retry the change order activation

Option B: Populate Required Fields
If the validation rule is enforcing a required field that is not being populated during the MACD process:

1. Identify the field(s) required by the validation rule
2. Navigate to the change order or subscription record
3. Populate the required field(s) with the appropriate values
4. Save the record
5. Retry the change order activation

Option C: Temporarily Deactivate the Validation Rule
If the validation rule is not critical for change orders and an immediate fix is needed:

1. Edit the validation rule
2. Uncheck the Active checkbox
3. Save the validation rule
4. Complete the change order activation
5. Re-activate the validation rule after the change order is processed

Important: Only use this option if you understand the business impact of temporarily disabling the validation rule.

Step 4: Verify the Change Order Activates Successfully

1. Return to the Solution Console or order record
2. Retry the change order activation
3. Verify the change order activates without errors
4. Confirm the subscription is updated as expected

Step 5: Test for Side Effects

1. Create a test change order for a different subscription
2. Verify the validation rule still enforces its logic for non-MACD scenarios (if applicable)
3. Confirm no other processes are impacted by the validation rule change

Prevention

For Salesforce Administrators

• Change Order Testing: When creating custom validation rules on CloudSense objects, always test with change order scenarios to ensure they don't block MACD operations
• Validation Rule Documentation: Document the purpose and scope of each validation rule, including whether it should apply to change orders
• Exception Handling: Include explicit exception logic for change orders in validation rules that should not apply to MACD scenarios

For Implementation Teams

• Validation Rule Review: During implementation, review all custom validation rules on CloudSense objects and ensure they account for change order workflows
• MACD Testing: Include change order activation in your test plans when deploying or modifying validation rules
• Communication: Document all custom validation rules and their impact on CloudSense processes in your implementation documentation

Related Information

• Affected Objects: csord__Subscription__c, csord__Order__c, csord__Solution__c
• Related Fields: csord__Is_Change_Order__c, csord__Parent_Order__c, csord__Order_Type__c
• Related Processes: MACD (Moves, Adds, Changes, Deletes), Change Order Activation
• Validation Rule Best Practices: Salesforce Validation Rule Documentation