-
-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export all transactions to single sheet #44
Comments
Hey @aadupirn – this isn't an option and I don't plan on supporting it in the near future. The reason we break this up by monthly sheets is to simplify fetching transactions in batch. Each time you run Mintable, it takes your given date range, re-fetches, and then completely overwrites the content of the automated columns. This makes it such that if new transactions come up since the previous fetch, or temporary transactions get removed (a hold on a rental car, a pre-auth for a gas station, etc.), Mintable doesn't need to keep track of an internal state anywhere, we just wipe the slate clean and re-fill the sheet with the most up-to-date data. If you put all transactions in the same sheet you'd need to manually keep track of which transactions you've seen before, de-duplicate those which have already been fetched, keep track of where each month starts and where it ends, so on and so forth. It's a lot of bookkeeping that I think overcomplicates the process. The provider and spreadsheet API should remain as simple as possible – a place to grab your data from, and then a place to dump it. If this is an unsatisfying answer for you – you can kind of "hack this" by taking advantage of Google Sheets' function library. You can use the
You can see this in action in the |
Makes sense, Thanks for the writeup. Would you be interested in a separate config for column names in the google sheet for transaction info? I've added it in a local branch in a TRANSACTION_READABLE_COLUMNS config field. |
Is there a config option to export all transactions to a single google sheet and update that sheet during future transaction retrieval?
The text was updated successfully, but these errors were encountered: