Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
i got an error in the Item Arrival Journal , when validating the lines
Locations can be checked only if an inbound dock is specified
i researched and found that the issue is coming from this field Check Picking Location ,
this checkbox was checked, when i removed it , the Error was gone and the issue was resolved.
but now this checkbox is coming checked on all the Purchase Orders being received and on all the Return Sales Order being received
where is it coming from ? given that in all previous Item Arrivals, this checkbox was coming Cleared
where is the setup for this field ?
note that we are using WMS on Sales orders and on Transfer Order, WMS is NOT activated on Purchase Order
appreciate your help, thanks
Check the Journal header. It defaults from there I think. And the journal header, it defaults from the Journal name (Inventory management -> Setup -> Journals -> Journal names, Warehouse management). Presumably, it has become ticked on the Journal name that you use for Arrival Journals.
Guy to the rescue , thanks buddy, that is actually it
but the weird part is why did we just start getting this error , i mean a lot of receiving were done till now with no issue, why did we just encounter this?
Perhaps someone recently changed the setting of the journal name?
Business Applications communities