I have a question about the Import CSV Line Items workflow from Tiller Community Solutions.
I use it to import AppleCard transactions. Recently, after an import, I tried to split one of the transactions and got an error message-- something like “transaction must have a transaction ID”. I went back and looked at all of the imported AppleCard transactions and, sure enough, none of them had transaction IDs (or account ID, for that matter). As a workaround, I generated a unique transaction ID and put it in that column, and then Tiller allowed me to split the transaction.
I guess my questions are:
Could a feature be added to the workflow to automatically generate transaction IDs?
Is there any downside to the Account ID column being blank for all of these imported transactions?
Thanks.
P.S. In case anybody’s interested, here’s the formula I used to generate the transaction ID:
It will produce something like “18f3ade1a64eb5754830b82b”. Once you have your generated ID, copy it and “Paste Values Only” into the cell where you need it.
I apologize for the limitation about creating splits for transactions with no transaction id. @heather has flagged this for development work. We published the fix to Excel and the work in Sheets is partway done. I’m hoping that we will have this testing and live in 2-4 weeks (some other work has been prioritized ahead of it).
So… rather than adding a feature to the workflow to generate transaction ids, the solution we are progressing toward is to just remove the requirement in both Sheets and Excel.
The blank Account Ids are not really an issue unless some of your workflows or templates filter on them. It’s not too hard to find the appropriate account, filter on the AppleCard transactions, and drag the account information down the new cells if it bothers you.
What is the status of this? It would be great to preserve unique transaction ids so that tools like Ai AutoCat (github . com / gregorrothfuss/ tiller_ai_autocat) can continue to work. I tried the workaround Hosferich offered but the ids were not stable, so I had to manually create transaction ids by mashing my keys Thanks!
Hi @rothfuss there currently isn’t a timeline for this update. For greater context, our product team prioritizes bugs, issues, and requests based on the severity of the issue and how many customers are impacted or requesting this feature. The timeline is based on the team’s current existing log of issues and upcoming feature releases which is subject to change.