Conditional base rates in pricing card are not listed in the GET API response and cannot be updated via the PATCH API endpoint

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When interacting with the VMware Aria Operations Suite-API endpoint `/api/policies/{id}/settings`, users may encounter the following issues regarding storage slabs/pricing settings:

 

1.  Missing Fields: The `conditionalBaseRates` field (and its associated values) is missing from the JSON response body when performing a `GET` request, even if the values are visible in the Aria Operations UI.
2.  Settings Cleared: When performing a `PATCH` or `POST` request to update policy settings, if the `conditionalBaseRates` field is not present or correctly serialized in the payload, the existing pricing slabs/conditional rates are erased or reset to default values in the UI.
3.  No Error Code: The API may return a `204 No Content` or `200 OK` status, falsely indicating a successful update despite the data loss.

Environment

• Product: VMware Aria Operations 8.18.x
• API Endpoint: `/api/policies/{id}/settings`

Cause

This issue is caused by a product defect where the `conditionalBaseRates` field is not correctly handled by the API serialization layer. The field is essentially ignored during the `GET` call and is not properly merged or preserved during `POST`/`PATCH` operations. 

Resolution

This issue is under investigation for a permanent fix in a future product update. 

Additional Information

Workaround: Policy Export/Import Method

 

If the API cannot correctly preserve the `conditionalBaseRates`, use the manual export/import method to force the system to recognize and retain the correct pricing configuration.

 

1. Create Policy in UI: Navigate to the Aria Operations UI and create a Policy with the desired conditionalBaseRates slab information
2. Export the Policy: Export the Policy as an XML file
3. Extract Mappings: Find the relevant section(s) concerning the desired conditionalBaseRates and extract from the XML
4. Insert into Desired Policies: For any policies which are missing this information, export, insert the extracted XML and then import