Skip to main content
Skip table of contents

Velixo NX 2025.8 Release Notes – Sage Intacct

Applies to:

  • Velixo NX

  • Sage Intacct

Release date: August 31st, 2025

Version number: 2025.8 or higher

🚀 New:

  • RD-1373 Using a set of 10 new functions (SI.EXPAND…INGROUP), you can now retrieve members of specific dimension groups: Class, Contract, Customer, Department, Employee, Item, Location, Project, Vendor, Warehouse. (RD-1373)

✨ Improved:

  • RD-4184 You can now change the order of columns in the results by reordering fields in Query Builder. (RD-4184)

    image-20250829-074139.png
  • RD-3189 When you select a range for Writeback or Distribution, hidden cells (rows, columns) are now excluded from the selected range. (RD-3189)

  • RD-4191 Transactions posted to adjustment journals in closed periods are now accounted for during Smart Refresh. (RD-4191)

  • RD-4096 Drilldown now respects your date format settings instead of defaulting to North American MM/DD/YYYY. (RD-4096)

🔨 Fixed:

  • RD-4802 An error no longer prevents you from performing a Writeback to fields that are specific to a particular subtype. (RD-4802)

  • RD-4599 In some scenarios where identical non-standard project tasks existed in the system, the balance functions with the Task dimension and IncludeChildDimensionBalances could return incorrect values. (RD-4599)

  • RD-4090 An “API rate limit exceeded” no longer prevents users from logging in to Sage Intacct. (RD-4090)

  • RD-4584 We mitigated a potential backend bottleneck that could result in an “Entity too large” error during writeback. Please note that we still recommend splitting your writebacks into smaller chunks for best performance and reliability. (RD-4584)

🐛 Known Issues:

  • RD-4737 An article is available, documenting a workaround for a problem when including custom fields from parent objects in the Select argument in their SI.QUERY formula (or Query Builder) causes an error. (RD-4737)

JavaScript errors detected

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

If this problem persists, please contact our support.