The api/report expects just JSON.
How the blob would be useful? Don't you need to anyway parse it then so you can loop over it?
However, you can use beforeRender script to actively fetch the data as you want and process it as you want.
https://jsreport.net/learn/scripts
Open your package.json, update the dependency jsreport to the 2.10.0, and hit npm install.
However, the 2.11.0 is the last v2 version and should be the most stable.
You can implement the pdf utils operations problematically inside scrips. Check the documentation. This opens many approaches to you.
https://jsreport.net/learn/pdf-utils#usage-in-script
Perhaps the simplest is just to use removePages to remove the first page.
https://playground.jsreport.net/w/anon/plnz68al
const jsreport = require('jsreport-proxy')
async function afterRender (req, res) {
res.content = await jsreport.pdfUtils.removePages(res.content, 1)
}
This error means that the client actually closed the connection before the report finished.
You can either look at the client/network why its closing the connection, or use the async reports that doesn't require client to wait for the end
https://jsreport.net/learn/reports#async
Did you try to use a more powerful HW? Don't you have some resource limits applied with kubernetes/docker... ?
If its possible, you can email me the workspace with the replicated crashing scenario and I can take a look. However, Chrome is black-box for us. We just typically try to remove styles and parts of the template to identify the minimal part causing the chrome crash and then think if it can be replaced with something else without big impact on the output.
The license key you are trying to use isn't in our licensing db.
Please email me some details, what email did you use for purchase?
Can you forward the email with the license?
How does this relate to jsreport?
Please update to the jsreport.Local@2.3.2.
There was a regression issue which I've just fixed.
I apologize for the problems.
Yes, we aren't parsing those environment variables as bools so the mssql package complains because those are strings.
Could you try to pass the uri with those configs if that helps for now?
extensions_mssqlStore_uri=Server=localhost,1433;Database=database;User Id=username;Password=password;Encrypt=true