Symptom
When Effective Date is changed with Quick Search filled, wrong product version is retrieved in configurator.
Environment
SAP CPQ
Reproducing the Issue
- Create a quote
- Set the quote Effective Date to a first date that corresponds to product version A
- In Quick Search on the quote, enter a term to locate a versioned product and open its configuration, verify that it is product version A
- Go back to the quote.
- Without clearing the Quick Search input, change the Effective Date to a later date that corresponds to product version B
- Open the configuration from the existing Quick Search result
- Observe the configuration still reflects data from version A instead of version B
- Go back to the quote, clear the Quick Search input, and re-enter the same term
- Open the configuration and observe it now reflects version B.
Cause
Bug
Resolution
- Issue:When entering a word in quick search input field on quote, API endpoint {tenantUrl}/api/rd/v1/Catalog/GetQuickAdd is called. However, after changing quote effective date, the value in quick search input field wasn't erased, nor was the above mentioned API endpoint called, and so the same result was kept for the quick search field, leading to wrong revision after changing effective date.
- Workaround: Reenter value in the quick search field in order to call once again the API endpoint to retrieve correct data
- ETA: Still not available.
Keywords
quick search, effective date, product version, bug, CPQ , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Known Error
Product
SAP CPQ 2024
SAP Knowledge Base Article - Public