Topics created by Vishnu Menon

How do you prepare the image? What's in your dockerfile?
It's typically better to use our docker image as a base.
https://jsreport.net/learn/docker

That is a big jump from 1 to the latest. You will need to migrate first to v2 and then to v3.

Here are the migration notes for v2
https://jsreport.net/blog/jsreport-v2-released
https://jsreport.net/learn/v2-breaking-changes
Note to install v2, just update your package.json and set a v2 version and run npm i

Here are the migration notes for v3
https://jsreport.net/blog/jsreport-300-released
https://jsreport.net/learn/v3-migration-guide

You may have it easier if you, while still in v1, export from s3 to the local fs store and perform the update with fs.

And if you don't have hundreds of entities, you may have it easier to start with v3 from scratch and just copy-paste the entities' contents.

If you want to use s3 as the template store, here is the latest doc
https://jsreport.net/learn/fs-store#aws-s3

Good luck!

hi! we don't have control over the default styles that a recipe engine (chrome, phantom, etc) uses when it encounters a broken image, if the behavior is different between versions 1 and 3 is probably because they both use different versions of the chrome/phantom.

perhaps you just need to apply some css styles to the images so they contain restrictions about not growing more than some specific width/height

jsreporonline tiers FREE - BRONZE - SILVER - GOLD each has some credits monthly limit.
Every credit is 1s jsreportonline used to render it.
You can see how much credit is spent for a particular template if you run it in debug and observe the output.
jsreportonline doesn't store outputs or input data. Only if you explicitly ask to through the reports extension
https://jsreport.net/learn/reports

Every few months we release a new version of jsreport which includes bug fixes as well as new features. The one time perpetual license allows you to update to the jsreport versions released during the 6 months after the purchase.
https://github.com/jsreport/jsreport/releases

Example:
You purchase today a perpetual (one-time payment) license, which will work with the latest 3.4.1 jsreport version.
The next month we release 3.5.0 and your license will still work with it.
However, in December we release jsreport 3.7.0, and because this will be 8 months after your original purchase, your license key won't work with it.

hi @Vishnu-Menon can you please put your demo here on the playground? doing that will allow us to check what you are trying to do and help.

My issue seems very similar to
https://forum.jsreport.net/topic/311/timeout-error-or-return-blank-sub-reports/10.
Here you have mentioned to increase the phantom js timeout.Where exactly you referred to increase it.Is it possible i can pass these configurations as part of payload of the post call in jsreports like
"data": {
"template": {
"shortid": TemplateId,
"phantom": {
"resourceTimeout":90000000,
}
},
"data": reportData,
"options": {
"language": locale,
"timeout": 90000000
}
},
"headers": {
"Content-Type": "application/json"
}
};