Area: UI Issues
Sub-Area: Properties Display
Issue
The Properties tab on a dataset shows a count indicating properties are present (e.g., "1 property"), but when you click into the Properties tab, no content is displayed. This creates a mismatch between the tab count badge and the actual visible properties in the UI.
You Might Be Asking
- Why does the Properties tab show a count but no properties are visible?
- How can I fix the discrepancy between the property count and displayed content?
- Are my dataset properties lost or corrupted?
Solution
This issue occurs due to a frontend bug where the tab count logic and content display logic use different filtering rules. The count includes all structured properties, while the content panel filters out properties marked as hidden.
-
Identify the Root Cause: The dataset has structured properties where the
isHiddenflag is set totrue. These properties are counted in the tab badge but filtered out from the display area. - For DataHub Cloud Users: Contact DataHub Support to clean up the leftover structured property references. Support can re-emit the structured properties aspect with an empty list to resolve the count discrepancy.
-
For Self-Hosted Users: Use the DataHub SDK or OpenAPI to clear the structured properties aspect:
# Using DataHub CLI datahub delete --urn "urn:li:dataset:(, ,PROD)" --aspect structuredProperties # Or re-emit with empty structured properties datahub ingest --config-file clear_properties_config.yml -
Alternative Workaround: If you want to make the hidden property visible, update the structured property definition to remove the
isHidden = truesetting through the DataHub UI or API. - Verify the Fix: After cleanup, refresh the dataset page. The Properties tab should either show no count badge (if no properties exist) or display the correct count matching the visible properties.
Additional Notes
This is a known product regression introduced when the dataset summary tab feature was added. The count badge logic was implemented without accounting for the existing isHidden filter that was already in place for the Properties tab content. The underlying property data is not lost - it's simply a display inconsistency between the count and content filtering logic. For DataHub Cloud customers, this type of metadata cleanup requires backend access that only DataHub Support can provide.
Related Documentation
Tags: properties, ui-bug, dataset, structured-properties, count-mismatch, frontend, display-issue, tab-content, metadata-sync, cloud-support