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 have a weird error when using SAVEASPDF for a report I created. When I run the report from the client and go in preview everything works fine. Also printing and saving as PDF via client works well. But when I use SAVEASPDF from code, i always get the following error: "Rendering output for the report failed. Error HRESULT E_FAIL has been returned from a call to a COM component." (I hope thats the correct error message, because I get it in german and used other posts as a source for the english version).
So, when I print the report, use preview or save it as PDF via Client everythings fine, but the following (test-)call fails:
REPORT.SAVEASPDF(50051, 'C:\temp\test.pdf', SalesShptHeader);
The report contains a barcode (font "Bar-Code 39"). When I remove the barcode, save the report and run the above code again it works. But the customer needs the barcode on the report.
Do you have any ideas on how to solve/workaround this? The used NAV versions is 2015 CU24.
Business Applications communities