hi!

which doesn't seem to work. I have along table that spans across multiple pages and following pages does not have any margin at all

there are two types of options, extensions options and template request options, the extension options are the ones you can pass during core initialization, the template options are the options you can pass in .render().

the marginTop, marginLeft options of chrome are part of template options, so in order for them to work you need to pass it like this:

.render({
  template: {
    // ... other options here...
    chrome: {
      marginTop: '30px',
      marginLeft: '10px'
    }
    // ... other options here...
  }
})

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

hmm, i have no clue, with the error message we just know that the tedious rejected the connection because probably bad credentials for the ELSReadOnly user, are you sure that you are using the right credentials? this is probably just a mistake in the code that does the connection to your database, I recommend you to try the connection first in a normal node.js file (outside of jsreport script) and verify that it works, that should be easy because you just need to commend some parts of the scripts that are jsreport specific, then copy the code in a file and try it with normal node.js execution

hi @djbrody

this is invalid javascript

Object.assign(req.data, {dbo_Account.recordset})

you can change it to be

Object.assign(req.data, { dbo_Account: { recordset } })

or

req.data.dbo_Account = { recordset }

hi @Rommel-Manalo, as you know the Apple M1 is brand new, so it is expected that software will take some time to support it without problems.

is this just a problem with docker? i mean, are you able to run jsreport as normal node.js application (no-docker)? the problem here is more about the ability for docker/chrome to be able to run normally on M1, we haven't tried yet an execution on a M1 machine, we probably can not do anything about the docker/chrome M1 support, but we will keep an eye on the issues of those repositories.

Are the docker versions > 2.8.0.0 using node > 14.14 by any chance?

no, we still use node 12 even on the latest version (2.11), we plan to upgrade the node.js version there in the next major version

i see, using toLocaleString relies on the icu information of the node.js version, in normal case using nodejs 14.15.0 is enough because it comes with the full icu information so all locales should work ok here. i did a simple test and this works ok with 14.15.0

*I'm running jsreport in Docker

this is probably the problem for your case, you have nodejs 14.15 installed however if you use the docker container then you end up using the nodejs version which is specified in the Docker build, which in the case of the jsreport 2.8.0 is nodejs 12, which does not come with the full icu needed to support all locales.

what you can try is make a custom docker image taking out image as the base, then you just need to change the nodejs version to node >=14.14 in that image

@rdkleine hi! which version of node.js are you using?

hi @seerat89 can you please share an example? i would like to see in which case the header/footer stops to work. i tried a simple example and i see it working, you can check it here

but of course, this does not mean anything, because if it is not working for you there can be other things involved in your template that are making it to not work, and it will better to check it in your real template

@seerat89 hi! the assets extension is only useful for static things, files that you have available during the template creation and basically don't change during the template execution, it can be fonts, some images, etc.

for dynamic images, the assets are not the right approach. you need to pass the images in the data that you send, there are basically two approaches you can take, it depends mostly if you host your files in some server or not.

• if you have the dynamic images hosted on some server (this means you upload the images you are going to use sometime before the creation of the report) and that server is able to serve them, then you can just pass urls to your data, and in the template just iterate your data and render a normal img element <img src={{imageURL}}} />
• if you don't have the dynamic images hosted, then you can just pass the images as data uri, which is basically the image in base64 encoding as string, and in the template yo do the same and just use an img element <img src={{imageDataURI}}} />