Invalid cannot index property of type text into type NSARequest

RE: Invalid cannot index property of type text into type NSARequest

jerrys790 — Thu, 27 Sep 2018 14:02:12 GMT

When making any changes to the CDT and Data store. Make the changes first in the database, then download the XSD file for that CDT make the changes in the XSD then upload the XSD file. This will prevent the issue of having ^2 as another version.

Regards,
Jerry

RE: Invalid cannot index property of type text into type NSARequest

Dastagiri Dudekula — Thu, 27 Sep 2018 06:04:39 GMT

Try to remap the cdt datatype in the process variables. Then also remap the cdt datatype in the activity class variable. It seems to be the latest change was not reflected in either of the variables.

RE: Invalid cannot index property of type text into type NSARequest

vishnuv — Thu, 27 Sep 2018 03:11:07 GMT

Hi,
1.Ideally, it appears the related CDT might not be updated. Hope impact analysis is done or may be you can remap the CDT at the reference artifact where is being used.
2. Sometimes, using dot throws an error while the value is NULL. I would suggest to use index() to overcome the same.
3. Is your CDT is multiple ? If so use cast in apply() function.

Thanks.

RE: Invalid cannot index property of type text into type NSARequest

Bryan Graney — Wed, 26 Sep 2018 20:05:06 GMT

anushas0002 Can you please confirm the following:

1) The datastore that references the CDT does in fact Verify when you Save and Publish it.
2) That the PM where you received that error references the latest version of the CDT that you changed (and hence the latest field name of that CDT). This means you shouldn't see a ^ followed by a version number (e.g., ^2) after the CDT name
3) And try indexing into that field to null handle, i.e., index(ac!nsaRequest, "officialName", {}) to see if that resolves the issue