Whenever a form is submitted, Team Forms automatically generates a PDF copy of that submission and archives it in your Teams SharePoint document library. Team Forms strives to ensure that the generated PDF closely mirrors the digital form, serving as a paper equivalent. However, due to the intricacies of translating a digital form into the PDF format, there are instances where the mapping isn’t perfect. In this article, we outline some known limitations of the PDF generation and offer user-driven workarounds wherever possible.
Data Grid rows larger than a single page
If a single row in a data-grid is long enough to span more than a single page, the contents of that row will be truncated in the PDF. This is demonstrated in the example shown below.
To resolve this issue please consider implementing the following:
Instead of having questions stacked vertically in each data-grid row, arrange some horizontally using columns. This approach reduces the height of each row and allows for a more compact display.
If possible, decrease the number of questions within each row of the data grid. By doing so, you’ll further minimize the row height and create a more concise layout.
Column Component positioned between a page break
If your form contains columns with multiple stacked fields that happen to land at boundary of a page break within the generated pdf, then you will find that the position of the components in the PDF may not accurately reflect the rendered form. This is illustrated in the screen shot below:
You can manually resolve this issue when building your form using one of the following strategies:
Place a PDF page break component before the column component. This will start the column component on a new page to avoid the scenario where a column lands on top of a page break.
Instead of stacking multiple fields vertically within a single column component you can stack multiple column component onto of one another. In this configuration each set of question that should appear side by side would be housed inside their own column component. This component structure is shown below
