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

[Bug]: OFX Importer "Corrupts" Existing Entries #419

New Issue
Closed
opened 2026-02-28 19:03:23 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-02-28 19:03:23 -06:00
Owner
Copy Link

Originally created by @Silvenga on GitHub (May 31, 2023).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

So there was this bug in non-OSS Actual where importing a OFX file would override existing entries incorrectly. This was reproducible with a clean database and a copy of the OFX files. Maybe @jlongster remembers?

For example, say the following was entered:

5/28/2023 Torchy's Tacos

After importing, the following would be shown:

5/28/2023 Torchy's Tacos (new)
5/28/2023 Torchy's Tacos

But in reality, the old entry was internally linked with a transaction id of Jamba Juice (but the entry wasn't updated for Jamba Juice). From the UI, it looks like transactions were duplicated, but in reality, old transactions were incorrectly updated.

Old Solution (No longer works)

I was using the tool tips to figure out when this corruption happened, but they were removed in https://github.com/actualbudget/actual/issues/567.

Previously, I would use the tool tips to see if this corruption occurred and remove the offending entries (to perform a clean import).

Other Notes

This only happens with Citi Bank (I have multiple cards with them).

What error did you receive?

No errors.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Windows 11

Originally created by @Silvenga on GitHub (May 31, 2023). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? So there was this bug in non-OSS Actual where importing a OFX file would override existing entries incorrectly. This was reproducible with a clean database and a copy of the OFX files. Maybe @jlongster remembers? For example, say the following was entered: ``` 5/28/2023 Torchy's Tacos ``` After importing, the following would be shown: ``` 5/28/2023 Torchy's Tacos (new) 5/28/2023 Torchy's Tacos ``` But in reality, the old entry was internally linked with a transaction id of Jamba Juice (but the entry wasn't updated for Jamba Juice). From the UI, it looks like transactions were duplicated, but in reality, old transactions were incorrectly updated. ## Old Solution (No longer works) I was using the tool tips to figure out when this corruption happened, but they were removed in https://github.com/actualbudget/actual/issues/567. Previously, I would use the tool tips to see if this corruption occurred and remove the offending entries (to perform a clean import). ## Other Notes This only happens with Citi Bank (I have multiple cards with them). ### What error did you receive? No errors. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Windows 11
GiteaMirror added the needs infobugtransaction import labels 2026-02-28 19:03:23 -06:00
GiteaMirror commented 2026-02-28 19:03:24 -06:00
Author
Owner
Copy Link

@Silvenga commented on GitHub (May 31, 2023):

Would it be possible to enable tooltips again, just to aid in tracking down this issue? My worry, there's no error, so it could silently break a database's ids (without understanding how this could happen).

@Silvenga commented on GitHub (May 31, 2023): Would it be possible to enable tooltips again, just to aid in tracking down this issue? My worry, there's no error, so it could silently break a database's ids (without understanding how this could happen).
GiteaMirror commented 2026-02-28 19:03:24 -06:00
Author
Owner
Copy Link

@Silvenga commented on GitHub (May 31, 2023):

Unfortunately, the repo-case was uploaded to the Slack instance, but has since been deleted (free version of Slack).

I'll try and find a new one (took a couple months last time).

@Silvenga commented on GitHub (May 31, 2023): Unfortunately, the repo-case was uploaded to the Slack instance, but has since been deleted (free version of Slack). I'll try and find a new one (took a couple months last time).
GiteaMirror commented 2026-02-28 19:03:25 -06:00
Author
Owner
Copy Link

@Shazib commented on GitHub (Jun 17, 2023):

@Silvenga I think as a temporary workaround you can see the guid in dev tools, e.g. Firefox:

image

@Shazib commented on GitHub (Jun 17, 2023): @Silvenga I think as a temporary workaround you can see the guid in dev tools, e.g. Firefox: ![image](https://github.com/actualbudget/actual/assets/4405777/263dd5b6-310b-4ead-9c37-86de3eaf7b1c)
GiteaMirror commented 2026-02-28 19:03:25 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Aug 26, 2023):

👋 Would you be able to provide reproduction steps and/or demo budget?

Without having reproduction I don't think anyone will be able to assist.

@MatissJanis commented on GitHub (Aug 26, 2023): 👋 Would you be able to provide reproduction steps and/or demo budget? Without having reproduction I don't think anyone will be able to assist.
GiteaMirror commented 2026-02-28 19:03:26 -06:00
Author
Owner
Copy Link

@Silvenga commented on GitHub (Aug 26, 2023):

@MatissJanis it's rather hard since I don't have access to the transaction id anymore, after the tooltip was removed. The workaround proposed by @Shazib doesn't work since that focus id isn't the transaction id that was originally specified in the old tooltip.

@Silvenga commented on GitHub (Aug 26, 2023): @MatissJanis it's rather hard since I don't have access to the transaction id anymore, after the tooltip was removed. The workaround proposed by @Shazib doesn't work since that focus id isn't the transaction id that was originally specified in the old tooltip.
GiteaMirror commented 2026-02-28 19:03:26 -06:00
Author
Owner
Copy Link

@Silvenga commented on GitHub (Aug 26, 2023):

(part of the problem is that I can't upload my whole database to github - making creating a repo exponentially harder)

@Silvenga commented on GitHub (Aug 26, 2023): (part of the problem is that I can't upload my whole database to github - making creating a repo exponentially harder)
GiteaMirror commented 2026-02-28 19:03:26 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 3, 2024):

Closing due to missing reproduction steps.

@MatissJanis commented on GitHub (Mar 3, 2024): Closing due to missing reproduction steps.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug needs info transaction import
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#419
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?