Problem
When attempting to create a MACD (Move, Add, Change, Delete) opportunity from an existing subscription, the operation appears to complete but the resulting basket is empty. No solutions or configurations are created in the basket, even though the opportunity and basket records are generated successfully.
Root Cause
The subscription or product configuration being used as the source for the MACD does not have the cssdm__solution_association__c field populated. This field links the subscription/PC to a solution in the Solution Management system.
MACD operations in Solution Management require this association to:
1. Identify which solution the change request applies to
2. Copy the existing configuration structure into the new MACD basket
3. Maintain continuity between the original subscription and the change request
Without this association, the MACD operation cannot determine what configuration to clone, resulting in an empty basket.
Resolution Steps
- Verify the Subscription's Solution Association:
- Navigate to the subscription record that you're using to initiate the MACD
- Check the
cssdm__solution_association__cfield -
If this field is blank or null, the subscription is not linked to a solution
-
Check the Product Configuration's Solution Association:
- Navigate to the product configuration(s) linked to the subscription
- Verify the
cssdm__solution_association__cfield on each PC -
All PCs that should be part of the MACD must have this field populated
-
Associate the Subscription/PC with a Solution:
- Identify the correct solution that this subscription/PC belongs to
- Update the
cssdm__solution_association__cfield on the subscription and all related PCs to reference the solution's ID -
Ensure the solution record exists and is in an active state
-
Retry the MACD Operation:
- After updating the solution association, navigate back to the subscription
- Click the "Change Request" button
- Select the MACD type (e.g., Disconnect, Upgrade, Downgrade)
- Click "Create MAC Opportunity"
- Verify that the basket now contains the expected solutions and configurations
Prevention
To prevent this issue from occurring:
- Ensure all subscriptions and product configurations are properly associated with solutions at the time of initial order creation
- If subscriptions are created via API or custom code, include logic to populate
cssdm__solution_association__c - When migrating data or creating subscriptions outside of the standard CloudSense flow, verify solution associations before attempting MACD operations
- Consider adding validation rules or process builder flows to flag subscriptions without solution associations
Important Notes
- This is a data integrity issue, not a system defect. Solution Management requires explicit associations to function correctly.
- If you're unsure which solution a subscription should be associated with, review the original order or basket that created the subscription.
- Bulk updates to solution associations should be done carefully, ensuring each subscription is linked to the correct solution.
Priyanka Bhotika
Comments