A lookup's display order is not unique
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
The refdata and IAM lookups carry display_order with a default of zero and no uniqueness. Two rows with the same order read in an undefined order. Add a unique index per list, or state a tie-break by code. The web screen sorts by order then code as a stopgap.
2. Why
Lists reorder themselves between reads when two rows share an order.
3. References
- Journey: Maintain a classification list, gap 3
- Journey: Tune the tenant, gap 2