I have a workflow that pulls from SharePoint, slices into various pieces based on project owner and status, and mails out separate tables based on the project owner's email address. No problem there.
The issue is the formatting of the table. As noted in LisaL's comment here the Email tool does not play well with new lines in data.
Here's how the data flows in from Sharepoint. The "Running Update Detail" field has new lines inserted.
Project ID | Project Start Date | Last Updated Date | Status | Running Update Detail |
54A | 10-30-17 | 10-31-17 | Pending parts | 10/30: Dispatch requested review of functionality. Approved by Scheduling. 10/31: Dispatched agent reported that part code #34B1-LL/A was not functioning and needed to be re-ordered |
23B | 10-24-17 | 10-27-17 | Pending Scheduling approval | 10/24: Dispatch requested review of functionality. 10/24: Due to remote location, Scheduling requested extension of project timeline 10/27: Approval from finance to extend project parameters |
I can see that Alteryx recognizes the new lines because it does flag them in the Results panes.
However when the data is emailed out through Alteryx, the following occurs.
Running Update Detail |
10/30: Dispatch requested review of functionality. Approved by Scheduling. 10/31: Dispatched agent reported that part code #34B1-LL/A was not functioning and needed to be re-ordered |
10/24: Dispatch requested review of functionality. 10/24: Due to remote location, Scheduling requested extension of project timeline 10/27: Approval from finance to extend project parameters |
Since there could be multiple lines of data flowing in per cell, I don't want to split apart into unique fields as in the linked solution because I don't know how many fields I'll need. (And I'm not aware of a "futureproof" method to do it easily if there is one.)
Is there a way to either:
Solved! Go to Solution.
@Prasanna921 Perhaps there is a better way to do this, but I 1) connected the Table tool directly to the render tool to set it up and choose the right field. 2) Disconnected the table tool and reconnected the formula tool to the render.
The render tool says the "Table" field is a bad Field Type but it appears to work.
@patrick_digan Thank you! this worked for me... and it came at just the right time :)
Can you please post your workflow or screenshots that would be very helpful ?
@Prasanna921 The workflow was attached to my previous message, let me know if you have any troubles. Here is a picture where the "Table" field is selected although is complaining about it. It runs without error.
@Prasanna921 It seems to be having an issue when multiple line breaks are in a row. Do you need multiple line breaks? If not, you can change the first formula to
REGEX_Replace([Running Update Detail],"(\n)+","<br />")
If you need multiple line breaks, I'm not sure how to do this...
@Patrick_digan This works for me. Thanks..!
@patrick_digan.. I have been waiting for such a fantabulous solution for for a similar issue for over 2 weeks. Thank You so much for the solution. It is working for me.
Thank you, this solution really worked for me and saved me a lot of trouble