Topics created by Cameron Forward

Thank you for the response Jan!

I was able to fix that here. It will be part of the next release 3.10.1 or 3.11.0. It's not clear when that happens, but you may subscribe to jsreport releases on github and get notified.

Yes, pdfDest should work across appended templates. Please share a minimal playground demo replicating the issue.

Thank you for the info Jan. Yes they are all appended with jsreport chrome-pdf. I'll keep an eye out for it.

Hi,

note the requests from the studio don't store the report output by default.
Do your API requests instruct jsreport to persist the report output?

{ "template": { "name" : "My template" }, "data" : { ... }, "options": { "reports": { "save": true } } }

don't you have a cleanup policy in your configuration?

{ "extensions": { "reports": { // how often the cleanup runs "cleanInterval": "5m", // how much old reports should be deleted "cleanTreshold": "1d" } } }

The debug logs for the particular report should have a line about storing or not storing the report. Like
2021-08-11T08:32:15.787Z - debug: Skipping storing report.

https://jsreport.net/learn/reports

It should come this month.

Yes, that was the idea.

Genius Jan - that seems like a more reasonable approach than me parsing the whole rendered html and getting the count of a class later on back in afterRender() through jquery or regex. With my method, I would have then needed to re-render the html to a pdf

Thank you for the bug report. We may have a regression issue in the latest version. We will discuss it internally.

In every case, the example in the playground now works.
Just refresh with F5.