Hello All,
I ran into some issues when pulling CSV data in from Power Automate Desktop because of commas in the actual data. I wanted to change the delimiter so I could more easily parse the data in a single Select action without commas in the actual data messing things up. I also may be parsing CSV files with hundreds or thousands of rows, so I didn’t want to use all my daily actions on this in a slow Apply to each loop.
Attached is the scope/flow I built so anyone can easily select their CSV data that has quotes around the comma-containing records, enter a new delimiter, and get the new delimiter separated data from the final compose action without the usual errors. And it only takes a few actions to do this, even on very large files.
I've found that many CSV files don't put quotes around their records with in-data commas, and this only works when there are quotes around those records. But if the file is saved as a text file, then it often puts quotes around the right records.
If you are using Power Automate Desktop, program the file to be saved as .txt and read that into your output variable.
It’s currently set to handle up to 50 comma-containing columns, but you can expand that to as many columns as needed by adding extra lines & expressions to the 1st Select action. Just follow the pattern by replacing some of the array numbers, like [50] with [51].
Also if your data has more unique values like an array with mixed quoted string data, Ex: ["string1", 2, 03/05/2022, "string3"], then this will create errors in the output.
The template for parsing CSV to JSON & entering it into a dataset uses the same change delimiter set-up: https://powerusers.microsoft.com/t5/Power-Automate-Cookbook/CSV-to-Dataset/m-p/1508191#M584
*Copying the template scope into another flow may not work as it may mess up the expressions. You may need to start with a copy of this template and copy & paste the rest of your flow into this template flow.
Thanks for any feedback, & please subscribe to my YouTube channel (https://youtube.com/@tylerkolota?si=uEGKko1U8D29CJ86)
Version 3 Uploaded 03/26/2022 (Adjusted the 1st Select input so it can now also deal with in-data commas in the 1st column. Added more lines to the 1st Select so it can now handle up to 50 columns with commas in them.)
Google Drive Link: https://drive.google.com/file/d/11uT15hXY0VjnOKDvFxdVgkuMtXqTmA0c/view?usp=sharing
Version 4 Uploaded 04/09/2022
(More minor fixes & additions.
I adjusted several expressions so it can now handle a few more scenarios with arrays in the CSV data. It should handle any array that doesn't include double quotes and any array that is all strings with double quotes, so ["String1", "String2", "String3"], but it will have issues if it is a mixed array with some double-quoted strings and some other values, for example ["String", 4, 03/05/2022, "String2"] won't work.
I also adjusted how the LineBreak setting is set-up so it now uses the /r/n for the LineBreak. I also provided this link in the flow so anyone can look up the right string for the decodeUriComponent expression(s) if they happen to have different LineBreak characters. This change also made it possible to differentiate between in-data line-breaks and CSV row line-breaks on the files I tested, so it should now replace the in-data line-breaks, like the multiple-choice fields some sites use, with semi-colons. That should make those records much easier to deal with & parse in later actions.
I also looked over a problem with in-data trailing commas. I added a line in the settings where anyone can toggle whether they want it to adjust for trailing OR leading commas in the data, it just can't handle both in one dataset. So if one column in one row has ",String1 String2" and another column in another row has "String 3 String4," then it will have errors.)
Google Drive Link: https://drive.google.com/file/d/1ZbhFGVKHSpaH2Duv8qXwMnNww8czdgc4/view?usp=sharing
Version 5
More adjustments for comma edge cases and for instances with one comma-containing value following another in the file data.
Google Drive Link: https://drive.google.com/file/d/1il_wI9fJRk11YaI4EPQvk2efrbBNRBwr/view?usp=sharing
Update 06/01/2022
Microsoft Power Platform & Paul Murana recently did a video demonstration of how to handle CSV & other files in dataflows: https://youtu.be/8IvHxRnwJ7Q
But it currently only outputs to a dataverse or Dataverse for teams table.
I have been looking for a solution to these commas as data in csv fields as I have a daily file that is coming in that has a column with currency amounts and may, or may not, contain a comma, and also a descriptor field that also may, or may not, contain commas. Right now I have the creator of this file to go in manually and search for and replace any commas. I really would rather handle this at the power automate level. However, my issue is that the fields are NOT surrounded by quotes. I also tried what you said and saved the file as a text (.txt) file, but still no. Is there a way to include those also? Thanks for the advice. And BTW, I subbed to your YouTube channel also.
Thanks for the feedback. I’ll have to think about this some more for files without quotes around the right lines.
In the meantime, I’d check if the CSV currency column maybe has some different formatting, like maybe it is set as a currency column & it could be changed to a text column.
And if that isn’t the case then there is another way to deal with this situation, it just takes a lot more set-up.
CSV to Excel With Office Scripts: https://docs.microsoft.com/en-us/office/dev/scripts/resources/samples/convert-csv#power-automate-flo...
Video: https://youtu.be/9J6ThPWGaG0
@jtanwm did you try \r\n? Another thing I do for line breaks is something like this as one of my files incoming is a csv file being dumped into SharePoint document library:
Hi @iskguy the issue here is that my data consist of \r\n in the text. Hence having difficulties to splitlines.
@jtanwm
I made a way to easily change the linebreak settings in the flow for the CSV linebreaks. But if you have CSV linebreaks & in-data linebreaks sharing the same /n characters for both, then that is really difficult to deal with.
You may have to use one of the other options for those types of files.
CSV to Excel With Office Scripts: https://docs.microsoft.com/en-us/office/dev/scripts/resources/samples/convert-csv#power-automate-flo...
Video: https://youtu.be/9J6ThPWGaG0
I'm about to test out how easy it can be to swap in the V5 scope in to a flow where I used the V3. - wish me luck!
Also curious about how things are progressing to apply these tactics with DataVerse as the destination
@chico
Thanks for checking in.
For Dataverse, I have to get access to my new company's Azure site first as it requires an Azure account for part of the set-up.
However, I did just start creating a Batch Update Excel template that is progressing really well.
Re: Batch Update Excel - Power Platform Community (microsoft.com)
It could also be copied & adjusted for batch create & batch delete Excel templates too.