I'm having an issue with Appian's automatic order indexing when a CDT co

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
  • Hi kumaraveln, I am receiving that error when data is inserted to the child table, if I do not include (indexed=false). I have since added (indexed=false) to both child CDTs and everything is working fine, I was just curious if it is possible or not to auto-index when there are multiple child CDTs - in my experience it will only work for one.
Reply
  • Hi kumaraveln, I am receiving that error when data is inserted to the child table, if I do not include (indexed=false). I have since added (indexed=false) to both child CDTs and everything is working fine, I was just curious if it is possible or not to auto-index when there are multiple child CDTs - in my experience it will only work for one.
Children
No Data