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
2960 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Error in Grid using Process analytics as Data
Issam Dabaie
Certified Senior Developer
over 8 years ago
Hello,
I have a grid using a Process Analytics Report as the source of data. I get the following message:
Expression Evaluation error in rule 'Rule Name' at function a!gridField [line 45] Type Validation Null.
I'm not sure what is causing this issue, since looking at the report the data looks perfectly normal.
Any thoughts? Your help is appreciated.
OriginalPostID-266095
Discussion posts and replies are publicly visible
0
rudrakshakammarig1
over 8 years ago
Hi issamd,
I think the column which you want to show on grid field might be returning null value. Please handle null exception at fieldData attiribute.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 8 years ago
I usually get that error when the parameter I'm using in my grid is spelled incorrectly. Double check the spelling of any key-value pairings you may have in your gridField
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aloks0189
Certified Lead Developer
over 8 years ago
@issamd850 I agree with @rudrakshakammarig , @reginaldm377 also try using index() rather than data.key because if you use that, and if there is no data for the key, you can expect the same error.
So do the following
1) Cross check with the spelling
2) use index() wherever possible rather than datasubset.key as
index(local!datasubset, "c0", {})
3) Cross check whether the field value which we are trying to retrieve(like c0, c1, c2, ...), is getting return from QueryProcess or not
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
kumara0002
A Score Level 1
over 8 years ago
Always use index() when you need to traverse through multiple .(dots)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Issam Dabaie
Certified Senior Developer
over 8 years ago
Hello,
Thank you all for your input.
All the fields are set using the index function, and everything is spelled correctly.
Looking at the process report itself it is also populating as it should with no missing data.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Issam Dabaie
Certified Senior Developer
over 8 years ago
Hello all,
After investigating, and checking the log files which returned the same vague error message, I found the issue was there was a link field using an expression that was missing pertinent record types to be returned.
Thanks again for your help.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Shyam Bommakanti
Certified Lead Developer
over 8 years ago
Debug with limited data and limited columns. Filter the portal report to have only 1 row. If the issue persists, debug by having only 1 column in SAIL and keep adding columns to isolate the data/column that is causing this issue.
Also, check if are using the hidden columns from portal report. To debug, this run the query analytics separately to verify you are using the correct c<number> column in SAIL.
P.S. I see your issue is resolved. Kudos to the feature the checks for updates before posting. I composed the comment before your update so, this is just other debug options for future reference.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel