Morning all, Has anyone found a 'nice' way round this issue o

Morning all,

Has anyone found a 'nice' way round this issue on a paging grid in Appian 7.8:

The dataset is expression backed via a webservice and often contains data that has a mix of 1 type (e.g. Boolean) and nulls.

When attempting to sort on the field an error is generated:

"The sort field must be a consistent type. Found two different types: 26 and 3, for sort expression <name>"
Type 26 = Boolean
Type 3 = Null.

Formatting the data in the a!textGridColumn has no effect as the sort is performed using the raw data from the expression, and we would like to avoid having to convert everything to text in the webservice and then back to the required dataType

Thanks in advance,

Gareth

OriginalPostID-157072

OriginalPostID-157072

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    Hi Gareth, so your data is returning the word "Null" or at least an empty string if it's saying type 3. If your webservice returned an actual null value then the paging grid would be able to handle the sorting.
    So the issue is with your data, somewhere it needs correctly type matching before Appian should be asked to put it in a paging grid. A boolean type with a string value obviously makes no sense..... nor does having a null boolean but that's a whole different topic!
Reply
  • 0
    Certified Lead Developer
    Hi Gareth, so your data is returning the word "Null" or at least an empty string if it's saying type 3. If your webservice returned an actual null value then the paging grid would be able to handle the sorting.
    So the issue is with your data, somewhere it needs correctly type matching before Appian should be asked to put it in a paging grid. A boolean type with a string value obviously makes no sense..... nor does having a null boolean but that's a whole different topic!
Children
No Data