This issue occurs due to issues in saving the Runtime Defined Entity (RDE) within the Cloud Director database. The RDE is responsible for saving the customization options.
This is a known issue in VMware Cloud Director 10.5.0 when saving branding theme assets.
Workaround:
To work around the issue, you will need to update the corresponding RDE via the Cloud Director API.
To update the RDE you will need to retrieve the brandingTheme URN.
As the brandingTheme API is an Alpha Feature:
1. Retrieve the brandingTheme Object Reference for the Theme in question.
GET https://{{base-url}}/cloudapi/1.0.0/brandingThemes/ Accept: application/json;version=39.0.0-alpha-1689260915
Truncated Output
{... "values": [ { "id": "urn:vcloud:entity:vmware:brandinguitheme:af85e10a-####-####-####-########492", "name": "My custom theme", ... ]}
Locate the target theme by name and copy the theme urn.
**Optional - You can proceed via the API Explorer if you would prefer**
2. Retrieve the associated Runtime Defined Entity(RDE) object for the Theme in question.
GET https://{{base-url}}/cloudapi/1.0.0/entities/urn:vcloud:entity:vmware:brandinguitheme:af85e10a-####-####-####-########492
Truncated Output
{ "id": "urn:vcloud:entity:vmware:brandinguitheme:af85e10a-####-####-####-########492", "entityType": "urn:vcloud:type:vmware:brandinguitheme:1.0.0", "name": "My custom theme", "entity": { "logo": "logo.png", ... }
3. Modify the RDE Response Body to add a reference to the customLinks.
"customLinks": "<URN from Step 1>_custom_links.json",
Example
"customLinks": "urn:vcloud:entity:vmware:brandinguitheme:af85e10a-####-####-####-########492_custom_links.json",
4. Update the RDE
PUT https://{{base-url}}/cloudapi/1.0.0/entities/urn:vcloud:entity:vmware:brandinguitheme:af85e10a-####-####-####-########492
Truncated Request Body Example
{ "id": "urn:vcloud:entity:vmware:brandinguitheme:af85e10a-####-####-####-########492", "entityType": "urn:vcloud:type:vmware:brandinguitheme:1.0.0", "name": "My custom theme", "entity": { "logo": "logo.png", ... "customLinks": "urn:vcloud:entity:vmware:brandinguitheme:af85e10a-####-####-####-########492_custom_links.json", ... } }
This issue will be resolved in the next release of Cloud Director 10.5.x.
For more information on connecting to the Cloud Director API see the article here, How to establish an API connection VMware Cloud Director (56948).