Skip to content

Fill JSON objects in transactions and balances

A technical upgrade operation: it converts the analytics on ledger entries and opening balances into the format the current version works with.

Where to find it: Modules → Database Maintenance → Maintenances → Fill JSON objects in transactions and balances

A worked example

Create JSON objects

No parameters. The service walks the transactions and forward balances and fills in their object-analytics structure. A transaction row that already has this structure is left as it is — only empty ones are filled, by the account's object mask, as posting does. Forward balance rows are all rewritten — from the header's and the row's objects.

Who needs it

A one-off, administrator-level operation. It is run after an upgrade on a long-running database: older records stored analytics differently, and the new version's reports read the new shape.

A fresh database does not need it — new records are created in the right format from the start.

Typical situations

Analytical reports are empty for older periods. A sign the operation was never run after the upgrade.

Not sure whether it is needed. Test on one old period: if the object report is empty while the entries are populated, it is.

Where to look next

  • Rebuild Object Values — a neighbouring operation on another layer: it reassembles the monthly balance store and does not fill the JSON analytics.
  • Transactions — what is being updated.