Solution Template Not Found on Basket: Missing Schema on Solution Definition

Problem

When attempting to add a solution to a basket in the CloudSense Solution Console, the operation fails with the following error:

ERROR Error: Solution Template (a2w6D0000005XSQQA2) not found on basket.

This error occurs regardless of which solution you attempt to add, with each error referencing the specific Solution Template ID for that solution. The error prevents any solutions from being added to the basket, blocking the entire ordering workflow.

Root Cause

The error occurs because one or more Solution Definition records in the solution hierarchy are missing an associated Schema. Specifically, when a Solution Definition is created without a Schema linked to it, the CloudSense engine cannot properly instantiate the solution template on the basket.

Why This Happens

Solution Definitions can be created in several ways:
- Manual creation through the UI
- Import from another org via JSON export/import
- Deployment through change sets or packages
- Programmatic creation via Apex or API

If a Solution Definition is created without properly linking it to a Schema, the record will exist in Salesforce but will be incomplete. When the basket attempts to load the solution template, it cannot find the necessary schema information and throws the "Solution Template not found" error.

Common Scenario

A Solution Definition record is created as a child/component of a parent Solution Definition (e.g., "Pricing Overview, Fibre Service" under "SIP2 Access and Voice Solution"). The child Solution Definition is created without an associated Schema, causing the error when the parent solution is added to a basket.

Diagnosis Steps

Step 1: Identify the Affected Solution Template

1. Note the Solution Template ID from the error message (e.g., a2w6D0000005XSQQA2)
2. In Salesforce, navigate to the Solution Definition object
3. Query for the Solution Definition:
   sql SELECT Id, Name, cscfga__Schema__c, cscfga__Parent_Solution_Definition__c, CreatedDate, LastModifiedDate, LastModifiedBy.Name FROM cscfga__Solution_Definition__c WHERE Id = 'a2w6D0000005XSQQA2'

Step 2: Check for Missing Schema

1. Review the query results and check if cscfga__Schema__c is null or empty
2. If the Schema field is empty, this confirms the root cause
3. Note the CreatedDate and LastModifiedBy to understand when and how the record was created

Step 3: Check for Child Solution Definitions

If the Solution Definition has child components, check if any of them are also missing Schemas:

SELECT Id, Name, cscfga__Schema__c, cscfga__Parent_Solution_Definition__c,
       CreatedDate, LastModifiedBy.Name
FROM cscfga__Solution_Definition__c
WHERE cscfga__Parent_Solution_Definition__c = 'a2w6D0000005XSQQA2'
AND cscfga__Schema__c = null
ORDER BY CreatedDate DESC

Step 4: Identify the Source of the Issue

1. Check the LastModifiedBy field to see who created the Solution Definition
2. If created by a deployment user or integration user, check recent deployments or imports
3. If created manually, contact the person who created it to understand the intended configuration

Resolution

Option 1: Associate the Correct Schema (Recommended)

1. Identify the correct Schema that should be associated with the Solution Definition:
2. Review similar Solution Definitions in the org to find the appropriate Schema
3. Consult with the customer's CloudSense administrator or product catalog owner

4. Check the source org if this was imported from another environment

5. Navigate to the affected Solution Definition record in Salesforce

6. Edit the record and populate the cscfga__Schema__c field with the correct Schema ID
7. Save the record
8. Return to the basket and retry adding the solution
9. Verify the solution is added successfully without errors

Option 2: Remove the Incomplete Solution Definition

If the Solution Definition was created in error or is not needed:

1. Verify with the customer that the Solution Definition can be safely removed
2. Check if the Solution Definition is referenced by any:
3. Active baskets
4. Product Configurations
5. Other Solution Definitions (as a parent or child)
6. If no active references exist, delete the Solution Definition record
7. Return to the basket and retry adding the solution
8. Verify the solution is added successfully

Option 3: Reimport or Redeploy the Solution Definition

If the Solution Definition was recently imported or deployed:

1. Verify the source Solution Definition (in the source org) has a Schema associated
2. Re-export the Solution Definition JSON from the source org
3. Reimport the Solution Definition to the target org using the "Override Existing" option
4. Verify the cscfga__Schema__c field is now populated
5. Test adding the solution to a basket

Prevention

For Solution Definition Creation

• Use Templates: When creating new Solution Definitions, always use existing working SDs as templates to ensure all required fields are populated
• Schema Validation: Before saving a new Solution Definition, verify that a Schema is selected
• Post-Creation Testing: After creating a Solution Definition, test adding it to a basket to catch missing configuration issues early

For Solution Definition Imports

• Pre-Import Validation: Before importing Solution Definition JSON, verify that all required fields are present, including Schema references
• Post-Import Verification: After importing SDs, run a validation query to check for missing Schemas:
  sql SELECT Id, Name, cscfga__Schema__c, CreatedDate FROM cscfga__Solution_Definition__c WHERE cscfga__Schema__c = null AND cscfga__Is_Active__c = true ORDER BY CreatedDate DESC

For Solution Definition Deployments

• Deployment Package Review: Ensure deployment packages include all required related records (Schemas) along with Solution Definitions
• Post-Deployment Testing: After deploying Solution Definitions, test the full workflow (create basket, add solution, configure, calculate totals) to catch missing configuration issues

For Bulk Operations

• Validation Before Bulk Creation: If creating multiple Solution Definitions programmatically (via Apex, Data Loader, or API), validate that each record has a Schema associated before inserting
• Error Handling: Implement error handling in bulk operations to catch and report missing required fields

Related Information

• Affected Object: cscfga__Solution_Definition__c
• Missing Field: cscfga__Schema__c
• Error Message: "Solution Template (ID) not found on basket"
• Affected Operations: Adding solution to basket, basket initialization
• Common Scenarios: Manual SD creation, incomplete import, deployment without related records
• Related Objects: cscfga__Schema__c, cscfga__Product_Basket__c