hi! is this a fresh installation? i mean, have you copied some configuration file from your previous project? this seems to be a problem of loading old configuration when jsreport v2 tries to start. is jsreport.config.json the name of your config file? can you show here the full logs that you get when starting jsreport (from the first line to the error you are seeing)?

I'm running jsreport on two different servers (one for development and one for production) so the shortid for my "print" folder will differ on each server. Is there a way to pass the folder name instead of the shortid in the URL?

i think there is no way at the moment. however you can get the shortid of folder by using another query by name. for example to search folder with name templates it will looks like this http://localhost:6200/odata/folders?$filter=name%20eq%20%27templates%27, however this query can give you multiple entities because there can be other folders (subfolders) named templates at different hierarchy levels. you can make the query more specific by specifying that you are searching folders at the root, it will look like this http://localhost:6200/odata/folders?$filter=name%20eq%20%27templates%27%20and%20folder%20eq%20null

i think i solved it, can you please update jsreport-pdf-utils to 1.3.1 and try again? i test it with your image and it works

thanks for the repository, i will check..

you just need to use call the data using the syntax of the template engine you are using (usually Handlebars), for example if the response contains some attribute named "foo" and you are exposing the response of http request as row, then you just need to put in your template {{row.foo}} if you want to print the content

you can change the query to be http://localhost:5488/odata/templates?$filter=folder/shortid%20eq%20%27<shortid of folder>%27 just replace the <shortid of folder> with the shortid of the folder, to see the shortid of a folder just do a right click and then "Edit", you will see in the url the shortid of the folder

ah sorry, i forgot to call done one more time in the script, here it is the script updated.

const https = require("https");

async function beforeRender(req, res, done) {
  var str = "";

  https
    .get(
      "https://app.sm4rt.com.br/feed/timevalue.json?id=40&apikey=f9cae76090f9f4ba97d5920fd003d3d4",
      res => {
        // A chunk of data has been recieved.
        resp.on("data", chunk => {
          str += chunk;
        });

        // The whole response has been received. Print out the result.
        resp.on("end", () => {
          try {
            req.data.row = JSON.parse(str)
            done()
          } catch (e) {
            done(e)
          }
        });
      }
    )
    .on("error", err => {
      done(err);
    });
}

yes, support for entity paths has been added in 2.3.0 along with folder entities support. note that entity path means just the hierarchy formed by folder + rest of entities.. for example if you create a folder, then inside the folder put an asset there, you can reference that asset with its entity path, which will be /[folder name]/[asset name].

if you just want to reference a file from your filesystem then you should be able to follow these instructions and pass a path to your filesystem to the asset call, it should work too

i think you just need

const https = require("https");

async function beforeRender(req, res, done) {
  var str = "";

  https
    .get(
      "https://app.sm4rt.com.br/feed/timevalue.json?id=40&apikey=f9cae76090f9f4ba97d5920fd003d3d4",
      res => {
        // A chunk of data has been recieved.
        resp.on("data", chunk => {
          str += chunk;
        });

        // The whole response has been received. Print out the result.
        resp.on("end", () => {
          try {
            req.data.row = JSON.parse(str)
          } catch (e) {
            done(e)
          }
        });
      }
    )
    .on("error", err => {
      done(err);
    });
}

then you can row in your template, in your previous examples you are not setting the data that you get from api into req.data, that is fundamental thing to do when you want to pass data from script to template

let's continue the conversation on this github issue, we will post the resolution here once it is clarified what is happening