github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-11 09:38:37 -05:00
Code Issues 1.6k Packages Projects Releases 57 Wiki Activity

[GH-ISSUE #2052] Emty category rule is not aplying on imported data (CSV, QFX) #7746

New Issue
Closed
opened 2026-04-10 17:44:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-10 17:44:17 -05:00
Owner
Copy Link

Originally created by @Maxiimeeb on GitHub (Dec 9, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2052

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I've encountered a bug with a rule (picture A) where uncategorized transactions are supposed to go into the General category. When I manually add a transaction, it correctly goes to General (picture B). However, when I import a CSV, it behaves differently (picture C, D, E). The bug appears to be related to the NewTransaction function sending {category: null} in JSON, while the import sets it to undefined. When the category is undefined, the eval function in packages/loot-core/src/server/accounts/rules.ts returns false (picture F).
image
b
c
d
e
f

What error did you receive?

The transaction wasn't categorised

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @Maxiimeeb on GitHub (Dec 9, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/2052 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? I've encountered a bug with a rule (picture A) where uncategorized transactions are supposed to go into the General category. When I manually add a transaction, it correctly goes to General (picture B). However, when I import a CSV, it behaves differently (picture C, D, E). The bug appears to be related to the `NewTransaction` function sending `{category: null}` in JSON, while the import sets it to `undefined`. When the category is `undefined`, the `eval` function in `packages/loot-core/src/server/accounts/rules.ts` returns `false` (picture F). ![image](https://github.com/actualbudget/actual/assets/48930628/c9ba0e15-07c2-4828-bc8e-e6bf551874aa) ![b](https://github.com/actualbudget/actual/assets/48930628/ee304070-2d2c-452e-bcf5-648ea9e88117) ![c](https://github.com/actualbudget/actual/assets/48930628/8632ea15-e16f-4b1c-82e3-b8ac7d983671) ![d](https://github.com/actualbudget/actual/assets/48930628/7dccc9bd-4a9e-4c30-b3df-720b312e4954) ![e](https://github.com/actualbudget/actual/assets/48930628/c60e7e40-e91a-4a94-8836-d995e6056b00) ![f](https://github.com/actualbudget/actual/assets/48930628/f48795bf-287e-4b3a-8e01-c0a581b14d80) ### What error did you receive? The transaction wasn't categorised ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the rulestransaction importbug labels 2026-04-10 17:44:17 -05:00
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 rules 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#7746
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?