Skip to main content
Question

Universal 2026.3.10 still not displaying data properly

  • Nov 19, 2026 3:32 PM UTC
  • 0 replies
  • 17 views

Forum|alt.badge.img+1

Hi everyone,

We are running into a major blocker while preparing to upgrade to Thinkwise 2026.3 and wanted to check how others are handling this or if there is any update on a native fix.

About 4 years ago, I reported an issue where 19-digit numbers do not display properly in the Universal GUI:https://community.thinkwisesoftware.com/questions-conversations-78/universal-2022-2-4-not-displaying-data-properly-3510

In the Windows GUI, 19-digit values work without any issues. However, in Universal, the values are still not displayed accurately—and this remains unresolved in version 2026.3. Since 2026.3 is fully Universal, this is currently preventing us from upgrading.

We reached out to TCP for an update and were given the following workaround:

  • Keep the original 19-digit column as-is.

  • Add a separate varchar column as an editable expression field so all 19 digits display as text.

  • Validate that the input is numeric and write the value back to the original column whenever a user edits the field.

While this might work for a single isolated field, we use this domain/field in multiple places across our application. Implementing an extra expression column, write-back logic, and validation everywhere this domain is referenced would require too much rework, add significant maintenance overhead, and introduce unnecessary risk to data integrity.

Questions for the community and Thinkwise:

  1. Has anyone else encountered this 19-digit limitation in Universal across multiple tables/screens, and did you find a cleaner, more scalable way to handle it?

  2. Is there any update on whether native support for 19-digit values in Universal is on the roadmap?

Any insights or suggestions would be greatly appreciated!