Page 1 of 1

View Foundset Datatypes

PostPosted: Wed Oct 21, 2020 9:39 am
by gk1441607435

I tried to create a View Foundset. This works fine with date and number fields. But as soons as I use Text or UUID Fields I get errors like:

ERROR com.servoy.j2db.util.Debug - Column type for column 'fieldname' defined in view datasource 'view:fieldname' does not match the one provided in the query.

This happens for example, when I have columns named 'x' both of Type 'Text' in a 'sourcetable'- and a view foundset definition.
When I take a look into the dbi-file of a sourcetable for the query, I see that a textfield has a datatype of -9. I guess that is the java.sql.Type of NVARCHAR;
But in the dbi-file of the view foundset the datatype is 12. This looks like the java.sql.Type of VARCHAR;
For the type UUID(Text(36)), the datatype is in both files 12. That looks ok. But in the (source)dbi file the "flags" property is set to 5, whereas in the view foundset dbi file the "flags" propterty is 4.
This differences are probably the reason for the error.

This looks to me like a bug. But it has been demonstrated in a the Webinar "2019.06 Launch Part 1 - FoundSet Optimization". (
There it worked fine with TEXT-fields. So why shouldn't it work now?

Are there any options in developer for dbi creation or is it still a bug in a newer version of servoy?



Servoy 2020.06
SQL-Server 2012

Re: View Foundset Datatypes

PostPosted: Wed Mar 03, 2021 10:11 pm
by pitc
Hi Gregor,
did you get an answer for this.
I am getting the same error.
Servoy 2020.12.3263

Re: View Foundset Datatypes

PostPosted: Mon Mar 08, 2021 10:43 pm
by pitc
Update: I added a Servoy Jira defect:
There I comment on the workaround editing .tbl file

Re: View Foundset Datatypes

PostPosted: Wed Mar 17, 2021 2:41 pm
by gk1441607435
Hi Tom
Sorry for my late reply. I didn't expected an answer to this anymore and the the view foundset is just a nice to have in our project at the moment.
Anyway, thanks for creating a case and getting a 'solution' for this.

For others: workaround and case from Tom ist here:
See Tom's comment