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
For cardinality-n cards, tiles can be sorted at the card level for a given resource. This is important for things like resource descriptors which derive the resource display name from the tile with the lowest sort order if using a cardinality-n card.
Currently, the Bulk Data Manager import modules do not have a way of explicitly controlling the tile sort order for tiles being imported. The current behavior is to initialize tiles with a sort order of 0, and leave any sorting to the front end (if any).
The primary goal should be to enable the ability to control sort order while creating new tiles through the bulk data importers. There should be discussion around how to handle new tiles that are not explicitly given a sort order provided in the imported csv/excel.
The text was updated successfully, but these errors were encountered:
johnatawnclementawn
changed the title
Feature: Capture tile sort order during bulk import modules
Capture tile sort order during bulk import modules
Aug 28, 2024
johnatawnclementawn
changed the title
Capture tile sort order during bulk import modules
Capture tile sort order during bulk import
Aug 28, 2024
For cardinality-n cards, tiles can be sorted at the card level for a given resource. This is important for things like resource descriptors which derive the resource display name from the tile with the lowest sort order if using a cardinality-n card.
Currently, the Bulk Data Manager import modules do not have a way of explicitly controlling the tile sort order for tiles being imported. The current behavior is to initialize tiles with a sort order of 0, and leave any sorting to the front end (if any).
The primary goal should be to enable the ability to control sort order while creating new tiles through the bulk data importers. There should be discussion around how to handle new tiles that are not explicitly given a sort order provided in the imported csv/excel.
The text was updated successfully, but these errors were encountered: