Indexing an array of records

stevenh6272 said:

However, this syntax does not work within the process model:

What do you mean? What do you observe?

Yes, sorry, I forgot to post the error message.  I need to regenerate the error and I will post the message in a bit.

Thanks.

Here's the error

An error occurred while evaluating expression: myRec:pv!myRecords[pv!recordIndex] (Expression evaluation error: PE My RecType must be indexed by its corresponding record type fields or relationships) (Data Outputs)

Can you please share screenshot of what stored in the pv

Bracket notation on a record array is reserved for field/relationship indexing, not integer position.Bracket notation on a record array is reserved for field/relationship indexing, not integer position.

Use index(pv!myRecords, pv!recordIndex, null) instead.

pv!myRecords[pv!recordIndex] works, if the PV is a list.

is the PV actually set to Array/Multiple type?

I did and received the same error.

Can you share your code snippet here?

Here is the exact line in the script task:

pv!performanceRecords[pv!recordIndex]

Here is the error:

Here is the screen shot of the data type

Here's the exact line using index (without a default)

index(pv!performanceRecords, pv!recordIndex)

Here's the error:

Now, you had mentioned using index with a default of null.  When I do this, it assigns null to the output variable (which of course causes downstream failures because a record is expected).

index(pv!performanceRecords, pv!recordIndex, null)

But expression rules can do both of these things without any problem. 

Here is the exact line in the script task:

pv!performanceRecords[pv!recordIndex]

Here is the error:

Here is the screen shot of the data type

Here's the exact line using index (without a default)

index(pv!performanceRecords, pv!recordIndex)

Here's the error:

Now, you had mentioned using index with a default of null.  When I do this, it assigns null to the output variable (which of course causes downstream failures because a record is expected).

index(pv!performanceRecords, pv!recordIndex, null)

But expression rules can do both of these things without any problem. 

What happens if you replace "pv!recordIndex" in your test code here with the literal value of "1"?  e.g. index(pv!record, 1, null())

Because I suspect this might be messing you up:

recordIndex is Text, not Integer. Record arrays must be indexed by an integer.
Change recordIndex to Number (Integer), or use index(pv!performanceRecords, tointeger(pv!recordIndex), null).

e.g. 

Aha!  I had not noticed the data type issue.  That would explain the matter.

The expression rule does accept an integer and Appian automatically converts the Text string to a number.

Such a simple mistake.... so much time lost.

Thank you!

Ran just fine using the [] indexing with an actual Numeric indexer.

Thanks all.

stevenh6272 said:

Such a simple mistake.... so much time lost.

Been there, hah.