on
RE:
I don't understand why companies are being encouraged to adopt Planning Optimization while deprecating classic MRP, yet a vital process like Intercompany is being removed in the transition. This decision seems completely illogical! At the Dynamics Community conference, Microsoft speakers explicitly advised transitioning to Planning Optimization due to the deprecation of classic MRP, yet they failed to mention that this shift would come at the cost of losing Intercompany functionality. With over 20 facilities worldwide, my company heavily depends on Intercompany operations. We are embarking on the migration from on-prem to the cloud, believing that this move, along with Planning Optimization, would resolve our MRP performance issues. Now, we’re realizing it’s not that simple. Planning Optimization may work well, but only if Intercompany isn't part of the equation.If I am missing something or there are future plans within the Microsoft roadmap, then please let us know. My company must have Intercompany included in the functionality of Planning Optimization.
RE:
The same is in Project management/Projects/All Projects/Journals/Fee,Hour,Item,Expense.
RE:
Hello Jonathon Nelson,Has this feature been implemented?
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.