Hi all,
we are having the following issues in Universal:
- where the data is not displaying properly.
- and Universal is changing the data.
See attachments
Anyone know what causes these issues?
Datatype is bigint
Solved
Universal 2022.2.4 not displaying data properly
- Apprentice
- 6 replies
Best answer by Mark Jongeling
Hi Zachery,
I asked a Universal GUI developer about this, and this sadly is a limitation of JavaScript and also browsers. JavaScript supports 16 digits as number whilst SQL Server can support up to 19 digits. This causes the last 3 digits to not show properly.
In the far distant future (soon™), this may be fixed but this is certainly not easy to be implemented.
Only workaround is to not show more than 16 digits, or to make it a text field and double check its input/value to be numeric. In our upcoming 2023.1 release, you'll be able to create an Input constraint on it that can check the value automatically.
This topic has been closed for comments
+23Hi
Can you confirm you are using the 2022.2.14 version of the Universal GUI as there is no 2022.2.4 version? Also the attachment image is not properly visible to me and most likely others too. Could you place the image inline inside your next reply? Thanks!
Have you tried the latest version of the Universal GUI? More on it here: https://community.thinkwisesoftware.com/product-updates?filters%5BproductArea%5D%5B0%5D=Universal%20GUI
Is [tag_option] a view or a table? In case it is a View, it should have a functioning Instead-of-trigger to process the entered data.
- Apprentice
- 6 replies
Hi
Yes, we are using the 2022.2.14. Sorry for the typo. [tag_option] is a table. Have you looked at the screen recording in the zip file?
Here’s the image.
+23Hi Zachery,
I asked a Universal GUI developer about this, and this sadly is a limitation of JavaScript and also browsers. JavaScript supports 16 digits as number whilst SQL Server can support up to 19 digits. This causes the last 3 digits to not show properly.
In the far distant future (soon™), this may be fixed but this is certainly not easy to be implemented.
Only workaround is to not show more than 16 digits, or to make it a text field and double check its input/value to be numeric. In our upcoming 2023.1 release, you'll be able to create an Input constraint on it that can check the value automatically.
+5Feel free to report a TCP ticket for this. In the meantime I would suggest you to convert the number to a varchar.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.