MNI parameters

RE: MNI parameters

karthip0001 — Sun, 01 Sep 2019 22:43:34 GMT

Stewart, Not always. Just today I am running into this issue where any time I do a concatenation of a field's value on a record instance from the CDT array, for some reason it uses the entire array!

"Record No. " & pv!cdtarray.record_no stores "Record No. 1, 2" into the output variable assuming the array has just 2 records. When I removed the concatenation, it displayed correctly Record No.1 and Record No.2 in the output. I thought this was bizarre!

And that's exactly why I am here now looking for an alternative. Going to try using instance index.

We are on 18.2.

RE: MNI parameters

Brad J Horstkotte — Fri, 12 Apr 2019 18:19:47 GMT

Interesting, I didn't try that - or maybe I did but that was before I fixed my type casting problem, so the error message led me down another path.

RE: MNI parameters

Mike Schmitt — Fri, 12 Apr 2019 15:55:21 GMT

Yes - and (frustratingly) exactly how this works is not very well documented. Out of basic paranoia, I usually manually index the array being passed in anyway - somehow it also "knows" when this is done and passes in the manually-indexed entry, fortunately.

RE: MNI parameters

Stewart Burchell — Fri, 12 Apr 2019 14:11:39 GMT

Interestingly when you call a sub-process as an MNI Appian seems to "know" to pass the relevant item from the array into the sub-process without you having to explicitly reference the item using tp!instanceIndex.

RE: MNI parameters

Brad J Horstkotte — Thu, 11 Apr 2019 14:41:37 GMT

Thanks very much for the speedy reply April, I'll give that a try (so far so good, but have a cast problem now - but at least it's the NEXT problem 🙂)

RE: MNI parameters

April Schuppel — Thu, 11 Apr 2019 14:30:10 GMT

Hi Brad,

You can use [tp!instanceIndex]

Example:

PV is myList

Input would be myList[tp!instanceIndex]