Glad to hear the google process is…..progressing!
Interesting - you have no Account_ID column? You can certainly add one - exact string is “Account ID”. But where did mine come from? I just tried creating a new Tiller sheet from my.tiller.com, and I do see an Account ID column - but it is hidden. Can you confirm that it’s present but hidden?
I think you’re referring to the Tiller “Account Id” column. That is a unique account identifier we use to manage accounts. A stretch goal for this kind of workflow would be to allow a user to map an credit card account number from the Amazon export to a in-spreadsheet Tiller account (e.g. the account id/name/number as captured in Tiller) and then map the account information from Amazon to the Tiller values for consistency within the spreadsheet.
yes, I’m familiar with it, I was just trying to figure out why this person did not have an account ID column. But maybe it’s just hidden?
The application does in fact fully populate account, account number, account ID, institution, transaction ID, month, week, date added,source, Meta data. The account information is calculated based on a user specified mapping table. unrecognized Amazon payment types cause a hard stop to the import process and a message to add the necessary entry to the look up table.
So I did find the account Id, hidden on the accounts sheet, so I have the id’s now but I do not show one on the transaction sheet. I will do more looking and see if it is hidden. What column is yours on the Tiller transaction sheet?
if you’re asking about which columns the import tool depends on on the transaction sheet, they are listed at the bottom of the AMZ Import sheet.
| Name in Code | Tiller label |
|---|---|
| SHEET_NAME | Transactions |
| DATE | Date |
| DESCRIPTION | Description |
| AMOUNT | Amount |
| TRANSACTION_ID | Transaction ID |
| FULL_DESCRIPTION | Full Description |
| DATE_ADDED | Date Added |
| MONTH | Month |
| WEEK | Week |
| ACCOUNT | Account |
| ACCOUNT_NUMBER | Account # |
| INSTITUTION | Institution |
| ACCOUNT_ID | Account ID |
| SOURCE | Source |
| METADATA | Metadata |
My tool does not create any new columns, just uses the same columns used by the prior Community CSV tool. However, for those that have not ever run that tool, it turns it that older tool may have created a new column called Metadata. I thought it was part of the Tiller template, but I just updated the code to insert this new column if it does not exist.
WOO HOO! App was finally approved. You can install it here: https://workspace.google.com/marketplace/app/tiller_tools_by_dave/135351721412
It does not have the fix to automatically create the Metadata column if it doesn’t already exist, but otherwise has no bugs. If you’ve never run the Community CSV importer before, you’ll need to insert a new column on your Transactions sheet called “Metadata”
I’m hesitant to publish the Metadata auto-insert update until I get more feedback on this release.
Thank you! I’ve been quietly monitoring this thread. Just installed and imported my transactions YTD. Lots of great features that improve over the old tool, like the ability to import the whole zip file at once and input an “oldest date” for import. I did have to add a Source column but that’s a one-time effort. And I did have to manually add a few payment methods that weren’t automatically detected. Overall great work!
That’s gratifying to hear, considering how much work it was.
So strange that some people don’t have the columns that I have. I will add code to insert a missing Source column. On my template, it’s populated only by the Yodlee feed and my CSV import. I assumed that since Yodlee import used it that it must be part of the base Tiller Template.
By “manually add a few payment methods”, are you saying that:
- You left the “check payment methods” box checked
- Only of your payment methods were listed, not ALL?
Great, that helped me track it down. I’ve just pushed these 3 changes to Marketplace:
- Create Metadata column if missing
- Create Source column if missing
- Properly handle similar Amazon payment sources
Back to zero bugs (for the moment…)
The columns that get included in the template change over time. Like the Source column didn’t get introduced until sometime after there were multiple source aggregators. A template generated today will have different columns and sheets then a template generated three/four years ago.
I was aware of some changes over time, but I thought the feed code added columns on the fly to keep structure consistent. Bad assumption. My template was created November 2022. I guess I’ll have to wait and see if there are any other people with missing columns.
My template was created 2019, my transaction sheet does not have a Account ID column. I did create a new sheet and Account ID column does show up (hidden) or otherwise, as column. I do know how to add a column but now how to have the id’s populate.
Also, I did download the app and obviously have the same issue.
We have added some new columns over time with some additions in the past year targeted at multi-aggregator and pending-transaction functionality. These are generally added only to the Foundation Template for inclusion in new spreadsheets and not automatically added into existing spreadsheets. (Perhaps @heather will know if we auto-added some columns for pending or Plaid aggregation experiments…)
Users with longtime spreadsheets can manually add the new column headers and they will fill for new rows (but do not backfill).
How do I get the added Account Id column that I add to my transactions spreadsheet to populate?
for my Amazon import process, if your account ID column label exactly matches the account ID column label defined on the AMZ import tab, then the account ID will populate the next time you do an import and insert new transactions. I assume the same is true for the Yodlee import.
That’s assuming you have also defined the correct account ID value in the Amazon payment method mapping table at the top of the AMC import tab.
I have been a very happy user of this tool, and Dave’s excellent support, prior to this release, using the manual install process.
Great news on this, Dave. And congrats on getting through all those hoops!
Can you assure me that reinstalling using this new release will simply overwrite my existing installation, and I need not first uninstall the old manual installation?
Thanks for all you do!
I would suggest you remove all the old code or at least the auto open in the code.GS file. That way you won’t have duplicate menu items.
thanks - this worked perfectly.