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 Timeline
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
So I added new document type as described here and here. The procedure seems to be quite simple and consists of 3 basic steps:
After all this is done, one will be able to create new print destinations for the chosen document type in the Order print management form like so:
The problem that I'm having (which not used to be the case before, apparently) is that the record created in SalesPrintSetup table has DocumentStatus field empty:
If I post-populate it with the value I need, then print destination is not being shown in Order print management form.
It works for all other document types, even newly created ones a while ago. Just no new doc. types seem to work neither for purchases nor for sales.
What am I missing here?
Thank you, guys!
The issue was messed up enums that got wrong ids assigned by AX. So, for example, if id assigned to enum value is 15 in front-end, in form queries it comes up as 255.
Business Applications communities