New properties are hidden by default
complete
Naama Ben Oliel Ronen
Goal: Reduce UI clutter and require explicit opt-in to display new properties.
Description:
Set newly added properties to be hidden by default.
Builder/API: Hidden in Entity Details widget and all tables (only meta properties visible).
Table (clicking on + Property): Hidden in Entity Details by default. Visible only in the table where created, hidden in all other tables.
Naama Ben Oliel Ronen
marked this post as
complete
You'll now find new properties hidden by default across all views. When you add one via + Property in a table, it only appears in that specific table — hidden everywhere else. In the Table, click on 'Manage Properties' to display/hide properties.
Scorecard rule properties are also hidden by default.
Your existing setup isn't affected.
Naama Ben Oliel Ronen
Merged in a post:
We should be able to hide scorecard rule related properties from the catalog pages/tables.
Isuri Ranawaka
Like we can exclude normal properties from a catalog/table via the Excluded Properties option, we should also be able to hide scorecard rule-related properties.
Naama Ben Oliel Ronen
Merged in a post:
Optional Control Over Auto-Display of New Blueprint Properties
D
Dan Amzulescu
When new properties are added to a blueprint, they are automatically displayed in the UI by default. We request an option to control this behavior, allowing admins to choose whether new properties are shown by default or require manual activation. This would help reduce UI clutter and improve manageability for large or complex blueprints.
Naama Ben Oliel Ronen
Merged in a post:
Option to Hide New Properties by Default in Page Views
I
Ignas Čiplys
Current Behavior
Any property or score (including rules) added to a blueprint automatically appears under all card widgets within that blueprint’s entity page views.
Issue
I have blueprints with entity page views containing multiple configured cards that group properties for different purposes. When a new score or property is added to an entity, all of those cards are instantly prefilled with the data. This results in unnecessary clutter and confusion across the cards.
Suggestion
Hide all properties by default, as was done under tables (https://roadmap.getport.io/ideas/p/property-exclusion-in-tables). Alternatively, allow the user to choose whether a new property or score should appear under widgets.
A
Anna Persico
When adding a new property to a blueprint, it should NOT be automatically added to existing widgets and views.
Problem Impact
- Extra manual work: Must manually remove the new property from dozens of widgets/tabs where it's not needed
- Easy to forget: Often forget to remove from aggregation widgets or specific tabs
- User confusion: Forgotten properties appear to end users, causing confusion and unnecessary questions
- Poor UX: The default behavior assumes properties should be everywhere, but in practice they're usually needed in 1-2 specific places
Alternative solution:
Add a checkbox during property creation which reads:
"Add this property to all existing views (not recommended)"