I have a couple of tables on a form that are dynamically filled using the lookup rules pulling the rows needed from a database view. One of the tables has 18 rows and when the form is submitted, only 17 rows show up on the saved PDF. See attachments on the form in the workflow and the form that is emailed/saved to the repository and how the table is set up on the form. We are on the version: Professional Version 11.0.2311.50553 - self-hosted
Question
Question
Answer
Do you have any show/hide field rules set for your table? Or any CSS that might be affecting it by chance?
This person fixed it by removing a bit of CSS that was setting the .fl-component padding to 0, although they also mentioned it's a known bug, so hopefully someone from Laserfiche can chime in if it's not a simple fix for you.
Replies
Yes, I am using CSS to format the table to condense it (borrowed from somewhere else in this site) - just weird how all the other tables on my form don't have this issue, but just this one, which happens to be the longest one. Here is the CSS for the .Eval_Table, which is the CSS class that I'm using on all of my tables:
.Eval_Table .cf-field {padding : 0px!important;}
.Eval_Table table td {height : 16px!important; line-height: 16px !important;background: #ffffff !important;}
.Eval_Table table tr {height : 16px!important; line-height: 16px !important; background: #ffffff !important;}
.Eval_Table table input {font-size:13px; background: #ffffff !important; border: none !important;}
.Eval_Table table th {
background: #000000;
color: white;
text-align: left;
}
.Eval_Table .ng-star-inserted {padding : 0px 1px 0px 1px !important;}
I wonder if you were to force a page break before your table, if stopping it from breaking in half would potentially fix your issue?
Try adding this and seeing if it works for you:
.Eval_Table {page-break-before: always !important;}
Editing to add:
Sorry, just realized you're using .Eval_Table for all of your tables! I would add a second CSS class to the problem table and use that instead.
For instance:
.PageBreak {page-break-before: always !important;}
This did cause the page break, however, it cut off the table even more - after row 10:
Well, that's even more bizarre. Maybe try adding a break after as well, so the only thing on that page is the table?
.PageBreak {page-break-before: always !important; page-break-after: always !important;}
It puts in the page break after the table, but still only shows 10 rows on the PDF:
Oh man, I'm stumped!
I've had multi-page tables without any issues, so it really does seem to be something with the 0 padding CSS causing it to go wonky, although I can understand not wanting to remove that.
Hopefully someone smarter than me can figure it out for you!
I played with the CSS some more and changed this:
.Eval_Table .ng-star-inserted {padding : 0px 1px 0px 1px !important;}
to this:
.Eval_Table .ng-star-inserted {padding : 1px 1px 1px 1px !important;}
and that seemed to do the trick (I omitted the page breaks):
There a little more spacing on the table than I prefer, but I can live with it.
Well, I'm glad you got it (mostly) sorted!
Thank you so much for your help!!
No problem at all!