<![CDATA[Report template metadata]]>Hi!
I need to store some additional info (Map<String, String> or dictionary) with each template and be able to query this info with along with the list of templates. Is it possible?

]]>https://forum.jsreport.net/topic/780/report-template-metadataRSS for NodeWed, 09 Sep 2026 07:17:42 GMTMon, 15 Oct 2018 16:40:08 GMT60<![CDATA[Reply to Report template metadata on Invalid Date]]>Hi!
I need to store some additional info (Map<String, String> or dictionary) with each template and be able to query this info with along with the list of templates. Is it possible?

]]>https://forum.jsreport.net/post/3817https://forum.jsreport.net/post/3817Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>Hi,

you can extend template type with custom string property inside a custom extension.
Here are the docs for writing custom extension
https://jsreport.net/learn/custom-extension

or simply add just this to your server.js.

const jsreport = require('jsreport')
jsreport.use((reporter) => {
  reporter.documentStore.model.entityTypes['TemplateType'].foo = { type: 'Edm.String' }
})
jsreport.init()...
]]>https://forum.jsreport.net/post/3838https://forum.jsreport.net/post/3838Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>I want actually to have something like template.metadata = {
customerId: "",
label: ""
};
I need this to solve following usecase - We have set of default reports and many customers, some of them want reports to look differently. Having metadata, I will be able to store for example customerId, base report type it corresponds to, etc...

]]>https://forum.jsreport.net/post/3846https://forum.jsreport.net/post/3846Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>Yes, so why don't you add two, three... new props to the template?

Or you can have one extra prop that serializes what ever you want. Like a map.

]]>https://forum.jsreport.net/post/3847https://forum.jsreport.net/post/3847Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>Sure, I can... I just thought that it can be a good base functionality :)

]]>https://forum.jsreport.net/post/3850https://forum.jsreport.net/post/3850Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>Yes perhaps. Thanks. Lets see if it gets requested more often.

]]>https://forum.jsreport.net/post/3853https://forum.jsreport.net/post/3853Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>I can relate to this, seems to be the exact same thing i need to do as well. I have to deploy the enterprise edition at each of my plethora of customers and this as base functionality would be greatly beneficial. Also I created an issue on Github before finding this post.
https://github.com/jsreport/jsreport/issues/620

]]>https://forum.jsreport.net/post/5742https://forum.jsreport.net/post/5742Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>Can this actually just be done via the API and resources now?

]]>https://forum.jsreport.net/post/5743https://forum.jsreport.net/post/5743Invalid Date<![CDATA[Reply to Report template metadata on Invalid Date]]>@Css-IanM thanks for creating an issue for this, let's move the conversation to the github issue, we will reply to the issue when we have analyzed the use case a bit more with the team

]]>https://forum.jsreport.net/post/5747https://forum.jsreport.net/post/5747Invalid Date