Paginated Report table text glob

I have a report that for unknown reasons has started to overlap text in the table cells, and I'm pretty dumbfounded on what happened, i.e., what I might have done to change a setting somewhere. Example:

image

should look like:

image

The left cell is a simple formula: @Shift.production_day@
and the right cell is another: Shift @Shift.shift_number@

What might cause this? We're running 8.1.15.
The first image is what we get in the PDF output (sent over email)
The 2nd image (which is readable) is what I get in the Designer.

Selecting a label and setting Text Properties → Character Spacing = -6 does it for me. Check that property to see what value it has.

Interesting idea, but this mashes up the spacing both in the designer and whatever output. My problem is that the design view, preview, and etc. in the Ignition Designer looks as it should; but the PDF produced for the email distribution is mashy/globby.

Additionally: the report as viewed in a Perspective ReportViewer object also is messed up.

Sorry, I was unclear. I meant that I can reproduce your problem by setting Character Spacing = -6 and that you should check that your settings are = 0. I didn't appreciate the difference you were describing. It sounds like a PDF corruption of some sort.

What's the font set to in this table?
Can you reproduce in a brand new report, or only in your existing report?
Can you upload one a PDF demonstrating the problem here?

Yes, Character Spacing = 0.
Even setting character spacing to 6 doesn't work.
Font is Dialog.plain 12.0 (Dialog)

Update: creating a new "test" report that just has the query to get the shift number, new simple table. In the same project. Still busted.

I'm not sure if I can share the project here because it has sensitive production information.

You should open a support ticket. IA support can work under any reasonable NDA.

2 Likes

Support ticket submitted. Thanks.

Hi @Andrew.Meronek
I know it's an old topic, but I'm facing the same issue on 8.1.38, suddenly all the reports messed up like that.
Did you find what caused the issue and find a solution?