[PR #6123] [MERGED] docs: update api reference for incorrect category parameter #113156

Closed
opened 2026-06-05 19:27:09 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/6123
Author: @mstill3
Created: 11/12/2025
Status: ✅ Merged
Merged: 11/12/2025
Merged by: @matt-fidd

Base: master ← Head: patch-1


📝 Commits (3)

  • a3d4714 docs: update api reference for incorrect category parameter
  • 9d5e3b5 Merge branch 'master' into patch-1
  • 11c9673 remove release note

📊 Changes

1 file changed (+3 additions, -3 deletions)

View changed files

📝 packages/docs/docs/api/reference.md (+3 -3)

📄 Description

Rename category_id attribute to category since thats the expected field and how it is stored in the database.

Discovery

I noticed this when trying the example listed on the api documentation and received the following error:

actual/myapp/node_modules/@actual-app/api/dist/app/bundle.api.js:14112
            throw new Error(`Field “${field}” does not exist on table ${table}: ${JSON.stringify(obj)}`);
                  ^

Error: Field “category_id” does not exist on table transactions: {"id":"abc123-def456-ghi789","category_id":"ghi123-def456-abc789"}`

Solution

When looking at the local db.sqlite file the transactions table has a field not named category_id, but a category TEXT field (which by the way is not a foreign key, which may be another issue).


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/6123 **Author:** [@mstill3](https://github.com/mstill3) **Created:** 11/12/2025 **Status:** ✅ Merged **Merged:** 11/12/2025 **Merged by:** [@matt-fidd](https://github.com/matt-fidd) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (3) - [`a3d4714`](https://github.com/actualbudget/actual/commit/a3d471483729ac4f3a6bb06d30b4a77377fd2b8e) docs: update api reference for incorrect category parameter - [`9d5e3b5`](https://github.com/actualbudget/actual/commit/9d5e3b5939455e6e3c187a4113234a2c726f1ec3) Merge branch 'master' into patch-1 - [`11c9673`](https://github.com/actualbudget/actual/commit/11c9673f85608363780e6187ca2679c38326f836) remove release note ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `packages/docs/docs/api/reference.md` (+3 -3) </details> ### 📄 Description Rename `category_id` attribute to `category` since thats the expected field and how it is stored in the database. ### Discovery I noticed this when trying the example listed on the api documentation and received the following error: ```text actual/myapp/node_modules/@actual-app/api/dist/app/bundle.api.js:14112 throw new Error(`Field “${field}” does not exist on table ${table}: ${JSON.stringify(obj)}`); ^ Error: Field “category_id” does not exist on table transactions: {"id":"abc123-def456-ghi789","category_id":"ghi123-def456-abc789"}` ``` ### Solution When looking at the local `db.sqlite` file the `transactions` table has a field not named `category_id`, but a `category` `TEXT` field (which by the way is not a foreign key, which may be another issue). <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-05 19:27:09 -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#113156