Run-time error '381': Invalid property array index - when adding a transaction code to the query criteria tab

When adding a transaction code as Criteria to a query, such as a transaction or account query (or otherwise) the error Run-time error '381': Invalid property array index may occur.

This may occur when a table for the transaction code contains more than 32,000 entries.
We are currently evaluating this issue and will update this article when we have more information.

Alternatively, inactivate or cleanup the extra table entries to reduce the number to 32,000 or less.

Steps to Duplicate

1. General Ledger > Query > New > Transaction Query 
2. Criteria > Expand Account distribution > expand Transaction codes
3. Attempt to double click on [Name of Transaction Code] Description
4. Receive Run-time error '381': Invalid property array index

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.