@rsemler6789 the v3 parses the helpers differently, it parses the code in helpers and looks for top-level functions, and treat them as helpers. so it works differently

it is not documented but if you want to do the same helpers registration (like v2) you can do something like this:

__topLevelFunctions.testing = function () {
    return 'Hola'
}

https://playground.jsreport.net/w/anon/QFCBJjJH

for your code i think you can change this last part to:

// OLD: })(this)
})(__topLevelFunctions) // NEW

the recommended approach is still to do it with assets but if you don't want to do big changes to your app then use what i described above

@Ish-Modi it all depends on the pdf viewer you use, in the studio we use the standard pdf viewer which has the limitation I described.

in your app, you don't need to use the same pdf viewer, although it is handy to let the browser handle the preview, it will have the same limitation. instead, you can check other pdf viewers which allow this customization. I think pdf.js is one of those that don't have this problem and will let you have a download button with a custom name. another solution is to add to your app a custom download button that triggers download from jsreport-client.

hi @Ish-Modi

this is the dialog you get when clicking the Download from the pdf preview, right? there is no way to change it, unfortunately, the pdf preview used in the browser has this limitation, it is a standard feature of the browser that does not offer a way to customize the name (the only way to have a different name depends on how you host the pdf file and the exact url you use to serve it, in any case, there is no way to have it work dynamic name values).

however, this only affects that button (on the browser preview), if you want to download the file you can use this button, which follows the options to customize filename

if you want to preview a pdf file from your app, i recommend to use pdfj.js which has a preview that supports customizing the download filename from the viewer

hi @Happy-Patel

it looks your code is the right way, there are multiple ways you can simplify it, one way is that instead of adding pdf page item per property value, you just use a single call with all the properties. then in the header you are sure your data is in the 0 index, and can create just a single function for all your properties access.

if you need to conditionally render something based on the avatar you can still do it in the header, from the main you can just propagate the avatar value (without the if) no matter if it is undefined or not

here is a demo
https://playground.jsreport.net/w/anon/EoeNYCW3

@Oleksii-Baula about the column width not being expected, I don't have a good explanation or solution, we use the chrome table layout algorithm so in this case we get the width values from chrome itself.

for the case in which overflow does not work (meaning that it does not make the cell to text wrap) i recommend that you just don't trust what the office preview shows you, i mean that you should download the output and check how it looks when you open the file.

I did a test and when the data in cell has spaces fiveThree fiveThree five... (like it is expected for the text wrap to work) I've observed that it looks different when opening the file locally.

however for the case in which the text does not have spaces fiveThreefiveThreefive... the wrap works but it hides part of the text (which is the result you don't want), basically right now in a case in which the text is long and it does not have spaces it won't work as you lile.

hi @Oleksii-Baula

my recommendation will be that just add a table width, and then set into the cols a value that distributes the available width, the exact distribution will depend on your needs, however i have prepared example using values that i think you were trying to replicate.

nested tr for get this construction, where i have each cycle inside another each cycle. If there another way to get construction like that, i will glad to see it.

in the example i have prepated you can see a different way without nesting, also another recommendation will be that you don't set overflow: scroll for all the cells, and instead only do it for cells that its content is expected to be large, so don't do it for the header cells.

https://playground.jsreport.net/w/anon/BG1GgqNg

@sahil12197 creating an executable with pkg and jsreport source is not an easy task. there are details to take care and explaining all of them will take a lot of time, however, it is possible.

the best i can do for you is to link to the source code we have for preparing the exe file we provide on each release.

the source code is available here, you will need to analyze it and discover how it works, we can not offer some guidance there because explaining will take lot of time for us

hi @Harishkanagvel

it is likely some of your xlsx transformations is causing this. you can try to comment some parts and try again until you get a not corrupted xlsx, you will be able to identify which xlsx helper call is causing that problem and probably be able to adapt it and fix it.

qq: is this how I need to do it moving forward? Or is there a patch/fix/alternative way I should look to do this going forward?

well, it depends, I am just showing how to pass the data to the subreport the easy way, based on your data entities, however, this does not mean that it is the approach you should take in production. after all the data entities are used more for testing, because on production you will feed the report with your own data (which is likely to be dynamic and not static like the data entity).

the main question here will be how you will get the data for the subreport, in the example i shared i get it from your data entity, but that is just for testing, in real world you can do either of the following:

• fetch the data for the subreport before you call the render of the subreport, this way you do http request (from the browser) and communicate with your server to get the needed data

or

• when calling the render of the subreport pass an id, your subreport should have a script attached that takes such id from data and uses it to execute an http request to your server (at the beforeRender step), then in the script you use the results to populate the report data req.data = <http request results here>

what you choose depends on what looks easier for you, and also if the communication with your server is already secure from the browser, if not then the solution with the script looks better because you can hide the http credentials that your server probably needs to authenticate and return correct response.

I should be seeing the entire report being generated, right?

yes, if you apply the changes I made in the example, you should see the sub report rendering as you would expect

testing subreport.mp4