Personalized Community is here!
Quickly customize your community to find the content you seek.
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 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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 used Word Layout for documents reports, instead RDLC layout in a project and I found it easy and fast. But on the other side, I don´t see a lot of people using word layout.
So, what is the problem? Is there any important issue that I can´t see? Can anyone share their experiences and issues with Word Layouts?
Thank you very much.
I've also used Word templates a lot for document reports (and an improved Excel buffer for all other new reports. We only used RDLC when modifying existing reports) in a previous job. It speeds up development a lot!
There is a few limitations that one should be aware of:
- If you or an user need to edit the template, you need to have a Word license. You also need to have word on the client to show preview (i think - workaround is to just print to PDF).
- Word layout does not support show/hide expressions (it is not supported by the 3rd party word merger Microsoft are using for NAV/BC). So you cannot let the word template decide which information should be shown or not. This also means that all your pages should be identical template wise (you can control if a field has as value or not in your dataset from NAV/BC, but you cannot show/hide i.e. a field based on another fields value directly in the word template). If you want i.e. your document totals in a frame in the footer on the last page in your document, you cannot do that in standard NAV/BC i think - it will at least show the frame on every pages footer… And you even have to be a bit creative to get that result :-).
- Word layout does not support transfer footers/headers
- You cannot remove a image dynamically - you'll get a grey box (but you can replace it with a 1x1 white dot in your dataset :-) )
There are probably more minor limitations I forgot about... Some you can work around easily and some are a bit harder (I've been involved in creating a post-processing PDF editor in my former work to fix some of it. It just required everything to be printed as PDF for the PDF-post-processer before actually beeing printed...
Thank you very much Gert for sharing, this is I was asking for!!
Business Applications communities