Today’s post covers some programming that is not of my own making. My colleague Andreas Rascher has built a damn cool functionality that allows you to export the dataset of RDLC reports in different formats. Since we think the functionality is extremely useful, we didn’t want to keep it from you.
On the Business Central Cloud, to save a report in PDF format and change its name while saving, you can use a STREAM BLOB through the “Temp blob” codeunit.
Once this is done, use the function then the BLOBExport function present in the “File Management” codeunit to export the report created with the “REPORT.SAVEAS” command, changing its name during saving.
Do you love reports? Personally, NO! 🙂 But that is, as a Business Central developer I think that sometimes (forced or not) you need to work with reports in your solutions.
As a quick recap, in Dynamics 365 Business Central a report layout controls content and format of the report, including which data fields of a report dataset appear on the report and how they are arranged, text style, images, and more.
Damn it. I gave everything to write 10 tips together, but in the end there were only 9. Reports can drive you to despair in AL. While extensions have been available for tables and pages for a long time, we have to be patient with reports until the following screenshot of a report extension becomes reality. To make your life as easy as possible until then, I’d like to share a few tips for developing reports in AL. For some…
Today,I came with widely used feature of business central.Contrary to pages and tables, extensibility is not yet supported for report objects in Business Central. Therefore, if you want to make any changes to the dataset or the layout of a base application report, you must create a new version of the report and apply the changes on the new object.