Posts made by bjrmatos

@a-pulvirenti_TSGC24 FYI, this problem is fixed, it will be part of next jsreport release

@a-pulvirenti_TSGC24 it took me longer (i was on vacation), but i am now checking this bug.

it seems your export does not contain some helpers you use, when i try to run the template i get the error that some assets are missing.

can you share en export with those files included? likely you need to include also the /TS320/IT/common folder, and the statistiche.js referenced in the helpers.

thanks.

@a-pulvirenti_TSGC24 thanks, i have received the email with the zip, i am going to review this soon

@a-pulvirenti_TSGC24 it seems the zip was not uploaded correctly. can you try again?

you can also email me the zip at bjrmatos@gmail.com in case the upload does not work again.

hi @a-pulvirenti_TSGC24

I have an Excel report where I use a data table and in the header I put a placeholder which contains the call to a function which is defined in the helper of the report itself.
Up to version 4.10, that worked perfectly, sinche the function call returned a string, and that string appeared in the table header as expected.
Now I am using versione 4.13 and whenever I try to launch this report, it produces a corrupted file, which Excel has to repair before opening it, while if I try to run the report from the jsReport studio, it does not manage to produce a valid Excel file.

if you have a template that worked fine in 4.10 but broke in 4.13 please share the full template so we can fix it.

I have tried to act in the template by using xlsxReplace to replace the value on the fly before rendering, but this does not work. It does not work either if I try to put the value in the shared strings replacing the fixed string value I put in the Excel template.

was this part of the original template in 4.10? or is it a workaround for your template in 4.13?

if this is just a workaround for 4.13, lets focus on fixing the original template so you dont need this.

hi @andribo

sorry for not adding a reply, yes i am currently working on fixing this.

hi @andribo the changes are these, if you have a case where a previous template was working, please share all the details so we can fix the implementation or investigate the reason for the result.

@Genhan @fmmich

hmm we only call promisify on script functions with 3 parameters, does your beforeRender or afterRender functions in the script are defined with 3 parameters?

it seems you have async functions but for some reason the definition of them have 3 parameters, which is incorrect for modern jsreport scripts. you are hitting a legacy part of code that we maintain to support older version in which the beforeRender, afterRender functions were callback based.

the solution is to check the beforeRender, afterRender functions in your scripts and if you are using async function just make sure the function does not receive 3 parameters.

@Ish-Modi the usage is exactly as the code snippet in this thread.

<table>
<tr>
      <td>
        <img src="{{base64imageDataUri}}" />
      </td>
    </tr>
</table>

to generate the base64 data uri you can use assets

hi @sallystalone we are currently taking a look into xlsx related tasks, when it comes the time to review this case i will reply.

got it, FYI this is now fixed on master branch, it will be part of next release

I've even tested putting the formula =B2 in the cell A3 and that causes this issue, so perhaps that's the simplest form

do you mean this? for me, it works

thank you for the replication, i am going to take a look at the problem.

@proxisua yes, it is not described in documentation. i have added a small description of this in the authentication docs.

thanks

hi!!

verything is working fine (creating and aasignment readAll/editAll permissisons) but assignments of IsAdmin alwais returned 401 Error (Unauthorized Access)

yes, this is expected, only the superadmin (the admin configured through extensions.authentication.admin) is allowed to modify the isAdmin flag of other users.

Also in JSReport Studio regular SSO user can't find Admin check box in groups properties.

this is expected too, as the explanation from above.

Is still this approach true?

no, since we added the support of having other admin users in https://github.com/jsreport/jsreport/issues/860 user management right now can be handled with these admin users. the only thing that is not possible to tweak from these users is adding or removing the status of admin users, this action is only allowed right now for the superadmin.

We would like to allow administrators of our system also manage the user access to JS report servers used to generate documents.

this makes sense, and it is possible right now either with user groups, or using admin users, however, why you need to be able to change isAdmin too? if you just want to control the access to jsreport server, all of that can be done right now. but i dont understand why you need to also have the chance to add or remove admin users in this workflow.

hi! i dont know what could be causing this without knowing what your template looks like. try to share a sample where the issue is fully reproducible

FYI, this is fixed now on master, it will be part of next release

hi @enoranowak-beep

can you try to upload the xlsx files again? it would be great if you add the data you use too.

if you like you can also send me those files at bjrmatos@gmail.com

hi @lennykey

Before this was working before jsReport 4.0.6

do you mean before 4.6.0? right?

{{lookup localize "months" (localizationFolder) settlementMonth}}

hmm i am not even sure why using the lookup worked previously here, that way you use the lookup makes use of 4 parameters, even though i think lookup only works with 2 (according to handlebars docs).

{{localize (concat "months." settlementMonth) (localizationFolder)}}

This looks good, and it is the correct way to use the localize helper, though i am not sure why you need to wrap the localizationFolder in parentheses (localizationFolder), if it is just a data variable you should not need to use handlebars sub-expressions here.

hi! yes, it is not possible to use ESM inside the sandbox, it is mainly because of some limitations in the implementation of sandbox (vm module and vm scripts).

we are tracking the progress of it in this issue, there were some changes in node that will likely help with making ESM modules to work in sandbox, however we have not yet evaluated the full history.

this change will likely require a major version bump in jsreport so we are still in the process of planning the next major release, and when we are on that we will fully check if ESM is possible right now or not yet given the current nodejs features.