You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Andreas Neumann (@andreasneumann)
Original Redmine Issue: 7924
Affected QGIS version: master
Redmine category:qgis_server
Assignee: Marco Hugentobler
I sometimes use boolean data types represented with checkboxes. In QWC (QGIS web client) I want to display them with yes/no instead of "t" and "f". I need to therefore detect these boolean values.
In the output of the GetProjectSettings reponse I get the type as QString. I cannot use the edit type, because in this setup the edit type is set to "Hidden". I want to hide them in QGIS desktop but show them in QGIS Web Client.
So, is there a chance that the boolean values (set to boolean in Postgis) would be reported as boolean and not as a QString?
example output of GetProjectSettings:
in the above example all of the "Betroffen_xxx" attributes are actually of type boolean, but are reported as "QString".
The text was updated successfully, but these errors were encountered:
Author Name: Andreas Neumann (@andreasneumann)
Original Redmine Issue: 7924
Affected QGIS version: master
Redmine category:qgis_server
Assignee: Marco Hugentobler
I sometimes use boolean data types represented with checkboxes. In QWC (QGIS web client) I want to display them with yes/no instead of "t" and "f". I need to therefore detect these boolean values.
In the output of the GetProjectSettings reponse I get the type as QString. I cannot use the edit type, because in this setup the edit type is set to "Hidden". I want to hide them in QGIS desktop but show them in QGIS Web Client.
So, is there a chance that the boolean values (set to boolean in Postgis) would be reported as boolean and not as a QString?
example output of GetProjectSettings:
in the above example all of the "Betroffen_xxx" attributes are actually of type boolean, but are reported as "QString".
The text was updated successfully, but these errors were encountered: