Posts made by jensweigele

Hi Jan,

thanks - didn't thought about that possibility!

Regards
Jens

Hi,

is there a possibility to ignore a missing asset?
I would like to load the asset "/logo.png" but if it doesn't exist, I want to take another logo.
I was trying to do this in JavaScript (check if the result of {#asset... is not empty etc.) but get an error that the asset "/logo.png" was not found.

Regards
Jens

Hi,

thanks - I created a global script to fix the issue and will update once a new NPM package is available.

Best Regards
Jens

Hi,

we are seeing a problem when using multiple language resources and the Studio Preview feature.
See this example: https://playground.jsreport.net/w/anon/8rg1MYrR

Look at the content of "@root.$localizedResource" and the name of the resources used - they do not match the names of the data elements.
When looking at the sourcecode (https://github.com/jsreport/jsreport-resources/blob/master/lib/resources.js#L60-L75), I guess it's because the "options.language" field is not set in the preview.

Do you agree or do I miss something?

Best Regards
Jens

Hi,

I'm using JSReport with the jsreport-mssql-storage Plugin.
With a custom plugin I'm trying to add another data-field to the "Reports" entity, like so:

    reporter.documentStore.model.entityTypes['ReportType'].myTest3 = {
        type: 'Edm.String'
    };

When starting the render process, I'm doing something like this:

jsReport.render({
    template: { _id: invocation.parameters.template.id },
    data: invocation.parameters.data,
    options: {
        reports: {
            save: true,
            async: false,
            mergeProperties: {
                myTest3: 'a'
            }
        }
    }
});

This works if I start JSReport with a "clean" database. The "jsreport_ReportType" Table gets created along with the "myTest3" column (in the database).

But doing this with an "existing" database (where my custom data was not specified in the beginning), gives an error, that the Column "myTest3" was not found.

For me it looks like, that there is no migration strategy for the documentStore.
Am I right with this assumption?
If so, what is the desired way to add properties to entityType?

Best Regards
Jens