Property exclusion in tables
complete
Priya Raghu
Current Behavior:
Any property added to a blueprint automatically appears on all tables referencing that blueprint.
Issue:
When new, unrelated properties are added, they show up on all tables referencing that blueprint. This requires Port Administrators to manually exclude these properties. If this step is overlooked, users might see irrelevant properties in tables, leading to confusion and a suboptimal user experience.
Suggestion:
Automatically add new properties to the exclusion list.
Alternatively, add a toggle on tables to manage this behavior.
Hila Kashai
complete
We just released this! Now when you create a new property, the property will not be added automatically unless you create it from a specific table.
Hila Kashai
Cody Dunlap, I merged your feature request into this one. We are currently working on a fix that will help reduce the duplication of titles and identifiers appearing, as well as adding new properties and their behavior across all tables.
Hila Kashai
Merged in a post:
Allow hiding identifier by default
Cody Dunlap
Most of the time the identifier for an entity is a duplicate of the title, but usually less readable because of autogenerated hashes or various casing.
I find myself updated views for all entities in the UI to hide identifiers but it would be really helpful to have an account setting or something that would allow me to hide identifiers by default and only add them in the cases where it's useful to display.
Hila Kashai
in progress
E
Etienne Jacquot
Maybe related, having the ability to block the other automated creation could be useful (so maybe a 2 in 1 feature here ?)
Dudi - Port team
planned
We are currently thinking about ways to improve the experience.
A first version of this feature can be to not add new properties to views automatically.
We would love to hear your thoughts 🙂