Skip to main content

Data Mart API - 2026-04-30

Data Mart Team
Visma Net ERP Data Mart

Removed Query Arguments​

includeDeleted argument removed from selected queries​

The includeDeleted argument has been removed from the queries listed below. For these entities the underlying deletedDatabaseRecord field is not populated, so the argument had no effect - it was previously documented as Not active yet for budgets and journalTransactions, and as deprecated for the GL balance queries. It has now been dropped from the schema entirely.

  • budgets
  • journalTransactions
  • generalLedgerBalances
  • generalLedgerBalancesV2
  • generalLedgerBalancesByPeriod
  • generalLedgerBalancesForwardByGroup
  • generalLedgerBalancesForwardExpanded

Existing clients that passed includeDeleted to any of these queries should remove the argument. Behavior is unchanged: results have always been returned regardless of the value passed.

Removed Fields​

deletedDatabaseRecord removed from selected types​

The deletedDatabaseRecord: Boolean! field has been removed from the following types because it is not populated for these entities:

  • Budget
  • GeneralLedgerBalance (was previously marked deprecated for the same reason)
  • JournalTransaction

Clients that selected this field in queries against these types must remove it from their selection set.

Documentation Clarifications​

deletedDatabaseRecord marked as Not active yet on remaining types​

The deletedDatabaseRecord field has been annotated as Not active yet on every object type that still exposes it, with the exception of SOLine and SalesOrderLine where the field is populated. The field remains in the schema for forward compatibility, but does not yet reflect the actual soft-deletion state for the affected types.