Running reports from a report

[nickakin]

Is there a way to create a report that is comprised of other reports?
I have two different srex files that I want to trigger from a single execution.

[ariacom]

you may create a simple report to show all:
import the models of the different reports into your new report (using Smart Copy if possible or XML copy...)
create a Tab Control View, then create a Tab Page View, then a Model view for each model.
You will have a single report..

Or you can create a report that have a task that execute reports:
check the samples:
01-Tasks\102-Task Generate several Report Results.srex
or
05-Scripts\504-Navigation - Execute reports from a report.srex

[nickakin]

Thank you for the ideas, the tab view or even using multiple containers in the view does work but run into issue with page numbering and page title. I did see 504 in the samples, perhaps using 102 to generate and then merging the results could work.

[nickakin]

Using report 102 to execute reports from a report worked great. However, to merge the results QuestPDF provides DocumentOperations API starting at 2024.12.0 (see: https://www.questpdf.com/concepts/document-operations.html).

Any objections to creating a pull request with the QuestPDF package updated? I can provide an example as a token of appreciation...

[ariacom]

Hi, no problem to update QuestPDF, however just make sure that the demo and the PDF renderer is still fine.

[nickakin]

Thank you, the library's reference to QuestPDF is conflicting when updating this one. I have put in a pull request there to update it to the latest so that both will be up to date.

[nickakin]

I cancelled the pulled request because QuestPDF.Barcodes has an "equal or greater than" on the QuestPDF dependency ([2024.3.6,]), so theoretically there shouldn't be an issue. I'm debugging into the RazorEngine.NetCore project and the Compile method is erroring out looking for a specific version of QuestPDF (2024.3.6) when invoking a method from the QuestPDF.Barcodes extension methods. I'm more confused that it worked using the version in Seal fine (2024.7.0) but began to error when I updated (2024.12.0 or greater).

I attempted to tinker with the LoadRazorAssemblies, but that's not the problem. It loads the new assembly fine, but the runtime fails to use the new assembly. Any ideas? Should I push the code for you to take a look at? Or should I be trying to get QuestPDF to incorporate QuestPDF.Barcodes changes?

[ariacom]

perhaps you have issues with the cache assemblies located in Repository\Assemblies\RazorCache -> cleanup this folder first.
you can also set 'Enable Razor Cache' to false in the Configuration of the Server Manager

[nickakin]

Thank you for pointing you the folder location, that did help with testing. However, it still fails to run the extension methods from QuestPDF.Barcodes. I pulled a fork from their repo and updated the reference, then packed the solution into a nupkg and loaded it from a local folder in my fork of the Seal repo and it works great. I dug a little deeper and found that the QuestPDF started signing their dll on version 2024.10.3.

I opened a new pull request in the QuestPDF.Barcodes repo to update the QuestPDF reference. If I don't get a response shortly, I can publish my fork publicly.

[nickakin]

The pull request was accepted today, and a new package was released

[nickakin]

I'm including an example report with my merge request. The solution combines steps from report 102 to generate a report from a report. The key parts to look for are:

• Create a Common model to collect any restrictions required to pass down to the child reports, if needed.
• Collect the generatedPdf path
• Using DocumentOperation to load, merge, and save

[nickakin]

#139