-
Notifications
You must be signed in to change notification settings - Fork 11
Description
🙋 Feature Request
😯 Problem to Solve
In the Assets table in SLE there is a capability to group by its "Location" property. A location of an asset could be 2 things:
- A system
- A physical location
Both of those do not guarantee uniqueness of the name. There could be multiple systems with the same name (even in the same workspace!), same applies to physical location. The only unique thing that can differentiate those kind of items is their ID.
This creates the following issue: grouping the Assets table by location will results in assets being grouped under the same system/physical location even if the assets actually have different system IDs/physical location IDs, making it look like they are in the same location, when they're not.
💁 Proposed Solution
The proposed approach is to allow the Nimble table to be grouped by a different property other than the display value. There is already an existing configuration sort-by-field-name. Following the same approach, if we would have a group-by-field-name property, we could then set the ID to that configuration and not the display value.
While it's true that the user would not be able to distinguish between the 2 groups since they have the same name, they would still be able to see that the assets are in 2 distinct locations, and can then look further into what locations are there.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status