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
6 replies
Subscribers
6 subscribers
Views
2527 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
I'm having an issue with Appian's automatic order indexing when a CDT co
Chris
over 9 years ago
I'm having an issue with Appian's automatic order indexing when a CDT contains 2 child CDT's, both in a one-to-many relationship. After the first child was added ("CDT_GateReview_Comments" in the attachment), indexing worked great without any input from my CDT. When a second child was added ("CDT_GateReview_Viewers"), I began receiving the error "null index column for collection: CDTGateReviewsDT1766.viewers" - when there certainly was data present. After some research, I turned off indexing in the CDT by adding only "(indexed=false)" to line 222 (on the @OneToMany annotation), for the second child. At this time, I stopped receiving errors and all everything works, just without an order index created automatically for child #2, where it still works for child #1.
Are there any known issues for this indexing when multiple child CDTs are involved - would we have to manage indexing manually in these cases? I do not need indexing in this scenario, ...
CDT_GateReviews.xsd
OriginalPostID-164945
OriginalPostID-164945
Discussion posts and replies are publicly visible
Parents
0
kumaraveln
over 9 years ago
Hi steward .. When are you seeing this error 'null index column for collection' exactly ? during inserting / updating into the table or when querying the values. There is a relative post without a solution
forum.appian.com/.../e-116958
One a quick look, comparing your xsd with ours, we have always defined (indexed=false) in all the oneToMany relation and there were no issue in insert / update / lookup even when there were more than 1 nested CDTs of type multiple. Please give more information on your issue
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
kumaraveln
over 9 years ago
Hi steward .. When are you seeing this error 'null index column for collection' exactly ? during inserting / updating into the table or when querying the values. There is a relative post without a solution
forum.appian.com/.../e-116958
One a quick look, comparing your xsd with ours, we have always defined (indexed=false) in all the oneToMany relation and there were no issue in insert / update / lookup even when there were more than 1 nested CDTs of type multiple. Please give more information on your issue
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data