Attribute value Field Not Displaying on Profile UI

Issue Summary

In the US DEV environment, the Website / Website URL field stopped displaying values in the Profile UI, even though it had previously been populated for existing records.

Users observed that the Website value appeared blank in the UI, despite the customer having made no recent configuration changes.

Symptoms

• The Website field appears blank in the Profile UI.

• Previously populated records no longer display the Website value.

• Updates to the Website field from the UI fail or produce inconsistencies.

• HAR logs show an incorrect attribute structure being sent during updates.

Root Cause

The issue was caused by a misconfiguration in the L3 schema for the nested attribute "Website".

Specifically, the child attribute name contained a space (Website URL) instead of the expected API attribute name (WebsiteURL).

Because of this mismatch:

• The UI and API generated payloads using Website URL

• The entity schema expects WebsiteURL

• This caused the payload to be incorrectly structured, preventing the value from displaying properly.

Incorrect Payload Observed

HAR logs showed the following payload during entity updates:

[
  {
    "type": "INSERT_ATTRIBUTE",
    "uri": "entities/2fvFxZt/attributes/Website",
    "newValue": [
      {
        "value": {
          "Website URL": [
            {
              "value": "https://resmed.com"
            }
          ]
        }
      }
    ]
  }
]

Problem

The nested attribute key Website URL does not match the schema attribute name expected by the API.

Correct Payload Structure

The correct payload should reference WebsiteURL (without a space):

[
  {
    "type": "INSERT_ATTRIBUTE",
    "uri": "entities/2fvFxZt/attributes/Website",
    "newValue": [
      {
        "value": {
          "WebsiteURL": [
            {
              "value": "https://resmed.com"
            }
          ]
        }
      }
    ]
  }
]

Incorrect L3 Configuration

The L3 configuration defined the nested attribute with an incorrect name:

{
  "label": "Website URL",
  "name": "Website URL",
  "type": "URL",
  "uri": "configuration/entityTypes/HCO/attributes/Website/attributes/WebsiteURL"
}

Correct L3 Configuration

The nested attribute must use the correct API name:

{
  "label": "Website URL",
  "name": "WebsiteURL",
  "type": "URL",
  "uri": "configuration/entityTypes/HCO/attributes/Website/attributes/WebsiteURL"
}

Resolution

1. Updated the L3 configuration for the nested attribute.

2. Corrected the attribute name from Website URL → WebsiteURL.

3. Verified that the payload generated by the UI matches the schema.

4. Performed a cumulative update with the corrected payload, confirming the Website value displays correctly.

Validation

After correcting the configuration:

• The UI successfully displays the Website URL value.

• Entity updates generate the correct payload.

• No further mismatches occur between UI updates and API schema.

Best Practices / Prevention

1. Avoid Spaces in Attribute Names

The name field should match the API attribute identifier exactly and should not contain spaces.

Use:

WebsiteURL

Avoid:

Website URL

2. Ensure Schema Consistency

Ensure that the following fields are aligned:

• L3 attribute name

• Attribute URI

• API payload keys

3. Validate UI Payloads Using HAR Logs

If UI values fail to display:

1. Capture a HAR file

2. Inspect the update payload

3. Verify that attribute keys match the schema attribute name

Key Takeaway

A mismatch between the nested attribute name in L3 configuration and the expected API attribute name caused the Website field to not display in the UI. Correcting the attribute name resolved the issue.