Comments
Given that there's a display order for a choice column that controls the UI on forms and for filtering a view, it seems strange that ordering in views/FetchXML for choices is alphabetical only.
If this needs to be limited to only one way of doing it, alphabetical seems to me to be the wrong way of doing it.
Absolutely agree and this in important to prevent users inadvertently adding serial or lot numbers that can cause issues with warehouse tracking.
To make it easier for users to understand(there are already a lot of fields on the item tracking setup) I would prefer a option field for the Serial No. Tracking and Lot No. tracking fields of (None, Free-entry, Mandatory).
This would also allow for potentially for fields to be hidden automatically on the item tracking page if lot or serial numbers are prevented making it easier for data entry.
We recently had this issue on an implementation where data entities were not available for detours/mds. It became a massively time consuming task to recreate the steps between environments and would only increase on larger projects. I can see this becoming a bigger requirement in the future as detours/mds are used more often. I believe this should be considered for the roadmap.