nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I filter at render time from rptdocument

grather · 2015-02-05T13:52:26+00:00

I have a report that outputs to PDF. My requirements have changed since I started. What is working right now using the RunAndRender I do the query returns (For Example) 6 records. The report then outputs one page per record. So I end up with 6 pages…

grather

I have a report that outputs to PDF.
 
My requirements have changed since I started.
 
What is working right now using the RunAndRender
I do the query returns (For Example) 6 records.
 
The report then outputs one page per record.
 
So I end up with 6 pages in PDF.

My New requirements is to return 6 different PDF's
 
I was thinking to take advantage of Run Then Render (Two different steps)
 
So I broke this up and it works
 
I Run and end up with rptdocument with six records.
 
Then I send the renderTask.render and I end up with the original PDF with 6 pages.
 
So I feel I am still doing good.

How do I render just one page. The loop through rendering each page separately.
 
I know what I want just not quite sure how to do it.
 
Gary

Find more posts tagged with

Comments

mwilliams

One possibility could be to create your report with a optional parameter for the record number or whatever unique value you have for the 6 records also a boolean parameter called "firstRun". On first run from your application, you'd pass true through first run and no value through the other parameter. This would return all 6 records or whatever. From there, you could write code in the onCreate of your table row to run the report again with firstRun set to false and the current row's value through the other parameter.
 
You'd just need to check the firstRun parameter to keep from running the onCreate script the second time the report is run. You could also handle this by creating a master and detail report to run the master which would automatically run the detail report for all records. Let me know if you have questions or would like a sample. There may already be something like this in the devshare or in the blog. If I find a post, I'll link it in here.

grather

I actually go this to work.
My requirements were to create individual pdf files saved to file system (One per record to the file system)
And to also return the full collection of Records in one PDF.
 
So What I did was run then render the report.
 
I output to a rpt document and created a bookmark for each record I wanted.
 
I then created a render task for each wanted file. But instead of passing the response output stream
I passed a file output stream.
I then opened the rptdocument and retrieved the list of book marks.
 
I then set the pageRange from the info in the rptdocument in the renderTask.
 
I then rendered each individual pdf into its file.
then after the loop where each individual file was created
 
I did one more but this time passing in the response output stream and did not use pageRange.
I then have individual files saved on the file system
And returned to the user a full PDF.
 
Works great.
And the only change was learning about bookmarks and pageRange in the render task.
 
Gary

mwilliams

Great to hear! Thanks for the update!