Replies: 2 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
1 reply
-
@BRTFTW unfortunately we don't have an "easy" way to handle this at the moment other than "reverting" the import entirely. This will erase all the categorizations as you mention, so its not ideal. The fastest (but not easiest) way to change signage conventions would be to reverse the Below is a read-only query that demonstrates this. You'll need to change it to -- All "transactions" with reversed amount
SELECT
amount * -1 as reversed_amount
FROM account_entries
WHERE entryable_type = 'Account::Transaction'; |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So I had some issues importing my transaction csv, because the amount format (1 123.00 standard in my country) is not supported. After editing my csv manually I got it to work but unfortunately, I missed the correct signage_convention this time. And I didn't realise that for another hours or so editing the categories to my liking. Now I am hesitant to delete the transactions and redo the import because of the work already done.
Is there a way to easily fix this from the selfhosting interface? I had a look at the sql database, but messing with the data surely introduces more errors, that maybe wont automatically detect and fix (like changes in balances after switching all the expenses to incomes and vice versa).
Beta Was this translation helpful? Give feedback.
All reactions