Start a conversation Sign in
Start a conversation
  1. CloudSense Support
  2. General category
  3. Cloudsense Data Orchestration

Resolving Service Specification Population Issues in Production

Overview

The issue of service specifications not populating correctly was due to `specification__c` records for a specific product definition having their `end_date__c` set to a date in the past, causing them to be skipped. This configuration issue affected multiple services, with only Attribute Details being populated instead of the expected component, pricing, and key details.

Solution

Follow these steps to resolve the issue of service specifications not populating correctly:

  1. Identify Affected Records: 
    SELECT Id, name, csedm__end_date__c, csedm__Active__c  FROM csedm__Specification__c WHERE csedm__Source__c = '<product_definition_id>'
  2. Correct the Configuration: Update the `end_date__c` field to a valid date that ensures the records are included in the generation process. (make sure to check csedm__Active__c flag as well)
  3. Verify Resolution: Attempt to generate the service specification again and confirm that all expected details, including component, pricing, and key details, are populated correctly.

Note: Ensure that all product definitions have correct configuration settings to avoid similar issues in the future.

Frequently Asked Questions

1. How do I know if this issue affects my service specifications?
If you notice that only Attribute Details are populating and key details are coming through as null, you may be experiencing this issue. Check the `end_date__c` field in your `specification__c` records for incorrect values.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Matej Storga

  2. Posted
  3. Updated

Comments