Release 39

Tree Grid View now supports selecting multiple rows at the same time, allowing users to work with sets of related items more efficiently. Instead of selecting and acting on one row at a time, users can apply supported actions across multiple selected rows in a single step. This improves productivity in scenarios where users need to review, organize, or manage multiple items within the same tree-based view.

Several standard dialogs can now be resized, and selected dialogs can also be maximized. This improvement gives users more space to view dialog content when working with long text, larger forms, or more complex selections. By reducing the limitations of fixed-size windows, the updated dialog experience makes it easier to review information, enter data, and complete tasks without unnecessary scrolling or repeated navigation.

Favorites now display the correct label when viewed after switching to another language. Previously, favorites created in one language might not display meaningful labels when accessed in another, making them harder to recognize and use. This enhancement improves the experience for multilingual teams by making saved searches and item favorites easier to identify, understand, and reuse across language settings.

Administrators can now configure a default descending sort order for supported grid columns. This gives organizations more control over how data is presented when users open search or relationship grids, especially in cases where the most recent or highest-value records are the most important to see first. By supporting descending sort order as part of the default configuration, the platform can better match common business expectations for how data should be displayed.

History entries are now easier to read by showing more user-friendly labels and keyed names instead of relying primarily on internal names, IDs, or raw values. This helps users better understand what changed when reviewing property updates, item changes, life cycle transitions, and list-based values. The result is a more readable and meaningful history view that supports auditing, troubleshooting, and general review of item activity.

Saved grid layouts now retain user-defined column sorting, including the selected columns, sort direction, and sort priority. When users restore a saved grid layout, the sorting is restored with it, so the data appears in the same order it was originally configured. This makes saved layouts more useful and consistent by preserving not just the visible columns, but also the way users want the information organized.

Favorites can now be edited after they are created, making it easier to maintain saved searches and item favorites over time. Users can now open edit dialogs from the title bar or navigation panel to update favorite details instead of removing and recreating them. For search favorites, users can update the label, sharing settings, and Quick Access pin status. For item favorites, users can update the label, with new item favorites defaulting the label from the item keyed name. Favorites can also be removed from the same workflow. Search criteria and saved layout settings for search favorites remain fixed after creation, and grid-based favorite actions for items now support single selection only to ensure changes are applied intentionally.

Aras Innovator now supports configurable labels for accordions in Item Views, helping users navigate complex layouts more easily. In views with many accordions and tabs, users can now see a clear group label for each accordion instead of relying only on tab names to understand each section.
The label remains visible whether the accordion is expanded or collapsed, making it easier to locate the right area quickly and understand how tabs are grouped. This improvement enhances readability in dense Item Views without changing existing accordion behavior such as expand/collapse, tab switching, scrolling, or layout interaction.

Administrators can now configure static colors for relationship tabs within accordions. This makes it easier for users to visually distinguish important or related tabs in item views with many relationship sections. The configured color is applied consistently to the tab label area, helping users scan large item views more quickly and navigate to the right section with less effort.

Relationship grids now provide a visual indication for required properties during grid-based editing. This gives users earlier guidance when creating or updating relationship rows, similar to the required-field indicators already available on forms. By showing required information in context, this enhancement helps users complete data entry more accurately and reduces save errors caused by missing required values.

Users can now save and restore grid layouts for relationship grids. Saved layouts can preserve settings such as visible columns, column order, column width, frozen columns, and the Redline Mode state.
This allows users to quickly return to a preferred relationship grid layout instead of manually adjusting the grid each time. Relationship grid layouts can also be saved with favorite relationship grid searches when the current layout is included with the favorite.

Performance and scalability have been improved for environments with large and complex xClassification models. These enhancements enable more reliable handling of large imports and items with a high number of xProperties, reducing query limitations and supporting more consistent system behavior at scale. Customers can now work with more flexible and data-rich classification structures with greater confidence.

As part of their continued improvements of the offerings, Microsoft has made the decision to consolidate its reporting functionality with Power BI. This means that Microsoft SQL Server will no longer have a Microsoft SQL Server Reporting Service feature shipped with the SQL Server product. Please see the following link for more details:

https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-consolidation-faq?view=sql-server-ver17

Affected Version:
Aras Innovator Release 39 and higher

Workaround:
Customers running SQL Server versions older than Microsoft SQL Server 2025 are not affected by this change. Customers using Microsoft SQL Server Reporting Services in Aras Innovator today are recommended to not upgrade to Microsoft SQL Server 2025 or higher until you have a migration plan in place for your existing reports.

Target Resolution:
Aras has no plan to replace Reporting Services directly but will plan to EOL the integration feature with the EOL of supported SQL Server versions prior to MS SQL 2025. To address the issue, it is recommended that customers adopt 1 of 2 solutions:

• Aras Reporting - Starting with Aras Innovator Release 28, Aras has provided a new platform component called Aras Reporting, which provides convenient reporting capabilities within configurable dashboards.
• Microsoft Power BI – Microsoft is consolidating their functionality inside Power BI. As an alternative to Aras Innovator managed reports, the customer could migrate reports from SSRS to Power BI using a direct SQL connection.

Please note that Aras Reporting and Power BI are not direct replacements for SSRS and no upgrade path is provided for your reports by Aras or Microsoft. Customers should plan to migrate their SSR reports of upgrading to Microsoft SQL Server 2025 or higher. Migration of reports is not included in Aras Upgrade Services, and so customers will need to plan internally how to address this change if affected.

Aras Innovator has been updated to run on .NET 10. This supports platform modernization and long-term support requirements while maintaining existing product functionality. Transitioning the enterprise system from .NET 8 to .NET 10 is a strategic move to ensure your PLM infrastructure remains secure, supported, and high-performing. Since official support for .NET 8 is scheduled to end in November 2026, this upgrade is essential to maintain industry compliance and protect sensitive product data from emerging security threats. By adopting .NET 10, the environment gains a stable Long-Term Support (LTS) foundation that remains fully protected and updated through late 2028. Learn more

Before upgrading to Innovator 39, customers should review their custom code for SQL queries that rely on locale-sensitive date or number formatting. These SQL parameters need to be in neutral date format, such as “2026-03-13T14:30:00". No action is required for standard Aras Innovator product usage.