Topics created by AB-D

Hi @bjrmatos that worked, thank you

I apologize for not mentioning the actual typo. You got it right then.

{{#xlsxReplace "xl/styles.xml"}} {#asset style.xml} {{/xlsxReplace}}

This is actually older v2 syntax. Its still compatible with v3, but now we use the following
https://jsreport.net/learn/assets

{{#xlsxReplace "xl/styles.xml"}} {{asset "style.xml"}} {{/xlsxReplace}}

However, virtually identical files with the extra curly bracket will also work.
It also does not explain why the same file was working locally but not on the test server

I have tried replicating the issue and getting some hypotheses why it works for you on one server and not on the other, but unfortunately, I don't know.

So it does, thanks for the confirmation

We don't know how to do that.
The pdf.js, browsers use to display pdf, guess the file name from the url, but in the case of displaying pdf from javascript blob object, there is no way to adapt the url.
https://stackoverflow.com/a/31990944/1660996

What you can do is use synchronous jsreport.openInNewWindow or jsreport.download which uses form submit, in case you use the browser client.

In case you fetch the pdf from your app server, just do a post to the iframe with url ending http://yourapp/some-path?desiredFilename.

Or you can try using your own https://mozilla.github.io/pdf.js/ instead of letting the browser display the pdf.

We will appreciate is anyone will find out some way out of this so we can document it for others.

The reports aren't running likely, just the profile information wasn't updated.
This can happen when the process is stopped forcibly and running reports don't get updated. We will add some logic to clean such profiles. https://github.com/jsreport/jsreport/issues/1006

Now you can just ignore such old profiles because they get rolled out anyway shortly. jsreport keeps just 1000 last profiles by default.

hi! such warning about the invalid source map was fixed since jsreport 3.7.0, which version do you use? perhaps you just need to update to latest version.

Just FYI I got around this issue by creating a asset js file and just importing that as an asset into the script. So it is not urgent.

Hm, this only happens to me when I have there the old jsreport-cli globally installed.
Don't you have a package.json or node_modules somewhere up the tree?
Didn't you install also jsreport binary and have it somewhere?

Could you try in a different folder to run the common install steps?

npm uninstall -g jsreport-cli npm install @jsreport/jsreport-cli -g mkdir jsreportapp cd jsreportapp jsreport init jsreport configure jsreport start

This is more a general docker question, but you can find some notes from us here
https://jsreport.net/learn/docker#install-custom-modules

Please upvote here, we will try to get to it soon when there is growing interest in it.
https://github.com/jsreport/jsreport/issues/1038

https://github.com/jsreport/jsreport/issues/540

The docxtemplater recipe unfortunately doesn't support a custom parser.
We decided to focus rather on our docx recipe implementation.
Feel to fork the jsreport-docxtemplater repo and add what you need.

The official jsreport docker image? Which version?
Do you allocate enough physical resources to the container?

hi @AB-D we were not aware, but now that you mention it probably makes sense that it work this way because each cell has its own style rules, nothing is shared, so the styles will grow proportionally to the number of cells that the file has. how many cells are you producing that you end up with a 10mb of style? this is probably an optimization we had to do later, it will take a while

You have likely a bigger asset and it timeouts during diffing the long text.
We are currently working on replacing the string diff library that is the bottleneck.
Until we release this, you can try to increase the reportTimeout config.

With the 2.8.0 there is a default timeout 60s.
You can see it in the output

2020-11-09T11:35:23.926Z - info: Using general timeout for rendering (reportTimeout: 60000)

If you want to increase it, you can use the environment variable

docker run -p 5488:5488 -e reportTimeout=120000 jsreport/jsreport:2.8.0

When you are still getting the timeout afterward, you may be hitting one bug we fixed recently. You can try to install the patch using

npm i jsreport-html-to-xlsx@2.8.1 --save

When developing on my local environment, the automatic reload/render when the template content changes is good, however, is there a setting to make it so that the reload/render will only occur when I save the file?

Do you mean when you hit save in your desktop IDE? This is how it should work already.
We monitor the file changes, and when you edit we do the reload/render.

You can reach me at jan.blaha@jsreport.net

btw jsreport now has a built in toJS helper to do this
https://jsreport.net/learn/templating-engines#tojs-data-

I attempted to delete the template using the API (using postman) and got this error:

I apologize, I didn't verify my advice and I see it is crashing also on the server.

Ok, so I fixed it. This is what I had to do...

Wonderful Idea! Thank you for sharing it.

The size of the logs we store for jsreport studio startup is limited. This is hardcoded at this moment, unfortunately.
However, you should be able to get standard jsreport logs in the file system logs/reporter.log. Would this work for you?

jsreport 2.6.0 is now released with respective docker images. The newer chrome which is part of it should work better in azure web app.