Export to PDF Issue on SQL Console

[kkadir]

Description of bug

When a query result on the SQL Console has long text cells, which are wrapped in the result table; then the first exported PDF is normal but next exported PDF files are distorted as wrapped texts are not wrapped anymore on PDF files.

Steps to reproduce

List the steps to reproduce the behavior:

1. Log in as a Super User
2. Go to Persona Bar > Settings > SQL Console
3. Write a query like SELECT * FROM Tabs and click the "Run Script" button
4. Observe that the result table is generated and some columns like IconFile, VersionGuid, UniqueId and etc. have wrapped long texts.
5. Click on Export > Export to PDF and wait for the PDF to be generated and downloaded.
6. Open the PDF file and see that it is normal; all long texts are wrapped as expected.
7. Click on Export > Export to PDF and wait for the PDF to be generated and downloaded for a second time.
8. Open the PDF file and see that, this time long texts are not wrapped and the PDF layout is distorted.

Current result

PDF files containing long text values in any table cell are distorted after 2nd export.

Expected result

PDF files should be consistently generated as the same without any distortion.

Screenshots

1st Export

2nd Export

Error log

N/A

Additional context

Note that non-wrapped texts do not have any separators or spaces.

Affected version

• 9.3.2
• 9.3.1
• 9.2.2
• 9.2.1
• 9.2
• 9.1.1
• 9.1
• 9.0

Affected browser

• Chrome
• Firefox
• Safari
• Internet Explorer
• Edge

[thabaum]

maybe move this waiting to complete task indicator

to

sure takes a while and this spinner or hourglass replacement is hard to find, should try to center on the screen view if it can or be at the top of the page next closer to the button.

other than that I actually COULD reproduce on a second time so I will take a closer look but this might not be for me...

[thabaum]

trying to export to excel gives this issue

exporting to CSV has the same columns word wrap not being applied to same columns. You can just export once there and it shows this effect.

1. export as csv
2. open with excel

So in a way your lucky to get the PDF to work on the first time it is a miracle it does not do the same thing everytime with or without word wrap on all columns in the table shown.

I think maybe some more thought here can be put into this. I have used all version of html2canvas and jsPDf except the latest and same results each time.

I put a new JS file in, clear cache and restart the app each time. I am not sure if I even need to do all of that as I think I should just be able to replace the JS file and clear cache along with refresh browser maybe someone can help me know if I can skip the restart.

I am leaning towards one of the cs files. And possibly even the database itself?!

Would possibly a stored procedure have this type of effect? @sleupold @valadas I dont see anything that should make this change... but since Excel files dont work properly as well I will be poking more around in that area next time...

it looks like the tab fields that do not wrap are Title, SkinSrc, Container, LastModified IconFileLarge VersionGuiID

vs

All others go behind the next column in excel from a csv file:

[mitchelsellers]

@thabaum The issue with XLS export is due to using the "cheating" way to open in Excel as a regular document. IF we want to log this as a feature request please break this into a separate ticket as it isn't related to the PDF Export.

[sleupold]

usually, export to Excel just creates an unformatted html table and uses file extension .xls to force it to be opened by Excel, when double-clicking the file. Excel will warn, but open properly. There are limited formatting options for HTML to be accepted by Excel, AFAIR.

[thabaum]

@mitchelsellers I can create an issue for this if I find a solution while looking at this problem.

The pdf export looks like the CSV, which you can open in excel and it looks how my screenshots show. I did not open the XLS file. I just closed it FYI.

So if the csv has the same issues that the PDF has in regards to which table columns are not being wrapped. I was showing there is a relation between the two. To much to be a coincidence.

So my question was if possibly this is more related to the database and the way it fetches the data to be presented. I am probably off in the wrong direction here but just wanted to be clear yes or no. I am wondering what is then dictating the CSV file to treat these same columns without word wrap.

So in my mind a possibility is that the CSS from the site skin might be causing the word-wrap initially for the PDF but then once it tries to make it a second time those settings are no longer available as all css is cleared after the pdf is created the first time. So then the second pdf and the csv files just use what the data type is set native to.

[mitchelsellers]

CSV/Excel will not have word wrap issues....your screenshot is an Excel only issue.

[thabaum]

ok so why does the PDF and the excel opening from CSV treat those specific table columns the same