on
RE:
Fully agree.
RE:
As D365 F&O users we required this feature on high priority, according to Indian tax act this ISD process is made mandatory from April 1st 2025.So we expect this feature from Microsoft to be released soon, instead giving some workarounds. Please treat this on high priority.
RE:
We are experiencing errors in the Statement posting batch job when statements have no lines.The statements are inspected in the form "Retail and Commerce" > "Channels" > "Stores" > "Statements". All empty statements must be manually deleted before the batch job can be completed without errors.
RE:
Need this. Too much spam or easy to mistype when doing the pre convo survey
RE:
Until MS provides an alternate option. As a workaround, you can default a dummy dimension on Netting Journal. Because the netting transactions are reversed in this process, so there is no impact on dummy dimension and original invoice is settled with same dimensions which are there on invoice.
RE:
You can see how fast the System could react if you are using the tablet client, way less resources (and cpu power) needed. I don't understand why no one is complaining directly to microsoft...
RE:
We have the same issue too with multiple clients. The clients have no requirement for catch weight but do want to be able to export on hand information by inventory status. It is particularly annoying that this entity requires catch weight when there is a separate set of entities specifically for outputting on hand information with catch weight.
RE:
There are other issues as well, like the revision number mismatch between the Agreement Booking Setup and the Booking Dates, which I am not sure why it's happening, but that's stopping WO generation, too. The workaround I followed was to change fields like pre/post flexibility date that trigger the booking dates generation.
RE:
Voting for this and adding a potential bullet point;I've had numerous process manufacturing clients that wish to validate 'built in quality' on production operations. Many of these also use PFE. A quality association where a result must be validated Before a job can be started would be a huge benefit for this configuration. In this case there is no inventory blocking, but only action blocking on the associated order/job (can't start). If this could be setup and then results input from PFE for the job it blocks, this would be a slam dunk.
RE:
I agree that this is an issue. I've had multiple clients complain about it.