Comments
I am surprised there is not more of a demand for this feature. With Omnichannel retail becoming more important, and in the interest of maintaining clean data, the POS should help the user avoid creating a duplicate customer account. This should be part of the standard application, like it is in the back office.
In that context perhaps Microsoft could also look into a general approval of the sequencing by being able to setup a kind of advanced sequencing matrix that would enable the user to setup different setup and consider different setup times if one order is sequenced after an other order and in this constellation it required less or even none setup time compared to the case when an other item would be next in the sequence!
This is very sorely missing. It was there in AX 2012. It's somewhat possible now with Edit in Grid. Yes, I know we could use DMF (Import/Export), but COME ON! Super helpful when you only need to update select records. I would even take a separate way if we could do this via OData and CRUD. ;)Example that I have done in the past is to update Packing quantity in the WHSSalesLine table. Have the InventTransId necessary and filter by that.
Surely the underlying database (SQL Server) isn't the cause here because the maximum unless you are using smalldatetime is 9999-12-31. I understand there will be remediation for existing customers that rely on it being 2154 so perhaps you could make this configurable so those customers not wanting to be locked into the artificial limit of 2154 can freely use up to 9999-12-31 as the underlying database technology supports?