What is the goal of your workflow? What problem does it solve, or how does it help you?
One of the challenges to importing CSV data from unsupported data sources is remapping the columns to match the Transactions
sheet. Further, some columns (like Month
, Week
, Date Added
, etc) contain derived data.
The goal of this workflow is to simplify and improve the accuracy of this process.
How did you come up with the idea for your workflow?
I built the Import CSV Line Items workflow in the Tiller Community Solutions add-on, but I know many users have CSV data sources that are not supported.
Please describe your workflow. What are the sheets? Does it use any custom scripts or formulas?
This workflow requires you to add bound scripts to your spreadsheet to perform the following actions:
- Requests sheet name of your imported CSV data
- Maps imported data to
Transactions
sheet headers per the column mapping in the first row (see below) - Creates new rows at the top of the
Transactions
sheet & inserts the data
Detailed documentation & script files are available in my csv2transactions project on Github.
I’ve also posted a video demo to walk you through:
- Installing the project script files
- Configuring your column mapping for your CSV data source
- Running the import process
- Learning a few power-user tricks
Is it ok for others to copy, use, and modify your workflow?
Of course.
Anything else you’d like people to know?
This script works with Tiller Money spreadsheets but it is a personal project not created, published or maintained by Tiller Money.
Let me know if you have any feedback!