Cannot sort on dataprovider scopes.globals...

[udiluca]

Hello,

I have this warning all over the place in the server log.

Basically, we are using a value list in a table view, with a global variable as dataprovider. There's no sort done on this column, I eve locked the sorting capabilities with no effect.
This warning is showing as soon as the form is displayed, whatever the user action.

Any clue ?

Thanks

We are using Servoy 7.2

[jcompagner]

do you have some testcase where you see that then? You could make a case for that.
But somehow a sort is being tried on a globals variable

[rossent1327331687]

We see similar warnings in the server log as well in Servoy 7.3.1.
They happen when a TABLE_VIEW form includes a column/field which uses as dataprovider a calculation. No sorting is being performed in our case either. The warning log message is generated as soon as the form is displayed. We have set as default sort for that form another regular column/field but this has no effect on the warning log message.

[Providence1]

So has this warning only been resolved for 7.3.1 as per:

[fix] SVY-6185 Warning log message "Cannot sort on dataprovider..." appears in Server Log even when no sorting is being performed by our code or by the user

I'm on 6.1.6 (don't laugh) and i'm seeing the same thing:

TABLE_VIEW, several columns that have a dataprovider as a calc over a relation, the warning is displayed (a kajillion times, or is it cajillion?) as soon as the form is displayed or refreshed. The initialSort is a regular (non-calc'ed) number field in the same table as the forms datasource.

Even when you remove the initialSort on the form the warning still fires. Since this warning is being written out to the java console, performance is affected.

Will this warning be subdued server side in 6.1.6?

[jcompagner]

not sure what you mean with " Will this warning be subdued server side in 6.1.6" because this is a client message.

But the fix is only made in 7.x so if you don't want these errors you have to upgrade or don't use those relations in tableviews, or maybe tweak the log settings (like don't log any warning message)