Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.
Free Trial

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Carriage Return (aka New Line or Line Break) being ignored in Report Table Tool

I know this has been posted before, but the posts are fairly old, and I have just confirmed with Support that it is still an issue.  Seems to be a pretty basic request, so I'm putting it out there again under this new heading.


The issue is that if you have data in a field, and you have that data separated by a new line (\n), it will show up fine in a browse tool, or pretty much any other output (database file, Office Document file, etc.). But if you try to use the Table Tool under Reporting, it ignores the line break and strings the data together.


Example:

The field data looks like this in a browse or most other outputs:

Hello, my name is 

Michael Barone

and I love

Alteryx

 

But when I try to pull this field into a Table Tool, it shows up like this:
Hello, my name is Michael Barone and I love Alteyrx

 

Putting this out here again in hopes that it gets lots and lots of stars so it gets put on the road map!!

 

27 Comments
mbarone
16 - Nebula
16 - Nebula

Thanks Alex, and thanks for the workaround JFR!

ColinG
7 - Meteor

I've lost hours of my life to this bug today, before discovering this thread that it's a long known bug. I kept finding different suggestions on the forums for ways to create carriage returns within fields hoping one would work when used in a report text tool, then render to PDF tool. Finally after my 4th attempt I realized it was probably a bug specific to the report text tool and not just another idiosyncracy of the overall toolchain, that would work with the right incantation.  

alexnajm
17 - Castor
17 - Castor

+1 on this! Someone just dealt with this today...

NicolasFabre81
8 - Asteroid

I can't believe we have still no solution on this 7 years later ..?

NicolasFabre81
8 - Asteroid
ColinG
7 - Meteor

That looks like the same thread I found when I was having this issue, tried reimplementing it in my workflow, and as bccpwc said, it didn't work for me. If not it, the proposed solution looks familar. Alteryx just reprinted the html tags into the end report, and did not put in line breaks.

I found I think 3 similar threads on Alteryx forums with potential workarounds, and none worked for me. Though it looks like I didn't bookmark them to know which ones I tried. In at least one of the threads besides this I posted it didn't work. Now I wish I did it in every thread but I felt that was redundant and could be seen as petty if someone was tracking all of them.

 

When I have time I may read all 4 pages, and try one last time. Thanks for the post as something to try.

NicolasFabre81
8 - Asteroid

The key point is to put this after the table tool. I just did it and it works perfect with my PDF output.

2024-09-27 16_31_10-Alteryx Designer x64 - solution pb saut de ligne.yxmd.png