Key Enhancements

Administrators can now enable a setting that displays numeric properties with thousands separators throughout the platform. The setting is a checkbox labeled “Use 1000 Separator” under Administration > Preferences > World > General Settings, unchecked by default.

When enabled, Integer, Decimal, and Float values are displayed with grouping separators in both view and edit modes across Search grids, Modal Search grids, Relationship grids, Tree Grid View, Classic forms, Responsive forms, Redline Mode, and xClassification properties. Formatting follows the browser locale, so en-US style grouping (1,000,000) and de-DE style grouping (1.000.000) are both supported, along with fr-FR (1 000 000) and ja-JP conventions. Existing decimal separator behavior is preserved in all cases.

Users can type or paste numeric values with or without grouping separators, including values copied from external sources such as Excel, and the system parses them correctly regardless of the toggle state. Malformed separator input, such as consecutive or misplaced separators, is rejected with a validation error rather than silently accepted. Values are always stored and queried in neutral numeric format regardless of how they are displayed.

Administrators can now configure the default display state of individual accordions in Item Views, in addition to the existing Default Structure View setting. Each accordion can be independently set to Expanded, Collapsed, or Maximized through its Accordion Element Control configuration, using an Additional Data property on the control (for example, {"attributes": {"maximized": true}}, with collapsed or expanded as alternatives).

When an accordion’s default state is set to Maximized, the accordion expands over the form when the item opens, hiding the item’s properties while keeping the title bar and toolbar visible. Users can return to the default layout at any time using the Restore button. Multiple accordions can each have independently defined default states, and where more than one accordion is set to Maximized, they display in reverse configuration order. Accordion-level configuration takes precedence over the legacy Default Structure View setting when both apply to the same view.

The existing “Tabs Max” option under Default Structure View, previously equivalent to “Tabs On” and reserved for future use, now maximizes the relationship tabs over the form in the same way.

Advanced Search now displays the ItemType’s configured label instead of its internal name, making search results easier to read and interpret, particularly in environments with many custom ItemTypes or non-obvious internal naming conventions.

Advanced Search metadata now loads asynchronously instead of using synchronous requests that previously blocked the browser while waiting for a server response. Selecting an ItemType in the Advanced Search grid, and interacting with property or criteria rows, no longer freezes the interface. A loading indicator appears in the property grid while metadata is retrieved for the first condition added to a search.

Administrators can now configure a new event, OnFilterSelection, on any item property to control which items appear as type-ahead suggestions. An administrator selects OnFilterSelection in the Property Event dropdown and points it at a Method that returns a filter definition. From that point on, type-ahead suggestions for that property are limited to items matching the filter, consistently across Responsive forms, Classic forms, editable Relationship and Search grids, and the Add Related Item toolbar.

The filter Method receives the property name and the current item, including any unsaved edits made elsewhere on the same form, so filtering logic can depend on other field values the user has not yet saved. If the Method returns no result or encounters an error, the system falls back to showing unfiltered suggestions and surfaces an alert rather than failing silently.

This release also changes default type-ahead behavior for properties that use the older OnSearchDialog event. Previously, configuring OnSearchDialog on a property forced its type-ahead into a read-only state, requiring users to open a separate search dialog to select a value. Type-ahead fields are now editable by default regardless of OnSearchDialog configuration. The search dialog itself is unchanged and still runs OnSearchDialog handlers when opened explicitly. Customers who relied on the previous forced-dialog behavior for filtering should configure OnFilterSelection on the same property to restore equivalent filtering directly in the type-ahead.

The Where Used tab now includes a filter panel alongside the results tree, letting users scope results to specific reference paths before loading data. Previously, expanding any node in the Where Used tree queried every reference type at once, which could be slow and return more data than needed for items with many relationships.

Selecting a row in the tree populates the filter panel with one card per available reference path, each showing the ItemType icon, the ItemType’s plural label, and the specific reference path in parentheses, since a single ItemType can be reached through more than one kind of relationship.
Users can select any combination of paths and click Apply Filters to reload the tree scoped to those paths, or select none to see all results. Filter selections are scoped independently per tree node, so different rows can carry different filters without interfering with each other. A “Select All” option is available to quickly select or clear every card in the panel.

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 Services feature shipped with the SQL Server product. See the Reporting Services consolidation FAQ for more details.

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 a migration plan is in place for existing reports.

Target Resolution:

Aras has no plan to replace Reporting Services directly and will plan to end-of-life the integration feature in alignment with the end of support for SQL Server versions prior to SQL Server 2025. To address this, customers are recommended to adopt one of two solutions:

• Aras Reporting: starting with Aras Innovator Release 28, Aras has provided a platform component called Aras Reporting, which provides reporting capabilities within configurable dashboards.
• Microsoft Power BI: as an alternative to Aras Innovator managed reports, customers can migrate reports from SSRS to Power BI using a direct SQL connection.

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