The Table tool from the Reporting tab is removing double spaces

[jmwagner]

I have created a workflow that puts together a table which then gets exported to excel per a certain group. There is one field in that table which contains folder paths. We have an instance where the folder path has a double space in it. When creating the output I want the folder paths to be untouched. When processing it through the Table tool it removes double spaces. Is there a setting that is causing this or is this a default procedure with the Table tool?

Thanks in advance.

[atcodedog05]

Hi @jmwagner 

Reporting tools using html logic at back end hence all double spaces and line breaks are removed. Follow the below post to insert the double space as required. 

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Working-with-wanted-line-breaks-and-th...

Hope this helps : )

[atcodedog05]

_

[atcodedog05]

Hi @jmwagner 

Here is how you can do it.

Workflow:

Output:

Reference post: https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Table-tool-removing-double-spaces/td-p...

Hope this helps : )

[DataDynamite]

I used this idea within a workflow that I needed to render to our Gallery with .pcxml.  The replace using " " worked on desktop but didn't in the gallery.  I found replacing with En Space (" " ) did work.    

Thanks!   DD

[RHehlmann]

Is there any way to achieve the same result with a normal space instead of a non-breaking space? The data I output using the table->render tool is afterwards used to be compared with a SAP output. Some of the data from SAP has double white space. If I use #160 space, the match via excel with the SAP data fails, as SAP uses the regular #32 space. But if I use #32 after my table tool, the render tool still removes double spaces.

[apathetichell]

@RHehlmann I wouldn't recommend using Render here --- use an excel template and write data to that template sheet ---- and keep existing formatting.

[RHehlmann]

@apathetichell that is unfortunately not an option. I use my outputs for a variety of clients and it's only the data for that one client where there are embedded double white spaces. Also, there are some dynamic elements in the outputs that make using templates not feasible.