What's new in Xtraction 2025.3

In earlier versions of the Data Model Editor (DME), there was one .dat file that stored both data source and database connection details. Prior to 2021, these were split into two files: one for the data source and one for the Database connection. To inform users, a one-time pop-up appeared when saving credentials. This pop-up has now been removed as the process has been changed for several versions.

The resizable dashboard now features a new template option that was previously exclusive to the fixed layout. In earlier versions, the resizable dashboard only included the File and Tools menus. However, based on user feedback, a new Template menu has been added. This menu allows users to create templates in both portrait and landscape modes, as well as upload and download current templates, similar to the fixed layout. Users can create and modify templates, and they have the option to apply them by using the "Use Template" checkbox during export.

When exporting from the resizable dashboard, the template is applied only if the user selects the checkbox and chooses PDF, DOCX, or HTML as the export format. Templates will not appear in Excel, CSV, or PowerPoint (PPTX) exports, which is consistent with the fixed layout behaviour. For example, if a template is applied and exported as a PDF, the customised template (with components like charts or text) will be reflected in the output. This update ensures a consistent and flexible export experience across both dashboard layouts.

The resizable dashboard, as its name implies, enables users to customise the components on a dashboard to any desired shape and size. Once a template is uploaded, it can be utilised during export, providing the same functionality and flexibility as the fixed layout dashboard.

Any changes made to a component, such as swapping an existing component for a new one, or adjusting the number of components by adding or removing them (which is only possible with a Resizable Dashboard), will result in those components not being displayed in the exported documents. If changes are made to a resizable dashboard after uploading the template, those changes will not appear in the exported template document until a new version of the template is generated and uploaded.

The Don't Refresh Data feature has been improved to work only within designer mode. Earlier, it affected documents and the home screen as well, which caused unexpected behavior. Now, when this option is selected, data will not load automatically when adding components or opening dashboards—users must click the Refresh button manually. This fix ensures the setting applies only at the dashboard level and does not interfere with other parts of the application.

The Date Filter has been enhanced to accurately display the correct date range for This Year, Last Year, and Next Year based on the chosen start month. Previously, the year range was sometimes inaccurate, particularly when selecting future months. Now, the filter adjusts correctly and shows the expected date range, resulting in more accurate and reliable date selection.

The Scorecard component now fully supports creating calculated series by applying arithmetic operations between existing data series. Users can combine multiple series, like adding two values together, and the calculated results display correctly in the scorecard. This update, included in a recent Hotfix, ensures smooth functionality and allows users to rearrange and view their series as needed.

The Highlight Rule feature has been improved to simplify the application of date-based conditions. Previously, for a date field to show up in the highlight rule’s date condition dropdown, users needed to enable both the Date Filter and Filter checkboxes in the Data Model Editor. This requirement was unnecessarily restrictive. With the new update, only the Date Filter checkbox needs to be checked. Once this is done, the date field will be readily available for use in highlight rules without any need for additional filter settings. This change streamlines the process and allows for more flexible use of date fields when setting up conditional formatting.

The latest release of the Sync Tool introduces support for creating and running jobs on multiple instance IDs using the same database. Previously, a bug allowed only one job to be created on Instance ID 1. This issue has been resolved in the recent hotfix, allowing jobs to sync correctly across different instances.

The instance-related functionality will not work with Ivanti Neurons for Patch Management (NPM). This feature is particularly useful for data sources like MI Core and NMDM (formerly known as MI Cloud).

This release addresses an issue that caused the Sync Tool job creation to fail due to the missing columns, isCustom and isCustomized. Previously, users had to manually add these columns as a workaround. With the latest release, this requirement has been removed, and job creation now functions correctly across all supported DataSource/Products.

Previously, when connecting to MI Cloud in the Source tab, users could only view up to 50 partition IDs after a successful test connection. This was problematic for clients with more than 50 partitions, as the additional ones were not visible, requiring manual entry if known.

With this enhancement, the limit has been increased to 500 partitions, making it easier for users to see and select all available partitions directly from the UI. Since it is an editable dropdown, users can enter any known partition or space ID directly instead of selecting from numerous options.

In the past, the Sync Tool would occasionally miss new records if they were added while a sync was in progress. This issue occurred because the tool used to fetch the data for future syncs from the Last Sync Operations success Date-Time for a particular table rather than the new records after the Max of last updated records Date-Timestamp, which caused it to overlook records created just before or during the Sync Operation.

This problem has now been resolved. The Sync Tool now utilises the lastModifiedDateTime (or the designated update field as it varies depending on the table) to identify the most recent updates and retrieve all records added after that point. As a result, all new records are now consistently captured during each sync.

Customers with large IT Service Management (ITSM) and IT Asset Management (ITAM) databases are advised to request backups of their cloud databases. Each customer is permitted to make up to two backup requests per year. This feature was introduced due to the considerable time required for an initial synchronization, as noted in the product documentation.

Once an Active Job is created in Neurons for ITSM/ITAM, data can be imported from a SQL Server backup. This method offers key benefits:

• Much faster than API syncs (minutes vs. days)

• Automatically includes all custom fields

• Tracks the latest update for incremental syncs

Earlier this import process failed but now it is resolved and works as expected.

For the import operation to proceed, the source database credentials must have the appropriate permissions to create and populate a table called TableAttributes, which contains the schema information for all tables. No other modifications will be made to the source database.