Weird Excel Headers using Reporting
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi Guys (and Girls)
Today, I was presented with this case:
Using the Reporting tools (a Table & Render), when I select Excel as the destination for the report, the Header names (Field names) are chopped or renamed (in HTML for example, they came out right).
In this case is something like this:
I'm attaching the basic workflow.
Any help would be appreciated.
Thanks in advance
Solved! Go to Solution.
- Labels:
- Reporting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi Alberto,
This is a little strange behaviour. It seems that the render does not like the A4 page layout size (or Letter) when outputting to Excel. The quick fix that I got to work was to change the Paper Size to A3 or B3, however this would then fail if the data was larger than a normal A3/B3 sheet....
It looks like a bug, so would be worth sending to Client Services to be logged. I've attached a version that has data and can be run by anyone to test.
Kane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thanks Kane,
I'll send this to Client Services / PRoduct team to be checked.
Thanks a lot for reviewing and putting the data into it (I really forgot).
Best,
_AG_
PS: I'll try with B3/A3 sizes to see what happens.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @Aguisande
I remember having this issue a few months back which my colleague @oliver_sayers and I investigated. I'm out of the office atm so hopefully he can advise you of the solution that we found.
Thanks,
Joe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi,
In the Render, under 'Report Style' select 'Custom Size' and then edit the size manually until all of the column headings fit.
Thanks,
Oli
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @aguisande,
Please see the attached photo for further guidance.
Thanks @joe_lipski
Oli
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thank you to all...
Even when we can workaround (thanks to your suggestions), is still a bug, right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hola Alberto,
The reason is that your data has too many columns to be fit into the page width requested in the Render tool. The Render is meant to produce document for printing purposes (reports and such). As I would expect, your workflow is throwing a warning message "the current page layout will cause some data to be incorrectly truncated. You may consider modifying how the data is laid out"
If you want to output a larger amount of data with the Render tool, then you would have to change, as suggested, the paper size to custom and increase the page width (the first value), don't be shy increasing that number, it seems that 20 did the trick for your sample data, it depends on the number of columns, I've seen it increased over 140. I think it is working as designed so no cucaracha =)
Let me know if you want to discuss further.
Sr. Manager, Customer Support Engineering
Women & Allies Committee
Alteryx, Inc.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thanks a lot !
Increasing the size works for me, so it should for our customers...
Thanks again! and right..no cucaracha at all!! :P
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Silly question as I realise it's just an example, but why use Render here? The output tool is much better for xlsx data output, I appreciate you can't do formatting then but a formatted Excel report is probably the worst way to deliver this data anyway...
