@Aylarann ok, i have created a request to support this, you can subscribe here to get updates when there is progress about it.

Unfortunately, the browsers have still very poor support for CSS-paged media.
So we typically solve such problems as you describe with pdf utils or with javascript.

Here is an example of how you can make the footer on the last page different.
https://playground.jsreport.net/w/anon/h3amrdZK

The first-page header content could be just moved to the main content to avoid problems with different header sizes.

Hopefully this helps.

Thanks! I got that kinda settled out and now its telling me that my css file isn't there, although I can see it so now I'm trying to get that sorted out.

Legend!

This is kind of a frustrating error, I also suffered this error on my chrome. I fixed this issue by follow some steps from here https://droidtheory.com/pdf-not-opening-in-chrome-fixed/ You can also try them, they worked for me

I think I just answered my own question. You can 'nest' helper calls like lookup, so I am now doing this:

{{#each foo}} <h2>Location: {{lookup (lookup ../mappings id) 'name' }}</h2> {{/each}}

Seems to work. Hope this helps someone else!

As a note, I also had to stop and start the npm server that was running before it picked it up.

yes, that is expected, if you make some change in the config you should stop and start the server in order to recognize the changes.

Thanks solution, works for me