Forum Discussion
Print and/or export to PDF from PowerBI Embedded Report
I've been banging my head against Power BIs inability to export natively to PDF for some time.
What we have done is to utilise AWS Lambda functionality to run Chromium into which we embed the report and save that to S3, served back to the customer as a download.
It's a faff, annoying, but works quite well
https://github.com/sambaiz/puppeteer-lambda-starter-kit/blob/master/README.md
I'm pretty sure you could adapt this for Azure Functions too....
- Nonsensely7 years agoAdvocate I
Thank you Stuart!
We do not run AWS, but I forwarded your response to my boss, who knows our systems and configurations. It would be awesome to get this thing running!
Regards,
Nancy
- kk00366 years agoHelper I
We are running into the same issue on our end. We have external users in the web application and we want to migrate them off of that into an embedded ISV solution, but we can't afford to lose the export to pdf option that the web service offers. Any ideas or thoughts about this issue would be greatly appreciated.
- stuartb6 years agoFrequent Visitor
Firstly I just want to say that Microsoft seem to missing a trick - the paperless office is a myth and virtually all our customers want the ability to print (some A3/A2 size) Management reports. I managed to use the above project using NodeJS to facilitate printing by automating Chromium in a way similar to the link I posted earlier. As Microsoft are creating a browser based on this technology (see: Dev Edge) I don't think this deviates from most peoples concerns of browser compatibility issues - for example; CSS styling across browsers. So I'm guessing you could automate that if you needed to.
In essence what I did, was write this as a Serverless Function (AWS LAmbda in my case) using with entry point taking HTML (or DOM document) with the Power BI Token and config already embedded. It was just a case then using Puppeteer to create a page, inject the given document and export it as PDF (to a persistent file - though returning a file stream is equally valid). We did notice some issues with CSS - some fonts were too small and we had to manipulate some styles to get the printing 'just right'.
In testing we found this to be scaleable and performant. Scaleability was achieved by being serverless; horizontal scaling and not having to care about the number of Chromium instances being created. Performance was suprisingly quick - most functions took less than 5 seconds, that's including loading and running chromium and the overhead of API calls to api.powerbi.com to render the reports in web page.The obvious thing here is that it requires development knowledge in order to create this. This is not something that can be done by a standard 'business team' - Microsoft should be able to offer this functionality relatively easily, but I guess it a case of priorities?
- Kvotava6 years agoFrequent Visitor
I am running embedded powerbi in puppeteer in aws lambda, but I am getting hung up on knowing when the report is done being rendered. How do you wait for the report to finish, so you know its time to create the PDF (or whatever). Currently I am sleeping, but I am trying to find a better solution to that. I did try to hook into the "rendered" event, but I can't seem to get that to fire.
I also did hook up to the public preview of this feature, but the restrictions on it are far too great to be viable.
Any insight would be greatly appreciated!
-Kenny
- stuartb6 years agoFrequent Visitor
Hi
Firstly kudos to the person/site that set me on the right track: https://www.sambaiz.net/article/132/
Secondly, it's been some time since I did this and we've changed the design from using Node to Pupeteer Sharp
Hope the following helps, it's a code snippet of the funtion that I used to embed the report. Note it's not code complete nor would I suggest it's production ready! In essence all it does is wrap up the "embed" call in a promise and only then create the pdf.Note: thee is a 'wait' in the code - I don't think I hooked up to the render with my prototype; just assumed that the API woudl render in less than 5secs. I know we did change this to something more robust, but I dont have access to the codebase for it as I no longer work on the project.
exports.exportPdf = async (browser, pbi) => { const magic = Math.floor(Math.random() * 100000); const filename = 'report-' + magic.toString() + '.pdf'; const localPath = '/tmp/' + filename; loggit('>> generated filename: ' + filename); const pageHtml = '<!DOCTYPE html>' + '<html>' + ' <head>' + ' <meta charset="utf-8" />' + ' <title>Printed PDF</title>' + ' <style> #reportContainer { height: 750px; width: 100 %; max-width: 1000px; } </style>' + ' </head>' + ' <body>' + ' <h1>Report</h1>' + ' <div id="reportContainer"></div>' + ' </body>' + '</html>'; loggit('>> new page'); const page = await browser.newPage(); loggit('>> generate filename'); await page.addScriptTag({ path: './powerbi/powerbi.js' }); await page.setContent(pageHtml); loggit('>>>Power BI stuff'); await page.evaluate((a, b, c) => { const models = window['powerbi-client'].models; const config = { type: 'report', tokenType: models.TokenType.Embed, embedUrl: a, accessToken: b, id: c, permissions: models.Permissions.Read, viewMode: models.ViewMode.View, settings: { filterPaneEnabled: false, navContentPaneEnabled: false } }; powerbi.embed(reportContainer, config); }, pbi.EmbedUrl, pbi.EmbedToken.token, pbi.ReportId ); loggit('waiting'); await page.waitFor(5000); loggit('exporting pdf from chromium'); await page.pdf({ path: localPath, format: 'A4', landscape: true }); loggit('reading pdf'); const aws = require('aws-sdk'); const s3 = new aws.S3({ apiVersion: '2006-03-01' }); const fs = require('fs'); const pdf = await new Promise((resolve, reject) => { fs.readFile(localPath, (err, data) => { if (err) return reject(err); resolve(data); }); }); loggit('writing pdf'); await s3.putObject({ Bucket: 'a-stu-bucket', Key: filename, Body: pdf, }).promise(); loggit('closing page'); await page.close(); loggit('returning'); return filename; };