Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
We have a client in the US that would like this feature for the newly released Cluster "Putaway" process.
We have a client in the US that would very much like to have this date feature.
Correction.... Should be: Current Transaction Amount is great than / less than 0.00. The symbols were omitted from my original post.
we have 10000 product which means we have to select 10000 lines to set up min-max. would be really good is to upload the min-max on the same table as fixed locations. And replenishment generates from there. which saves lots of manual input.
Really important and useful option to have
You're not alone, I agree on all points.
This is a great idea, I would really appreciate this new feature!
The issue is not the Functionality to loaf the voucher and set the parameter to "Yes". It actually works fine if in the accrual scheme which you setup you select a "New voucher for each accrual transaction".
However, there is a bug in the system when you select "Same voucher for all transactions" in the Voucher in the Accrual schemes setup. Then you create a General journal and apply accrual scheme which uses this setup , post the journal and later try to reverse you get double transaction lines if you select the parameter to show Accruals to "Yes". The workaround to get only the lines you need it to select the parameter to "No". However, this is against the logic of the functionality as in this case you should just see the main transactions.
So really the bug is in the accrual scheme setup in the voucher when you try to use the same accrual scheme" and it carries out to the loading the transactions menu.
Is this on any roadmap atm?
I have been waiting since 2019.
More specifically, we need to be able to search a product based on one or more of its attribute(s), wherever these attributes are generated through the Procurement hierarchy, the Commerce hierarchy or any other one.
Moreover, even if this functionality does exist with Engineering products, we don't want customer to implement engineering products only to have this feature