Pricing Attribute Value Null or Empty Preventing Save

Problem

When attempting to validate or save a solution in the CloudSense Configurator, an error occurs stating:

"Attribute Value should not be null/empty"

This error typically occurs when pricing-related attributes on product configurations are not populated, preventing the solution from being saved or submitted.

Root Cause

CloudSense pricing attributes that reference price items, add-ons, or price item references require values to be populated before the solution can be saved. These attributes have special field names that end with:
- __PriceItem__
- __AddOn__
- __PriceItemReference__

When these attributes are left empty or null, the validation process fails because the pricing engine expects these values to be present for pricing calculations.

Resolution

Step 1: Identify the Attribute Causing the Error

1. When the error "Attribute Value should not be null/empty" appears, note the context (which product or configuration was being saved)
2. If the error message includes the attribute name, note it down
3. If not, proceed to the next step to identify the empty attribute

Step 2: Review Product Configuration Attributes

1. Open the solution in the CloudSense Configurator
2. Navigate to the product configuration that is causing the error
3. Expand the Attributes section for the product
4. Look for attributes with names ending in __PriceItem__, __AddOn__, or __PriceItemReference__
5. Identify any of these attributes that are empty or have no value selected

Step 3: Populate the Required Pricing Attributes

1. For each empty pricing attribute identified:
2. Click on the attribute field
3. Select the appropriate value from the dropdown or lookup
4. If the attribute is a price item reference, ensure you select the correct price item that matches the product configuration
5. If the attribute is an add-on reference, select the appropriate add-on
6. Save the attribute changes

Step 4: Validate and Save the Solution

1. Click Validate to check if all required attributes are now populated
2. If validation succeeds, click Save to save the solution
3. If the error persists, repeat Steps 2-3 to identify any remaining empty pricing attributes

Prevention

• Ensure that pricing attributes are configured with default values or are set as required fields during product definition setup
• Use attribute rules or validation rules to enforce that pricing attributes are populated before the solution can be saved
• Train users to always populate pricing-related attributes when configuring products
• Consider using attribute templates or pre-populated values for common pricing scenarios