Latest Contributions by 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.   ... View more

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.     ... View more

@JamesTedrick or @IsmaelChivite  - Would either of you have any advice on this topic?  There seems to be no answers to this thread yet, though it seems as though some folks experienced a resolution after some time.  I'm having this issue now, but mine is not resolving on its own.   I have a survey embedded in a dashboard (in edit mode) that has been running perfectly for 2 years now.  I recently had the need to add a related table to the hosted feature layer so I could add inspections to the features in the layer, which I found you can do via some python scripting in Notebook in ArcGIS Pro.  This seemed to work perfectly, until I discovered yesterday that my survey is now displaying the error "Cannot read properties of undefined (reading 'indexOf').  See screenshot below. I suspect this has something to do with the fact that there is now a related table associated with the hosted feature layer.     Here's my URL for the embedded survey:  "https://survey123.arcgis.com/share/[itemid]?mode=edit&globalId={field/globalid}&version=latest" I've checked this syntax and it is correct (and it has been in place and working for a long time now).  I suspect this error has something to do with referencing the globalId now that there is another sublayer in the hosted feature layer, but I don't know for sure.  I can tell you that when I remove the "&globalId={field/globalid}&version=latest" from the URL, the survey displays properly, though it does give the message that editing is not possible because there is no reference to the globalId.   Again, I think the key indicator for me is that this survey & dashboard have been operational for 2 years now with daily editing taking place and no issues.  It was only when I added the related table to the feature layer did the problem occur.  I think that helps point to the problem, I'm just not sure where to look (or what I'm looking for). Is it possible that the sublayer within the hosted feature layer needs to be identified within the globalId syntax (sublayer "0" is the feature class and sublayer "1" is the table), and is that even possible to make that distinction? Any advice you can provide would be helpful for both me and the other folks who have been experiencing this problem.  I need to get this back up and running as quickly as possible for the folks relying on this in my office.  I'm happy to send you the xls form for the survey or anything else that would help diagnose this issue.  Thanks! ... View more

@ZhifangWang Thanks for the info.  I had a view layer set up already, but apparently when I enabled Sync on the main feature layer it caused the Survey to encounter errors.  I learned my lesson there.   ... View more

@ZhifangWang I believe I have this fixed.  While initially trying to solve the dashboard embedded survey problem yesterday, I enabled "Sync" on the main feature layer upon which this survey is built in an attempt to ensure settings were correct for the Dashboard to view the survey.  After I discovered the problem with submitting to the survey, I suspected that my enabling Sync may have caused an issue.  After researching a bit, I found that you can disable sync, though it requires all view layers to be deleted.  While not ideal, I performed this action, deleting all view layers.  I then disabled sync on the main feature layer, then created a new view layer from that.  I then had to go back into my xls form for the survey and change the submission url under the settings tab to point to the new view layer, then re-publish the survey.  It seems to be working at this point.  I'll keep monitoring.   ... View more

@ZhifangWang Here is the link to the survey:  https://arcg.is/1arLCf0 Also, I've attached the xlsform to this post in the event you need to review that.   This particular survey is set up to use a View Layer of the original layer, set up for public editing.  I should also state that this is set up to add data to a related table, not the main feature layer.  As I stated, everything was working fine yesterday morning.  We actually submitted one for practice at about 8 am EST and had no issues.   ... View more

Well, now my survey won't allow submissions (not from within the Dashboard, just in the regular browser using the link to the survey).  It loads fine and acts normally when entering data, but upon hitting the "submit" button, I receive an error stating "Failed to Submit.  Object reference not set to an instance of an object".  Any ideas?  This is a public survey that I recently created and had been working fine through all of our testing until today, after the BUG referenced in this thread was fixed.  Now I'm receiving this error and can't seem to find a resolution to this issue.  ... View more

@RyanKopp you may have already found a solution to your issue at this point, but I thought I'd throw out a suggestion to look into.  I'm not sure how you'd do EXACTLY what you want to do, but have you considered adding a field to your feature layer attribute table that would contain the URL to the youtube video?  Then you could play around with different ways to access that attribute (from the pop-up, or creating a "detail" view in the dashboard, using the "list" to populate the detail view of your attributes, which would then show the URL and allow the user to click the link from there).  I'd have to play with this to see how it would function, but it's just a thought.  I don't know if your videos are fairly static or change frequently.   ... View more

This BUG has been marked as closed and, after some initial testing, it appears as if functionality has been restored.  Thanks ESRI team for the speedy resolution to this problem! ... View more

The beta site seems to work for me as well.  At least we have a workaround at this point.  I'll continue to monitor for any issues.   ... View more

@ZhifangWang Thanks for your quick response!  After reviewing the thread at the link you posted, it appears that I am experiencing the same issue, so we can let the responses be directed to that thread.  Thanks! ... View more

@ZhifangWang Excellent information.  Thank you! Tyler ... View more

@Anonymous User Thanks for looking into this.  I'll update to 3.14 as soon as I can to test this out.  Thanks for all the response.   Tyler ... View more