RE:
This appears to affect all buttons.If the default state has any of bold, italic or underline selected it applies the same to all states even if deselected for other states.If the default state has any of bold, italic or underline deselected, the other states can have them selected and they work in practice.
RE:
Dear Microsoft team, Could you please clarify why this function is still not available or planned for future releases? This is a basic standard feature to disable or hide a retired payment method, which is typically available by default in other POS software. As highlighted in the Microsoft ticket, the absence of this feature is causing problems and errors in our retail operations.
RE:
Dear Microsoft team,Do let us know if / when this will be available, thank you
RE:
It is released to Excel 365 Insider also. High time, it should be rolled out to PQ as well.
RE:
Honestly, it really costs credibility in the eyes of our SMB customers (not working 24/7) if weekend or public holiday due dates occur despite correct calendar entries have been set up.
RE:
A gap we have experienced as well and would like to have a configurable option for.For now, we have solved it be restricting the storage to only allow material of a single expiration date in a flow rack lane, and then using the Expiration date to calculate the pick order from the rack. This is quite restrictive in regards to the space in the warehouse.
RE:
This would be super helpful - spend way too much time copying and pasting code, feels a bit backwards for this not to be a feature in 2024.
RE:
It would be nice if all other languages have the same shortcuts like the English version, so if you switch languages you have still the same shortcuts
RE:
Part 3 due to character limitation:Problem 2 - it is not user friendlyAs Laeticia Cunah already mentioned, it's absolutely a waste of time if user has to set it manually. Additionally, it would prevent user errors due to selecting wrong bank code manually. In my opinion a modern ERP-System should support users instead burdening additional work. SolutionAs already mentioned Dynamics should try to set bank code automatically in pruchase invoice if a QR-Bill is scanned and therefore IBAN is known. If on vendor a corresponding bank code with that specific IBAN is missing, bank code should be empty and an info message should be shown. Preferred bank account should only be used if there is no IBAN provided!
RE:
Part 2 due to characater limitation:Problem 1 - Preferred bank account code is always usedWe can set a preferred bank account code on a vendor. When we scan a QR-Bill, IBAN is set correctly in purchase invoice. But instead to set the correct corresponding bank code, it sets the preferred bank account code. Effect: user does not recognize a wrong bank code is used and payment is done on wrong IBAN. This has already led to problems with vendors. As i mentioned above - with this functionality Dynamics supports/produces actively failures! To be honest, in my opinion this problem is more a bug than anything else and it would be easely fixable when it would automatically set corresponding bank code or throw an info message if no corresponding bank account code is defined on vendor. Futhermore, i do not understand why it should work when using "purchasing entry journal" - but it does not when using "purchase invoice". It's somehow inconsistent functionality inside Dynamics itself. I would really appreciate if there is a clarification about that behavior. Do you know about that problem?