cmenon12 / bank-account-to-sheets Goto Github PK

Run this to find out what the changes look like (compare a JSON before & after from Plaid). If the IDs do change, need to be careful matching them up. Consider using a date cutoff to ensure that transactions aren't deleted.

Classes should be created for:

• Transaction - this should be for a sheet transaction because this is what we use most. Include methods for:

  • Comparing with a Plaid transaction, need to be careful with this in case of two identical ones on the same day, include parameter for ID.
  • Importing a Plaid transaction.
  • Updating with a Plaid transaction, need to be careful with IDs & dates.
  • Exporting to a range (one row)
  • Static method to map attributes to header names.

• Account - include totals reported by Plaid but not transactions.

• SubCategory - a subcategory

• ParentCategory - one of the top-level ones. Include methods to get and set subcategories.

Use JavaScript dates throughout. Need to include required getters and setters for objects. The 'last mile' of writing to the sheet should be handled procedurally, but these classes should prepare the data for it. Think carefully about headers.

Need to implement more IDs (pending and transaction) to maybe make updating more effective. Think carefully about dates, IDs, and updating with new transactions (need to look at how this is currently implemented). Fixing the broken updates when the access token changes is out of scope here (see #10).

Object classes should be defined in a separate file. Don't make any changes to the sheet (but do include additional fields that might be useful later). This should not change how it works for the end-user (we're not improving anything), merely the backend structure to make it more extendable and maintainable.

See https://github.com/cmenon12/contemporary-choir/blob/main/google-apps-scripts/the-new-ledger/ledger-checker-classes.gs for an example.

I'm using plaid - and the way you have created the spreadsheet is amazing - rolling up totals - especially the first 3-4 columns.

Add total for pending transactions that are unaccounted for (i.e. where the difference between current balance and available balance isn't the same as the sum of the pending transactions).

• Add an 'account' column to the sheet.
• Display total amounts on a per-account and combined basis.

Make dates from both existing and Plaid JavaScript Date objects as soon as they are fetched, for consistency.

Use the onEdit(e) trigger to update the data validation for the subcategory column dynamically, restricting the possible values to match the corresponding category. This will need to apply when the transactions are updated and when the category is changed.

I got it working like this.
For my use case - I have some power users (not tech) who need access to changing this value.

Make it clearer which is being used where. Could use ptransaction and etransaction?