You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When an entity reference is configured to display a name (e.g., addressLine1 for an address entity), the system misleadingly displays a loader if the display name is empty, even though the entity reference has a value. This confuses users as it suggests that the system is still loading data, when, in fact, the display name is simply missing. Additionally, the Quickview incorrectly displays the error message "Quickview not configured properly" even when it is configured properly, but the display name for that entity type is null. This issue occurs when using the components autocomplete with "Use Quickview" enabled and an entity reference.
The table is sorted by address in ascending order to show loaders on the first page.
Observe the loader displayed in place of the display name in the address column.
Hover over the loader and notice that the data exists, but addressLine1 is empty, and take note of the "Quickview not configured properly" error message.
Expected Behavior:
If the display name for the entity is empty but the entity reference exists, the system should display a default/fallback message (e.g., "Unnamed Entity" or "No Display Name").
A loader should only appear if data is genuinely being fetched or processed.
Actual Behavior:
A loader is displayed even though the entity reference has a value, misleading users to believe that data is still being retrieved.
The Quickview incorrectly displays an error message even though it is properly configured.
Suggested Fix:
Fallback Value Display:
Implement logic to show a fallback value such as "Unnamed Entity" or "No Display Name" when the display name is null or empty.
Tooltip/Info Icon:
Add a tooltip or info icon next to the reference, explaining that the entity exists but the display name is missing. This provides additional context to users.
Placeholder Text or Highlighting:
Display placeholder text like "Display Name Missing" or highlight the entity reference in a distinct style (e.g., greyed out) to indicate the incomplete display name.
Conditional Loader:
Show the loader only if the entity reference is genuinely being fetched (e.g., the API request is pending). If the reference exists but the display name is empty, display the fallback text instead of the loader.
Error Message Correction:
Ensure the "Quickview not configured properly" message only appears when the Quickview is truly misconfigured, not when the issue is with the entity’s display name being null.
Attachments:
The text was updated successfully, but these errors were encountered:
Tshepiso-R
changed the title
Draft Display name for Entity Reference shows loader when empty
Display name for Entity Reference shows loader when empty
Sep 17, 2024
Description:
When an entity reference is configured to display a name (e.g.,
addressLine1
for an address entity), the system misleadingly displays a loader if the display name is empty, even though the entity reference has a value. This confuses users as it suggests that the system is still loading data, when, in fact, the display name is simply missing. Additionally, the Quickview incorrectly displays the error message "Quickview not configured properly" even when it is configured properly, but the display name for that entity type is null. This issue occurs when using the components autocomplete with "Use Quickview" enabled and an entity reference.Steps to Reproduce:
addressLine1
is empty, and take note of the "Quickview not configured properly" error message.Expected Behavior:
"Unnamed Entity"
or"No Display Name"
).Actual Behavior:
Suggested Fix:
Fallback Value Display:
"Unnamed Entity"
or"No Display Name"
when the display name is null or empty.Tooltip/Info Icon:
Placeholder Text or Highlighting:
"Display Name Missing"
or highlight the entity reference in a distinct style (e.g., greyed out) to indicate the incomplete display name.Conditional Loader:
Error Message Correction:
Attachments:
The text was updated successfully, but these errors were encountered: