Expected results:
The PrintOnPage event is triggered multiple times for a single report control, if this control is repeated multiple times in the report. Moreover, each report control occurrence that is split between pages will trigger the PrintOnPage event for each page where the control is printed.
But, if the report control's occurrence is printed on a single page, the PrintOnPage event should be triggered only once.
Current results:
We found that in some configurations, when a report control is located in a container with the KeepTogether property enabled, the PrintOnPage event may still occur for two pages. In such a case a part of the control that is too small to be visible will appear on the second page, ignoring the container's KeepTogether property.
Additional information:
We were able to replicate the issue on our side by using a specific report configuration shared by a customer. We will update this thread as soon as we have any updates on this issue.