You’re offline. This is a read only version of the page.
Announcements
67
We are in the process of migrating from AX2012 R3 to D365 FO cloud. We operate a selling company using direct delivery from two other companies in our environment. Process steps relating to releasing products below.
During our migration we encountered above issue releasing products both via Data Management integrations and directly in the Web Client. It appears something has changed in this area between AX2012 R3 and D365 FO (App release 10.0.29) and we wondered if anyone knew the purpose or planned steps so we can assess our next steps?
Our developers identified new validation on EcoResStorageDimensionGroupItem table under the method validateStorageDimensionGroupIsSameAsInProduct, and coded a bypass to facilitate the upgrade.
Since we have thousands of products/orders with this configuration we wondered if anyone knew the purpose of the change so we can establish next steps and if we need to prepare a post go live change to align with some best practice?
AX2012 Process Steps:
The SO is created in the Selling company with Direct delivery enabled and auto-creation of the associated PO/SO. Everything has been working fine. If we were to turn off this validation (through extension) what implications might be encounter?
Thanks
Hi Colby
Thank you for the response, we did proceed to try your described process shortly after we posted, which resolves one part of the issue. Allowing initial creation and release to selling company (which holds no stock), however when releasing to the manufacturing company where we do utilise advanced warehouse (WHS), we then see ‘It is not allowed to set warehouse management information for items that do not use warehouse management processes’ when we attempt to configure the various dimensions related to advanced warehousing (again not seen as an issue in AX2012 R3). We are testing process on 10.0.29.
thanks
Joe
The way I see the validation in method EcoResStorageDimensionGroupItem.ValidateSTorageDimensionGroupSameAsInProduct is that if there is a storage dimension group set on the product, then the released product must have the same dimension group. Rather, leaving the product's storage dimension group blank / undefined gets around this logic and allows the process you outlined above. I've always followed this process of leaving the product's storage dimension group blank precisely for the scenario you outlined above, where it needs to be different in two legal entities.
I don't see that 10.0.27 or 10.0.30 work any differently than what I describe above, both by looking at the code and recreating your scenario in the front end. Can you advise what version you are on? If the product and released products storage dimensions must always match exactly, I would raise that as a bug to Microsoft.
Hi Jerhsysacct,
Please wait for someone more experienced in this area to answer this question.
Best Regards,
Charlotte
#1
André Arnaud de Cal...
294,075
Super User 2025 Season 1
#2
Martin Dráb
232,860
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
