What's new in Xtraction 2026.1

The Xtraction Tool and Sync Tool have been updated to version 2026.1, with the updated version verified across installation, update, and uninstallation scenarios. All interfaces now accurately display the new version, and the copyright has been updated to 2026.

The Output tab has been moved to the second position, instead of the third, in the property section for all components. The functionalities remain unchanged.

A percentage value format has been added to the output tab for all the components. Users can now select percentage formats from 0 to 4 decimal places, like the previous decimal options, and the values will display accordingly with a percentage symbol. This functionality works consistently across components and remains accurate in exported documents or when toggling chart views. All user-selected percentage formats display the correct number of decimal points in both chart and document exports

Xtraction has been updated to ensure full compatibility with Windows Server 2025. Users can install and run Xtraction on Windows Server 2025.

When scheduling a dashboard export, the parameter value now correctly appears in the dialog, which was previously empty. Users can see and change the value before exporting. This issue is fixed, so the export window shows the original value as expected. If a task is already scheduled, users need to edit the task to update the value.

Earlier, dashboards were not cycling or refreshing as expected when using the refresh and cycle URL settings—they would only show one item. This issue is now fixed, and dashboards or documents in a folder will automatically switch and refresh at the set time interval. The system makes sure refresh times stay within allowed limits. Now, users can easily view all their favourite items in rotation using these URL parameters.

Previously, deleting and re-adding tables in the Sync Tool caused records with null values to be omitted during subsequent syncs. This issue has now been resolved, and all records—including those with null values—are consistently retained and synced each time. Users can now delete and re-add tables ensuring that data consistency is maintained across syncs.

The SQL DateTime Overflow Error occurred on multiple NPM database tables due to limitations in the datetime data type, which restricted the range of acceptable date values. As a result, certain values outside this range could not be inserted, causing sync failures and exceptions during data operations. This issue has since been investigated and resolved by updating the affected fields to handle a wider range of date values, preventing overflow errors

There was a sync failure in the Ivanti Neurons for MDM Devices tables when fields contained both dates and text. The problem happened because some columns only allowed date/time formats, so any extra characters caused errors during sync. The fix was to change these fields to use the nvarchar(max) data type, which can store both dates and text. Now, sync operations work correctly and no errors occur. This update makes table syncing for MDM Devices more reliable.