Hi - I currently have a workflow setup so that it downloads a CSV file from Box to Okta and then from there, I have an import to CSV action card to import it to an okta table. Unfortunately, the headers from the CSV have a ‘.’ in them and so I’m getting an error when trying to map them to the okta table columns. Is there a way to map them so that the headers will match to the table columns, with the period?
I’ve tried mapping them in the Import to CSV card as an object with key:value but that didn’t seem to work either. For example ‘Employee.Identification.LastName’ to ‘EmployeeLastName’ doesn’t seem to import over the data. Any ideas how to to map it?
Hi @MC_bpham: welcome to the forum!
So, does the CSV file have a column named ‘First.Name’, and do you want to map it to a table with the same column name? Or could the table name be different?
Could you share screenshots of the column names from the CSV and the table?
Hi Max, attached the CSV headers, and the okta table columns. The CSV headers are fixed, so I can’t change it, but the okta table columns, can be a different name. But when trying to map it in the action card, I can’t get the CSV header to successfully map.
I tried several things, but none worked. Today, importing a CSV file with such column names is impossible.
Not ideal, but would something like this work for you?
- Download the CSV file
- Upload the CSV file to Google Sheets
- Rename the columns
- Download the CSV file from Google Sheets
- Import the CSV file into a table
Well, I typed (responded) too fast.
Upon further checking, this is a bug, since directly importing a CSV file with a column name containing a dot works.
We have created a bug ticket for it.
Thanks Max, I was JUST about to test uploading to google sheets. Would I get any update on when I can potentially test the fix?
The fix should be listed in the Release Notes.
You can also post here for an update or email me.
Also, creating the columns in the Okta tables with the ‘.’ character says it’s not allowed because it’s a special character. Is that a restriction? I am able to use other characters like the ‘_’, but no period. Just trying to match the headers exactly.
Correct, creating a Workflows table with a dot in the column name is not possible.
The bug fix will allow importing from a CSV with a dot in the column name into a Workflows table.
Hello everyone!
Having the exact same issue - do you know if it will be in May release notes?
Thanks for your help
I don’t have a timeline for the fix. It is unlikely to be fixed in May.
If renaming the CSV file column names is not an option, consider the solution here Importing CSV into Workflows Table - #4 by maxkatz
