[GH-ISSUE #7171] [Bug]: Rules override provided transaction properties using API client addTransactions #17235

Closed
opened 2026-04-14 20:08:36 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @benjamonnguyen on GitHub (Mar 11, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7171

What happened?

I was trying to add a transaction with a provided category through the API client.
Expected: transaction to be created with the provided category
Actual: rules are applied

Suggestion: "runRules()" should not override non-null fields

How can we reproduce the issue?

Add rule if payee is P -> set category to C
Use api client add transaction
Provide any category id does not match C. Provide payee_name P
Observe transaction always added with category C

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other

Operating System

Linux

Originally created by @benjamonnguyen on GitHub (Mar 11, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7171 ### What happened? I was trying to add a transaction with a provided category through the API client. Expected: transaction to be created with the provided category Actual: rules are applied Suggestion: "runRules()" should not override non-null fields ### How can we reproduce the issue? Add rule if payee is P -> set category to C Use api client add transaction Provide any category id does not match C. Provide payee_name P Observe transaction always added with category C ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other ### Operating System Linux
GiteaMirror added the transactionsAPIbug labels 2026-04-14 20:08:36 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#17235