This is probably not be a good enough solution as-is and more drastic measures I think are required, namely a partial override of frappe/www/printview.py
There should be three checks/ Payment Entries in this Check Run, only one renders on the preview page due to the inclusion of page break HTML. It's likely that a better technique for previewing page breaks will be required.
Given that one cannot render the Payment Entries of the Check Run until it is submitted, I think it makes sense to return nothing or an error message in that case.
It would also be preferable to have a dedicated page to preview the Check Run and handle that with specific route rules instead of overriding the print preview. This would give greater control of the configuration of the printing, including showing important options like starting check number, etc.
211
This is probably not be a good enough solution as-is and more drastic measures I think are required, namely a partial override of frappe/www/printview.py
Screenshot
There should be three checks/ Payment Entries in this Check Run, only one renders on the preview page due to the inclusion of page break HTML. It's likely that a better technique for previewing page breaks will be required.
Given that one cannot render the Payment Entries of the Check Run until it is submitted, I think it makes sense to return nothing or an error message in that case.
It would also be preferable to have a dedicated page to preview the Check Run and handle that with specific route rules instead of overriding the print preview. This would give greater control of the configuration of the printing, including showing important options like starting check number, etc.