github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-11 12:43:09 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[WIP] Clarify post-processing in add/importTransactions (#438)

Browse Source 
Clarify that `importTransactions` runs rules
This commit is contained in:
Tobias Diez
2024-08-18 22:14:02 +02:00
committed by GitHub
parent 96f480ef3c
commit 7e2439f781
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/api/reference.md
View File

@@ -183,7 +183,9 @@ This method is mainly for custom importers that want to skip all the automatic s
<Method name="importTransactions" args={[{ name: 'accountId', type: 'id'}, { name: 'transactions', type: 'Transaction[]'}]} returns="Promise<{ errors, added, updated }>" />
Adds multiple transactions at once, but goes through the same process as importing a file or downloading transactions from a bank. You probably want to use this one. Returns an array of ids of the newly created transactions.
Adds multiple transactions at once, while going through the same process as importing a file or downloading transactions from a bank.
In particular, all rules are run on the specified transactions before adding them.
Use `addTransactions` instead for adding raw transactions without post-processing.
The import will "reconcile" transactions to avoid adding duplicates. Transactions with the same `imported_id` will never be added more than once. Otherwise, the system will match transactions with the same amount and with similar dates and payees and try to avoid duplicates. If not using `imported_id` you should check the results after importing.