Skip to main content
Skip table of contents

Velixo NX 2025.9 Update Pack Release Notes

Update Pack 2 (2025.9.302)

Release date: October 20th, 2025

✨ Improved:

  • You can now use the BC.BUDGETTURNOVER function to retrieve turnovers for a range of budgets provided in the Budget argument. (RD-6325)

Update Pack 1 (2025.9.260)

Release date: October 15th, 2025

🚀 New:

  • The new BC.DIMENSIONNAME function lets you retrieve a dimension name tied to the specified dimension code. (RD-6032)

✨ Improved:

  • The BC.EXPANDDIMENSIONRANGE function now retrieves dimension codes instead of their names. (RD-6031 )

  • Improvements in the BC.WRITEBACKBUDGET function:

    • Multiple amounts and dates are now supported per function – simply use equally-sized arrays for Date, Amount, and (optionally) Description arguments.

    • You can now use any dimensions in budget lines (even if they are not a part of "declared" budget dimensions). This is consistent with BC behaviour. (RD-5804)

    • A new EntryNumber output argument lets you provide an array of entry numbers that identify the GL entry to be updated – it can be specified only for the by-entry-number update mode. (RD-5802)

    • We have introduced three Budget update modes

      • by-entry-number, which requires specifying the internal ID for update (see the output argument above). If the ID is not specified, a new budget entry is created.

      • recreate – recreates the entire budget. Be careful with using WRITEBACKCOMMIT.

      • by-natural-key – "smart" mode where you can specify a set of columns (such as the date, account, dimension values) by which Velixo will decide whether to update an existing budget entry or to create a new one.

  • If unused, columns in a mirrored table are now deleted after mirroring finishes. (RD-5621)

  • We clarified the warning dialog displayed when key columns for a mirrored table are changed. (RD-5620)

  • When creating a connection, the connection name is now pre-filled. (RD-5583)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.