Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
7 replies
Subscribers
7 subscribers
Views
2722 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Morning all, Has anyone found a 'nice' way round this issue o
garethm
over 8 years ago
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
garethm
over 8 years ago
Thanks Tim - Every test I have run on the data is returning true null values - except when used in the dataset, when the nulls are being returned as type 3 (text).
I suspect the reason for this is that the data is not explicitly typed - the value array is built from jsontodictionary() and that the function is assigning all nulls a type of 3 - I have tested this with a json string with a mix boolean, num(int), num(dec), date dateTime and each element with a value is getting correctly typed, whereas every null is assigned a type 3 no matter the datatype the column has been assigned.
As the json is dynamic and can't be typed, pending a fix to the rule, it looks as though I will have to resort to the backup of sending all values through as quoted text and then convert it in Appian.
Thanks for your help!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
garethm
over 8 years ago
Thanks Tim - Every test I have run on the data is returning true null values - except when used in the dataset, when the nulls are being returned as type 3 (text).
I suspect the reason for this is that the data is not explicitly typed - the value array is built from jsontodictionary() and that the function is assigning all nulls a type of 3 - I have tested this with a json string with a mix boolean, num(int), num(dec), date dateTime and each element with a value is getting correctly typed, whereas every null is assigned a type 3 no matter the datatype the column has been assigned.
As the json is dynamic and can't be typed, pending a fix to the rule, it looks as though I will have to resort to the backup of sending all values through as quoted text and then convert it in Appian.
Thanks for your help!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data