hi! the code looks good, i don't know what can be the problem so the best will be that you create a small repository with your code so i can check it more deeply, then i can tell you why it was not working

since that you were using jsreport v1 and you upgraded to v2 but you forgot to update the format of your configuration options.

please check this page https://jsreport.net/blog/jsreport-v2-released to know what you need to change.

hint: you will need something like this in the end

exports.jsreport = jsreportcore({
  templatingEngines: { strategy: 'in-process' },
  appPath: "/report",
  phantom: {
    allowLocalFilesAccess: false
  },
  extensions: {
    express: { app: app, server: server },
    assets: {
      allowedFiles: "**",
      publicAccessEnabled: true,
      searchOnDiskIfNotFoundInStore: true,
    },
    scripts: {
      allowedModules: "*"
    }
  }
});

you can also use

FROM jsreport/jsreport:2.5.0

if you want to extend the most lightweight image

hi! you can extend the jsreport docker image and install custom extensions there.

i believe you need something like these

FROM jsreport/jsreport:2.5.0-full
RUN npm install jsreport-docxtemplater

you can build your own jsreport image with the above, which will have the docxtemplater enabled

we released a new version of chrome-pdf extension that can generate PDF from an URL.

to use it use an script that does the following:

function beforeRender(req, res) {
  req.template =  req.template || {} 
  req.template.chrome =  req.template.chrome || {} 
  req.template.chrome.url = 'http://your-page-here.com'
}

i don't think the speed issues is caused by the logging but you can try without the logs if you have some concerns about it.

here are some details about how to configure the logs https://jsreport.net/learn/configuration#logging-configuration

if you don't want debug logs then you can put something like this in your config:

{
    "logger": {
        "debug": {
            "transport": "debug",
            "level": "debug"
        },
        "console": {
            "transport": "console",
            "level": "info"
        },
        "file": {
            "transport": "file",
            "level": "info"
        },
        "error": {
            "transport": "file",
            "level": "error"
        }
    }
}

I'm using the web client's renderAsync call to run my report. Works great. I'm putting the result into an iframe and it displays just fine. But when I go to download it, the file is named 'download.pdf'. Where can I set the name to something better - like the report name plus parameters?

how are you downloading the pdf? are you doing it using the res.download method? or are you using the PDF viewer download button? the res.download should work and give you custom report name. however the other one using the PDF viewer download button is a bit random because we don't control that, it depends on how the pdf was loaded on the iframe, what we recommend is that you always put a custom "download" button that just call res.download for your users.

When I run a PDF report, I'd like to store the result on the server in addition to sending it to the client. How can I do that? Relatedly, where would it be stored so that I can get a listing of stored reports?

well, you can send the pdf that you generate to some custom route in your server and save it in any place you want, if you do that you are in control about how to get a listing of the stored reports. the other option is that you use the reports extension, which can store the reports on file system, s3, azure, etc it depends on how you configure the blob storage

hi! i'm afraid the server does not return or have an event which provides that information. the best here is to switch the loading indicator to a spinner

here in the docs https://jsreport.net/learn/browser-client#large-report-file there is the explanation why it does not work for big files, and also how to make it work by using res.toObjectURL()

oh so you are using jsreportonline, right? well since that is a service there is no way to change the configuration.

i guess your only options are

1. you can define the functions in a .js file then you can read that file as string and pass that to the helpers option

and

2. you can use some ES6 to avoid having too complicated syntax, in the end you can have something like:

i like the first