Cannot read properties of undefined (reading 'indexOf')

[JasonJordan00]

I have an editing-mode Survey123 webform embedded in a dashboard that filters off of a category selector. About 1 in every 5 selections of a feature from the category selector the form fails to load:

The form seems to pop up for a split second before moving to the error.

I don't think it has anything to do with the attributes in the field because I can reload the same feature over and over and it will error out eventually. However reselecting the record will generally prompt it to load correctly. Its coming from a feature layer hosted in an SDE. Not seeing any error in Chrome developer tools. Anything I can try?

[TylerBragg2]

To follow up on this:

I reviewed what was happening in my dashboard when selecting a feature from the "List" widget using the Google Chrome Developer Tools and I'll put some screenshots below.  It begins all the queries of the feature service necessary to display the data in the embedded survey.  The images below are of the query performed immediately before the error message.  It runs through several queries of the feature service successfully, then it looks like it's querying the related table (FeatureServer/1) where the "ParentGuid = 'undefined'.  It then receives an error for invalid query parameters.  I'm not sure why or how to resolve this.  Maybe this will help shed some light on what's happening.

[TylerBragg2]

Posting another update to this - I have resolved my issue, though I'm not sure if it's applicable to the OP's issue nor would be considered a "solution" to this thread.  This is specifically dealing with the feature service with a related table, as some other users have commented above. 

To resolve my problem, I went to the item details page of the feature layer that contains the related table (the one to which my survey is connected).  I created a view layer from this original layer.  When creating the view layer, you'll have to option to choose which feature layers within the service are included in the view layer.  I "unchecked" the related table so as NOT to include it in the view layer, then proceeded with finalizing the view layer.  Once this was created, I opened the survey that is embedded in my dashboard in Survey123 Connect, opened the xls form, and modified the "submission_url" on the "settings" tab to point to the item ID of my new view layer (that doesn't include the related table).  Once I re-published this, the problem seems to be resolved.  I'm no longer receiving any errors and, when checking the activity using the Chrome Developer Tools, there are no further queries directed towards the related table.

This may not be a viable workaround for everyone, but it seems to have solved the issue with the erroneous query of the related table and is not producing errors.  I've also tested submission of the form and it seems to be working as expected.  Hope this helps someone else having this issue.