01-09-2020 01:07 AM - last edited 01-10-2020 01:21 AM
Title: Import CSV File
I have created a csv import 2.0
It is smaller and simpler.
Find it here
Description: This flow allows you to import csv files into a destination table.
Actually I have uploaded 2 flows. One is a compact flow that just removes the JSON accessible dynamic columns.
You can easily access the columns in the compact version by using the column indexes . . . ,,, etc...
This step is where the main difference is at. We don't recreate the JSON, we simply begin to write our data columns by accessing them via column indexes (apply to each actions). This will cut down in the run time by even another 30% to 40%.
** If you need to add or remove columns you can, follow the formatting and pattern in the "append json string items" and anywhere else columns are accessed by column indexes with 0 being first column -- for example "variables('variable')" or "split(. .. . )", etc.. .
Import the package attached below into your own environment.
You only need to change the action where I get the file content from, such as sharepoint get file content, onedrive get file content.
My file in the example is located on premise.
When you change the get file content action it will remove any references to it, this is where it belongs though.
Please read the comments within the flow steps, they should explain the using this flow.
Be sure to watch where your money columns or other columns with commas fall as they have commas replaced by asterisk in this flow, when you write the data you need to find the money columns to remove the commas since it will most likely go into a currency column.
Also check the JSON step carefully since it will let you access your columns dynamically in the following steps.
You will need to modify the JSON schema to match your column names and types, you should be able to see where the column names and types are within the properties brackets.
In this step of you JSON notice my values have quotes because mine are all string type, even the cost.
If you have number types remove the quotes (around the variables) at this step where the items are appended and you probably need to replace the comma out of the money value (replace with nothing).
This step will control how many records you are going to process.
The flow is set up to process 200 rows per loop and should not be changed or due to the nesting of loops it may go over the limit.
It will detect how many loops it needs to perform. So if you have 5,000 rows it will loop 25 times.
You should change the count though. Make sure the count is over the number of loops, the count just prevents it from looping indefinitely.
Note: This flow can take a long time to run, the more rows with commas in the columns the longer.
9-25-20 - A new version of the flow is available, it is optimized and should run 40% to 50% faster.
Questions: If you have any issues running it, most likely I can figure it out for you.
Anything else we should know: You can easily change the trigger type to be scheduled, manual, or when a certain event occurs.
The csv file must be text based as in saved as plain text with a csv extension or txt in some cases.
Note: any file with csv extension will probably show with an excel icon.
The best way to find out if it will work is to right click it on your computer and choose to open it in word pad or note pad. If you see the data it will work. If you see different characters it is an excel based file and won't work.
An excel based file is of type object and can't be read as a string in this flow.
You can easily convert it by saving excel file as CSV UTF-8 comma delimited in save as options.
It should also work on an excel file without table format as long as you convert to csv the same way and same extension requirement.
** If the file is on sharepoint go ahead and save as csv utf-8 and then change the extension to .txt or sharepoint will force it to open as an actual excel spreadsheet file.
you may also need to use .txt extension from other "get file contents" besides sharepoint. I know for a fact on premise can stay as .csv extension.
My sample run of 12000 rows, this sample has 10 columns, you can have any number of columns.
Can you clarify on setting the connector where I open the file from? I have OneDrive for Business set up as a connector, but it doesn't show up in the list. My connector list is blank when I try to set it.
Does it have to be a network path that is accessible through the on-prem gateway?
In the step where I open from the network you can replace it with onedrive.
So I need to update that, it should say select an action to get the file content with, which could be sharepoint, onedrive, etc...
You should be able to open the csv file from one drive.
Right. But I cannot get to the flow. When I import, I have to make two selections in reviewing the package content, the CSV import, and the file system connection. The file system connection does nothing. It doesn't recognize OneDrive for Business or any of the SharePoint connectors as a valid file system. Make sense? Or am I totally missing something?
The problem @EdHansberry is facing is the same for me and for all people that will try to import your flow: you cannot change the resource type to access the CSV file during the import phase. And since your flow's resource type is File System Connexion, if one wants to import your flow in its tenant, it needs to create a File System Connexion and define a local gateway, ... which can be a bit harsh.
May be if you could provide another version of your flow with a OneDrive or SharePoint connexion... 😉
Note to all: you can find attached to this reply a similar flow with a connexion to a SharePoint document library where you can put your CSV file.
Ok, I have uploaded a new one using sharepoint as the default start.
Also notice that in sharepoint the extension should be .txt after using the csv utf 8 save as if you had to convert it.
I have a CSV file that consists of 12 columns, can this script be able to accommodate that?
Update: I received below error when I tried to upload the csv file; I guess the answer is no
Yes, it can handle any amount of rows.
It is not specific to rows.
You just need to build the columns in the append json and JSON schema and anywhere columns are read or written.
Your error "out of bounds" means that there was nothing to access such as a blank data or line....
I'll post for you a sample with 12 columns. Or you can provide me a sample.