Aras Innovator Platform

Appendix A: Custom Server-Side Code and SQL Date Formatting

Before upgrading, customers should review their custom code for SQL queries that rely on locale-sensitive date or number formatting.

Warning
This applies to SaaS deployments that contain custom server-side code where a localized date is passed directly to SQL Server as part of a SQL condition, instead of being passed as a SqlParameter object. No action is required for standard Aras Innovator product usage.

Aras Innovator 40 runs on .NET 10, hosted on Ubuntu 24.04. The ICU 74 globalization library shipped with Ubuntu 24.04 introduced a change in certain locales where a Narrow No-Break Space (U+202F) is used instead of a standard space before the AM/PM designator in formatted date strings. This can cause SQL Server to throw an exception when it attempts to parse a localized date string passed from the server.

Customers with custom server-side code that passes a localized date string directly to SQL Server as part of a SQL condition. For example:

SELECT login_name
FROM innovator.[USER]
WHERE created_on > '5/14/2026 2:48 PM'

SQL parameters must be in a locale-neutral date format, such as 2026-03-13T14:30:00. Use typed SqlParameter objects or culture-neutral format specifiers (for example, “s”) at all storage and SQL boundaries. Do not pass locale-sensitive date strings directly to SQL Server.

SQL Server may throw an exception because it cannot parse the localized date format passed from Ubuntu 24.

Any custom server-side code that constructs SQL queries using formatted date strings will return errors.

For further technical detail, refer to Cross-Platform Date/Time Formatting Normalization section of the Aras IOM SDK 15.1.2 Release Notes.