Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
This is a very urgent matter for us. During lifecycle of partnumber, tracking dimension group can change adn customer do not accept a new part number to implement this. So the function to change is vital.
Same for me, my vote is not registered for some reason?
This website doesn't register my vote, for whatever reason. Counter was at 10 before, still is. Aside from this: Why was it removed? "Location Code" is in the value entries, so you can group by location. Which is a regularly used feature.
This would be a helpful addition for our retail operation as well.
Barcode printing is of greater importance than phone scanning. Right now we can't get consistent barcode printing on forms or labels for our manufacturing and distribution clients. High volume label printing is a real problem. We can manage Code 39 fairly well, but UPC labels are a real challenge.
The requirement for branch offices should be handled by Responsibility Center. That way the responsibility center of the user/document should be the from address.
All of this should of cause be available via Events to cater for the special customer requirements...
This is a stock standard accounting feature that small businesses expect to work out of the box in Australia. Importing manually via CSV is not an adequate substitute for this functionality. This is THE most important feature that needs to come to BC in Australia
Fantastic to see this. It would be great if we start to see a synchronisation of ledger entry descriptions and posted document descriptions. i.e. If you can change one it would reflect back into the document. Like due date on customer / vendor ledger entries it doesn't make sense that the ledger entry is edited, but not the originating posted source document.
If you really implement this, please do also allow proper access to the standard CSS (and publish a document describing the correct usage) for custom controls (controladdins).
Rebuilding the look and feel of standard controls is already a pain in the a**.
can you please update docs.microsoft.com with the answer