Skip to main content
Question

Is there a way to restrict table height on a check regardless of how many lines of data there are?

  • May 19, 2026
  • 2 replies
  • 27 views

Forum|alt.badge.img

I am using IFS Report Designer version 200.3.0004. I cannot put a block container in the flow section to restrict height, and I cannot put the table in the header or footer sections as the check itself needs to go below the flow section. I need the table to be the exact same height for every check in order to align properly when printing, and tables with multiple invoice lines end up having more space than the checks with only 1 line. 

 

2 replies

ashen_malaka_ranasinghe
Hero (Employee)
Forum|alt.badge.img+14

Hi ​@AlexValenzuela,

In IFS Report Designer (especially in the older 200.3 version you are using), the behavior you are seeing is expected due to how the layout engine works. The Flow section is inherently dynamic and is designed to repeat for each occurrence of data, meaning that tables placed in the Flow will automatically expand based on the number of rows returned. Because of this, there is no native way to enforce a fixed height on a table or container within the Flow section and attempts such as using block containers will not give the desired result since blocks are primarily meant for grouping static content in header or footer areas rather than controlling layout dimensions in the Flow.

Since the table height changes based on the number of invoice lines, this causes inconsistent spacing between checks, which leads to alignment issues during printing. Unfortunately, this is a limitation of the underlying XSL‑FO rendering engine used by Report Designer, where layout elements expand naturally to fit their content. It does not support strict height constraints or overflow behavior in the same way modern layout tools do, especially within repeating sections.

To achieve consistent height across all checks, the commonly accepted workaround is to ensure that the table always renders with a fixed number of rows. This is typically done by padding the dataset so that even when there are fewer invoice lines, additional empty rows are added to reach a predefined maximum. By doing this, the table will always occupy the same vertical space, regardless of whether there is one line or multiple lines. This approach directly addresses the root cause of the misalignment variable row count by making the output structurally consistent.

If modifying the underlying data is not feasible, a similar effect can be achieved within the layout itself by conditionally rendering empty rows. For example, you can define a fixed number of rows and display actual data where available, while leaving the remaining rows blank. Although slightly more complex to maintain, this method still ensures that the visual height of the table remains constant across all checks.

In summary, what you are trying to achieve restricting a table to a fixed height within the Flow section is not supported directly in IFS Report Designer. The only reliable way to maintain consistent check alignment is to control the number of rows rendered, either through data-level padding or layout-level conditional rows, so that every check produces a table of identical height when printed.


Forum|alt.badge.img
  • Author
  • Do Gooder (Customer)
  • May 22, 2026

Do you know what condition can be used to hide a row if the line count of a field is greater than one?