An action to get rows from a text file (CSV) would be handy.
@MattyP You might be able to do this... what does your csv data look like?
Potential workaround I had for a regular scheduled csv report.
Flow saves csv to folder
Have a workbook setup with a data connection pointed to the data in the csv file
Setup vbs file (can just use notepad for this if need be) which opens the workbook and refreshes the data and close the workbook. (Googled to find the code)
Setup a scheduled task in Windows Task Schedular that runs the VBS script at whatever frequency required (you can set it to start a minute after you expect to receive your csv file)
Setup your flow to detect when the excel file is modified and hey presto.
if you dont have batch job rights you have to be logged on for task schedular to run
If your files are on onedrive or a share point synced folder this can cause some delays between saving and syncing of a few minutes (a bug related to task schedular I think)
Even with autosave off I've found my flow will win twice so I had to setup a list item in Sharepoint which is switched to true when flow is running (checked as condition for being false before running) add a 20sec delay near the end of the flow before switching this item back to false. This ensured it only ran once.
I've been told to look into Powershell as a better option over task schedular but dont know enough about it yet
Depending on your data, you may be able to use this.https://powerusers.microsoft.com/t5/Building-Flows/convert-CSV-string-to-table/m-p/162524#M16441
Virtual every automation task that I was looking to implement with flow starts with a CSV. It's somewhat ridiculous that something as common as CSV isn't supported. I'm hoping we can get some bumps and votes on this.
Agreed. I was able to get this to work but it is VERY ugly with a bunch of string splits, piles of variables, loops, conditionals, and very very slow. Native CSV support is a must have.