Okay good to know, thanks for the help. It's still quite inconvenient (especially when using such an UI), but at least less time consuming!
Stefan Op donderdag 25 juli 2019 16:07:15 UTC+2 schreef Irene Polikoff: > > ... > Basically, if you set sh:datatype xsd:integer constraint before you enter > min/max values and save it, then min/max values constraints will be saved > as integers. > > But if you add the integer constraint after entering min/max, then it > would be saved as a string. The same happens if you enter both of them in a > single edit transaction since the system does not know yet that it must be > a digit. > > So, in the future, enter the integer constraint first, save it. Then you > can enter values constraints and they will be integers. > > -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/5814194a-54f3-495e-afbd-ca7cb4a16cd8%40googlegroups.com.
