This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Absolutely agree with you Chris, but no matter how many times you think it (and tell it to the user / customer), it appears that the "frustrated Graphic Designer" or "Graphics Designer wannabe" we all have inside comes to life and takes control of our Excels! Forcing us to add Headers, colors, and a lot of "pretty stuff"...
Anyway, it was a sample, because the original data is a confidential survey analysis from a Customer, and they wanted it that way to be able to filter the results later.
If you have a workflow which may generate different columns (more or less) and so are unable to plan for how wide of a document you may need, there is another workaround.
In the Table tool, set the sizes of the existing columns you have coming in to a fixed width. For example, in mine I have them all set to a fixed width of 2 inches. Then, set the options for dynamic or unknown fields also to a fixed width or 2 inches. No more manual adjustments!
I'm working on a build that renders as .xlsx as well. I'm rendering this rather than using and output data tool because I need hyperlinked text within a certain field. Due to rather large number of columns I changed the Render Configuration to Paper size B3 and orientation Landscape. This solved the truncated data issue for me.
I'm still experiencing an error with the hyperlinked field. Here is my Report Text tool configuration:
I'm not receiving any errors or warnings after running the workflow, but when I try to open the rendered excel file I'm getting this message:
If I remove the hyperlink field the file is created and can be opened without issue. Any thoughts?
I am also able to "fix" the truncated headers and data by making the paper size wider. But, I would like to not have the columns so wide and just have the smaller columns in excel with the headers and data wrapped. It still seems like a bug that the headers and data are truncated, is there a plan to fix this? I also do not get a warning when running the workflow that there is truncation happening, so if I hadn't looked at my output first there is no indication of lost data.