15 posts tagged with "ETL"

In this release:

• Sales order line unit prices (breaking change): unitPrice and unitPriceInBaseCurrency now return the values the Visma.net ERP API returns.

In this release:

• Deleted supplier and customer payments: once deletion is enabled for payments, a payment deleted in ERP will be marked as deleted even when ERP does not report the deletion to Data Mart.

In this release:

• Action recommended: where each incremental fetch starts: start each run one minute before the start time of your previous run, not from the most recent updatedInDataMartDateTime you received.
• Deleted records in incremental fetches: a deleted record now gets a new updatedInDataMartDateTime, so an incremental fetch returns the deletion.
• Records deleted before this release: a one-time update on 2026-10-15 returns them once in your next incremental fetch, without a full reimport.
• Timestamps set when records are written: updatedInDataMartDateTime no longer predates the write, so an incremental fetch no longer skips records written while it ran.

In this release:

• Supplier documents, payments and payment lines: synchronization of the new supplier document, payment and payment-line fields, with historical backfills.
• APHistoricalData: new ETL, disabled in Production while testing is in progress.

In this release:

• Customers: field values, customer fields, notes, related-data lookups and reimport.
• Locations: nullable GLN and historical data refresh.
• Contacts: date-of-birth synchronization and historical backfill.
• Branches: branch-name synchronization and historical backfill.
• SalesOrders: field removal and reimport.
• Employees: full-refresh synchronization, soft deletion and attributes identifier import.
• Customer and supplier IDs on lines: line synchronization imports the customer or supplier ID and backfills existing lines.
• GeneralLedgerBalances: removed balances are now marked as deleted, with a one-time cleanup of existing data.
• CustomerPayments and CustomerPaymentLines: cash-document inclusion remains disabled.
• ARHistoricalData: remains disabled in Production.

Production ETL availability​

• ARHistoricalData is disabled in Production while testing is in progress. The AR_HISTORICAL_DATA enum value and API reference are present, but the ETL is not enabled in Production.
• InventoryItems is enabled in Production. The INVENTORY_ITEMS ETL is enabled for inventory item synchronization.

Location sync reports missing Payment By values as null​

Locations with no Payment By value in the ERP now sync with paymentBy and paymentByType set to null. Previously a missing value was silently reported as the default Due Date, which could not be distinguished from a real setting. Locations with an unrecognised Payment By code continue to sync with paymentByType: null while keeping the raw code in paymentBy.

New ETL: Financial Periods​

The FinancialPeriods collection is now synced from the ERP. Each document describes a period in the company's financial calendar:

• finPeriodId, startDate, endDate, description, active and year.
• Per-module close flags: closedInGeneralLedger, closedInSupplierLedger, closedInCustomerLedger, closedInInventoryManagement, closedInCashManagement and closedInFixedAssets.

The collection supports deletion tracking and reconciliation (deletedDatabaseRecord).

Budgets collection reimport​

The Budgets collection has been updated to use the full GLBudgetLine composite key (companyId, branchId, ledgerId, financialYear, groupId, parentGroupId). Sibling budget lines that share a groupId but differ in parentGroupId were previously collapsed under a single document, causing related rows to be lost.

Data Quality Improvements​

• Deletion tracking is now available for all collections except Budgets, GeneralLedgerBalances, and JournalTransactions. The API exposes an includeDeleted filter so integrations can choose whether soft-deleted records are included in query results.