even though Location is added to the Transfer Order Line, when we do the "Receieve" operation, the Location is empty on the ParmLine, which then throws the error that the Location has to be set.
I have debuged the code and can see that the InventDim that is assigned to the transfer lines do have the wmsLocationId and when the ParmLine is being created, it uses the method from InventDim called "clearNotSelectedDim", which clears out the location from InventDim and then with InventDim::findOrCreate method, another inventDimId is assigned to parm line which does not contain the location.
But I do not understand the logic why it does "clearNotSelectedDim" and what does that mean. If I go with the name it kinda means if location is displayed or not. in opur case it is displayed.
There is no customization in this area and no ISV.
Hi, You're absolutely right to look into clearNotSelectedDim() — this method is designed to clear out any inventory dimensions that aren't actively selected on the Dimension Display settings. So, even if the wmsLocationId is technically present on the InventDim, if Location is not an active dimension in the context, it will be cleared. Now coming to your scenario:
Even if Location is assigned on the transfer order line, it won’t automatically flow into the ParmLine during receipt unless the transfer registration is performed.
This is because D365 expects you to explicitly register the receiving location via Transfer order registration (Inventory management > Inbound orders > Transfer order > Registration).
Without this step, the system doesn’t assume where you’re receiving — even if a location is shown — because actual receiving logic expects confirmation through registration or arrival journal.
✅ Suggestion:
Try doing a transfer order registration before performing the receive step.
This will properly assign the expected wmsLocationId to the ParmLine and resolve the error.
Hope that helps — let us know if this works for you.
Thanks,
Zain
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.