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
4 replies
Subscribers
11 subscribers
Views
2719 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Data and Records
Dot operator not working for nested CDT in Record Grid View configuration
vbhardwaj
Certified Senior Developer
over 7 years ago
Hi,
Have a service based record for which CDT has two level nesting. While configuring Grid View in 16.2, it gives the following Error :
The Requested Record Type Is Not Available
Expression evaluation error : A grid layout column [label=“Vendor”] has an invalid value for “component”. The component in row 1 encountered the following error: Expression evaluation error : Could not find variable 'rf!POHeader' (APNX-1-4198-000)
Expression which gives error --> rf!POHeader.vendor.vendorName
While using index() function it does not give me the error.
Using index() function --> index(index(rf!POHeader,"vendor",{}),"vendorName",null)
Dot operator should also work here as it works at other places like Record Title etc.
OriginalPostID-230592
Discussion posts and replies are publicly visible
0
reginaldm377
over 7 years ago
Could you show the portion of the query that is suppose to retrieve data for this column?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rishub
over 7 years ago
This error comes when the CDT is empty. When CDT is empty, it does not get the field names so DOT does fail in that. Using index to fetch values from fields of CDT is the best way to handle these errors.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vbhardwaj
Certified Senior Developer
over 7 years ago
Thanks all for your replies. It gives error only when field referenced using DOT operator is not coming from Webservice. Hence, index() function is a better choice.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
No problem and thanks for the comments as well @rishub & @vikrantb. It's nice to know about these situations through others experience.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel