Topics created by zewar96

i don't know what can be the problem, as mentioned, the full docker image work for us, we are using it with docker for windows/macos and also running it on linux directly, so it is working fine.

if this issue only happens when you are building your own image, then something must be wrong there, but we can not know without testing a complete docker image.

Thank you for the bug report. I can replicate it.
The v4 includes several studio optimizations for large workspaces which caused some regression bugs, we gonna hotfix it this week.

Maybe you can change the URL here to your private Office Online Server.
https://github.com/jsreport/jsreport/blob/master/packages/office/lib/response.js#L87

Please try it out, if it works we will happily make it configurable.,

I may not be describing things correctly, but i am trying to access variables from within helpers, not scripts. Does that matter?

I will work on getting you a playground entry to look at so you can see, but if the helpers can't run the beforeRender and don't have access to variables within the global, it won't really matter much

That's fantastic news. Thanks for digging in to this as i know it wasn't easy to find and fix. Hopefully the performance improvements will be a benefit to everyone. I know they will be huge for us and save us from having to rewrite a bunch of reports using a non-standard way.

I emailed you the whole folder compressed so you can see what's running. It came from my other email so i could share a large file with you, but i put this forum in the subject

Thank you

Does a backup from the studio work for your purposes or would you like me to pull the files from the docker image directly?

The studio export doesn't backup scheduled runtime tasks or stored reports so its better to use data copy.

@zewar96 jsreport does support node.js 18 (should work with any version that is >=16.11).

if we talk about node.js alone, then v18 works also with jsreport + docker, however, i think the issue is that changing the base image from node 16 to node 18 needs some changes to be done in the dockerfile (perhaps some linux packages need or updates or some extra linux packages need to be added), so this is more an issue that the dockerfile needs to be changed to work against a different base image.

we just provide one node.js version for the docker image, and that is what we test so far. we are aware that v16 goes EOL later this year, when it comes the time we are going to increase our minimal version and update the dockerfile, you can track this issue to receive notification when this happens.

perfect...thank you!

The jsreport 3.11.1 with fix is released.

The ne isn't supported. I will add it to the next release.
The fs provider doesn't fail but doesn't support ne and doesn't filter as well.

No authorization used. This is just a clean load using your windows instructions, running locally via powershell to load Node.js. The only thing i did was to add 1400+ templates to the system before exporting.

Thank you, I've filled it to our features backlog
https://github.com/jsreport/jsreport/issues/984

I have emailed you the files i was able to get. Hopefully it helps. In the meantime, I am going to try to write something in AWS Lambda that can do the backup to S3 for me daily so we don't run in to this again. Thanks for the info, it should be all we need to get this setup.

Is there a way i can recreate a folder that goes missing (with the same shortId)? Is this something that could get lost in S3 or is a folder metadata only?

Yes, just look on another folder and create it the same way. You will need to create s3 folder (folder name) and inside config.json with the following structure.

Or just create the folder with studio and then update the shortid inside config.json.

You will need to reboot jsreport afterward.

I don't know i did wrong the other day, but adding Encoding to it worked!

Thanks...we can now use JSReports for document conversion of Docx to PDF!!

Thank you, I've put it in the backlog and we will implement it.
https://github.com/jsreport/jsreport/issues/917

Do you have any other suggestions?

You solved my issue!!!

The reason I thought it was odd was because I actually had the wrong syntax

In my example i was doing {{#xlsxAdd "xl/drawings/drawing1.xml" "xdr:wsDr.twoCellAnchor"}}

In your example you did {{#xlsxAdd "xl/drawings/drawing1.xml" "xdr:wsDr.xdr:twoCellAnchor"}}

I completely missed the 2nd namespace which is what caused things to not work at all. This is why things looked odd to me but I couldn't figure out why.

As always...thanks for everything! It's a great product!

That is an interesting problem, thank you for sharing.

We need to make one change in jsreport to make this work. I've put it to the backlog, it should be ready in the jsreport 3.5.0, which should be released in a few weeks.
https://github.com/jsreport/jsreport/issues/908

https://github.com/jsreport/jsreport/search?q=dockerfile

this is how I got a lot of links too

This issue is resolved. AWS must have changed their rules on the XSS validation because their WAF was the cause of the problem. I added an exclusion for odata within our XSS rules and now it's working fine. Thanks for the info on the intervals changes. We will update that as well.