Microsoft Dynamics 365
Support for CE would be great!
Highly Requested Feature.
FEFO and Round up to full LPs already exists, so please replicate for FIFO
Hey Chery, we can be able to monitor the offline status of registers from HQ, you just have to enable the feature "Modern POS offline monitoring" from Feature Management. Which covers most of your requested features.
This really affected us at first when all the registers got deactivated in an instant cos the token expired :(
That's a great idea!
It's a great idea and very important to print G/L entry information
Thank you @Jaroslaw highlighting very important issue for handling batch tracked items at Dynamics Moder Point of Sales (MPOS) for Retail businesses. I would second the proposed solution and case statement you have provided in the idea above.
In my view point...
“This is not good for MS to provide an ad-hoc solution to its customers for batch tracked item. In order to deal with Retailers using batch enabled items at MPOS, the solution should be complete in all possible aspects. Presently Retail Sales posting process is not working correctly for both sales scenarios that you have correctly documented in your email. I also hope MS team should also understands the quantum of issue from retail business perspective that is using batch enabled items. The volume of issues in retail would be quite high and it’s not possible either for MS Partner/MS Support team to support customer to keep customers business running and neither customer’s ERP/ operations team can be held responsible to clear batch related errors for return sales manually or manage new/unnecessary batch numbers created by retail statement posting process in D365FO. The D365FO application design should be fixed to match with requirements/scenarios of batch enabled items handling just like it does for back office operations.“
I would also encourage others from the industry to vote your idea..
When a default value for a product attribute is set in a retail product hierarchy node, it overwrites the default value for the same product attribute in another retail product hierarchy node when the product attribute is assigned to the same product attribute group.To solve this, Microsoft advises to create different product attribute groups when you want to set different default values for 1 and the same product attribute. As my customer has 100 values, and wants to set 80 different defaults, I now have to create 80 different product attribute groups which is a bit crazy. Please vote for my idea!
Hi I raised this again separately and it was declined as a duplicate. The reason I raised it again was due to the typo of variant in the title ("Varinat") which meant it didn't come up in my search when looking if one already existed. Imagine it will get more traction if that is corrected so others can find it?