https://community.appian.com/discussions/f/process/6884/hi-i-have-a-reviewdocuments-cdt-which-contains-two-multi-value-child-cdtsHi I have a ReviewDocuments CDT which contains two multi value child CDTs. I have a documents array containing 2 documents and a CDT FieldworkAnalyticalReview array with 3 sets of details. Each FieldworkAnalyticalReview needs to be associated with eachen-USTelligent Community 12https://community.appian.com/thread/27509?ContentTypeID=1Tue, 09 Feb 2016 15:06:29 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cd747f88-ad3d-44e0-84c2-2dbd9faffc47suemHi all, I’m afraid we’ve had to re-work our output CDT to match others in the system so it’s been simplified to the following:<br />ReviewDocument :-<br /> <br />The two input CDTs, Documents and Reviews:-<br /> <br />For each combination of Review and Document we need to write a ReviewDocument. <br />For example if we have 3 rows in Review {“A”,”B”,”C”} and two in Document {1,2} then the output ReviewDocument will contain 6 rows ie A1, A2, B1, B2, C1, C2 where ReviewDocument .farId = gtFieldworkAnalyticalReview.id and ReviewDocument .assignmentDocumentId = gtassignmentDocument.appianDocumentID <br /><br />So far we have had little success in nesting the functions and have yet to discover the correct combination which seem endless -<br />single rule in a script task output, or via the script task inputs or possible using an MNI?<br />thanks<div style="clear:both;"></div>https://community.appian.com/thread/27431?ContentTypeID=1Mon, 08 Feb 2016 14:00:46 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cc7b6b9b-87b6-4a1b-bd39-f0595ab53a2dsuemHi thanks sonalk, Phil. I&#39;ll try out the apply merge approach as it looks like it will do exactly what we want. Thank you<div style="clear:both;"></div>https://community.appian.com/thread/27429?ContentTypeID=1Mon, 08 Feb 2016 13:27:13 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:5704ac89-74cf-4258-b32f-91b22054705ePhilBBit of a complex one this, but the below pretty much does what you want. Sue - I&#39;ll contact you directly with a more complete solution.<br /><br />load(<br /> local!documents: {&quot;A&quot;, &quot;B&quot;},<br /> local!reviews: {1, 2, 3},<br /> local!reviewArray: reduce(<br /> fn!append,<br /> {},<br /> apply(<br /> fn!insert(<br /> {},<br /> local!reviews,<br /> _<br /> ),<br /> enumerate(<br /> length(<br /> local!documents<br /> )<br /> ) + 1<br /> )<br /> ),<br /> local!documentArray: reduce(<br /> fn!append,<br /> {},<br /> apply(<br /> fn!insert(<br /> {},<br /> local!documents,<br /> _<br /> ),<br /> enumerate(<br /> length(<br /> local!reviews<br /> )<br /> ) + 1<br /> )<br /> ),<br /> apply(<br /> fn!concat(<br /> _,<br /> _<br /> ),<br /> merge(<br /> local!reviewArray,<br /> local!documentArray<br /> )<br /> )<br />)<div style="clear:both;"></div>https://community.appian.com/thread/27416?ContentTypeID=1Mon, 08 Feb 2016 04:17:52 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:755b1703-dd27-45ee-9d94-81f5a8238501sonalkHi Suem,<br />Not sure if you have already gone through the below related forum posts link :<br /><a href="/search?q=OriginalPostID-145331">forum.appian.com/.../e-145331</a><br /><a href="/search?q=OriginalPostID-190101">forum.appian.com/.../e-190101</a><br /><a href="/search?q=OriginalPostID-153616">forum.appian.com/.../e-153616</a><br />Please check if it helps.<div style="clear:both;"></div>https://community.appian.com/thread/27415?ContentTypeID=1Sun, 07 Feb 2016 13:21:44 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:bdecb5e5-6847-4c38-8677-84af305e9f4asuemWe&#39;re having trouble with the syntax required to populate the cdt for the join table. We&#39;ve tried lots of different combinations but haven&#39;t hit the right combination of functions yet. Any ideas on that please.<div style="clear:both;"></div>https://community.appian.com/thread/27400?ContentTypeID=1Fri, 05 Feb 2016 23:09:17 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:aef05946-e445-4d10-be74-9bec43a3b2afjackm829Use a join table between FieldWorkAnalyticalReview and Documents. This may be called FieldWorkAnalyticalReview_Document. There will be at least 3 fields - add other metadata fields as you like. The ID (primary key) of this type, the foreign key ID of the Document, and the foreign key ID of FieldWorkAnalyticalReview. I would probably recommend not nesting the types - as in the screenshot. Your queries may return more data than you need. You could just soft-link by ID.<div style="clear:both;"></div>