Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1 Discover 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
It has been recommended for a while online that the Print Preview is the preferred way to print a Dynamics 365/CRM form. Due to a customer request, we have uncovered a bug with V9 that the new multi-select option set fields do not display in Print Preview. Neither the value nor the display name shows. The entire field is simply skipped as if it did not exist on the form.There is also a longstanding issue where quick view forms or embedded grids do not display in Print Preview either, ostensibly because they are script loaded after the initial form load. This is understandable from a technical perspective, but hardly a robust business solution. It would be nice if Microsoft could provide a legitimate "print it as you see it" functionality for Dynamics. The mobile app is currently being re-designed to hopefully improve things, but regardless connectivity is still not ubiquitous in many areas. There are many times when a simple hard copy of a form is the best option.
Thank you for sharing and reminding.
Indeed, this is a bug. I tested it in my environment and this problem has also appeared.
Microsoft has received this bug and is researching it. A related support ticket has been raised.
Currently, Microsoft has analyzed this reason: This is a control specific issue and assigning to controls to do the 1st level of investigation.
We could wait for Microsoft to resolve this bug and provide a solution. I will pay attention to this ticket, if there is any progress, I will reply here.
Hope this helps.
Business Applications communities