asked on March 23

I've seen lots of posts about rows being cut off on the save to repository tasks but not about columns so I'm hoping someone has some insight on this.

The use case is that I'm sending a dynamic HTML table from Workflow to a business process to save as a TIFF to the repository in order to move the pages into a summary report of multiple reports. This HTML table has a variable number of columns depending on how many years of data are being sent. However, I've noticed that if there are many years (and therefore many columns) the table doesn't fit the width of one page, which is fine, but then they don't get saved anywhere to the repository at all. Is there a way to have the columns render on the "next" page as just those columns (and then continue on the following page for the rows that also exceeded the page limit, which does currently work)? I attempted to make the width of the form the max value but that did not affect the ability to save all the data to the repository.

This also occurs if I select to save as PDF, so no difference there. This is in Cloud.

Thanks!

0 0