Pdf Function cannot create multipage pdfs

[Uv_]

The PDF() function is locking me to a single page pdf and cutting off rows from a gallery.

I have expanded containers set to true, I have the following typed in:

Set(PdfQuo,PDF(('Print Out'),{Orientation:PaperOrientation.Portrait,Size:PaperSize.A4,ExpandContainers:true}))

where 'Print Out' is a container in which a gallery sits which I want to create a pdf file off.

I have this PdfQuo blob placed in a pdf viewer in the app. From what I can see, for some reason, its not expanding the container vertically and cuts off the information after filling 1 page.

I know this wasn't previously an issue, because I have used this before and I remember being able to generate pdf files with more than 1 page, this did work before.

Unless I made some silly mistake, I can assume its a bug, and since this is an experimental function

Does anyone have a clue if these are generally fixed fast or should I start investigating an alternate method for creating pdfs for now?

[kevinlowe]

Same issue for us.  It IS expanding the container, but it is only producing a single page of pdf content. I really hope this one is fixed soon, with this bug this amazing feature is useless, and we lose a lot of value in using the platform.

[Uv_]

Just a quick update. This bug is still there and giving the same issue.

I have however stumbled across a temporary workaround for the time being, posting in case it might help someone.

The container in question that I am trying to expand, but cuts off after 1 page, on that I changed the height of the container. 

Previously was 'set by container', changed that to 'custom' and put a really big number there.

Result is now it will always generate more than 1 page pdf, though in cases you will get blank pages towards the end depending on the size of your content and how big you've set the height. I am gonna play around a little more to get a cleaner result but right now this could work for me instead of having to change the whole app I made to this point.

Downside though is that while the pdf itself and the pdfviewer, I have it in scrollable view. However the container itself is cutoff on the display screen and only partially visible (not scrollable), but that is a compromise I am happy to live with for now, at least until this hopefully gets fixed.

[Uv_]

Since it seems that more than 1 page can be produced by altering the height of the container, I am once again thinking the issue might be linked to the container expansion ability of the Pdf() function. But I could still be wrong 🤔 

[kevinlowe]

Interesting! We did a test by shrinking the container to be very small and expand containers still gave us a whole page. I'll try the container height today. 

[kevinlowe]

Update: Some change was made overnight. Same application that was refusing to print two pages now does (but fires an error when viewing the document) Today, I tried increasing the height of the container dramatically and it worked with no error in the document. My setup was a main container that has two child containers - one with a document html, one with a panel of instructions for taking action on that document. I also tried taking the document container out of the main container, set it to auto-height, it did produce multiple pages for me without an error in the document (all the same HTML, of course).

[Spiedini91]

Had many issues with PDF function only printing the first page, even though ExpandContainers is set to true, the solution we found is explained here: Re: PDF Function weird issue - Power Platform Community (microsoft.com) hopefully it may help someone else too.

[TPPFC]

Similar issue.  I've experienced the edit mode issue (which is handled with containers). I am also having an issue where when the PDF is created, I can view the PDF (often slow load time, so I power automate a conversion, which gets faster load times), however every page after the 1st page results in an error. I can see the pages in previews at least, but when you try to edit they error and not much can be done other then converting to .doc (losing formatting) and converting back.

It's pretty frustrating. The first page is great, and I can see the next pages however can't click on anything in Adobe. Just error.