Latest Contributions by TylerBragg2

@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

@ZhifangWang  and @Anonymous User  I just conducted a test to see if I could identify a solution, and it worked.  Here's what I did: I did still have the 3.12 version of Survey123 Connect installed.  I opened the survey up and re-published it from 3.12.  I then opened the "Settings" tab of the survey in the Survey123 web app to verify that it recognized it as being published with 3.12 and it did.  I then ensured that it was fixed to this version and not to update to the latest version.  I then removed the "version=latest" url parameter from my link to the survey, opened it from Field Maps using that link, and it appears to be functioning properly for now.  I will continue to monitor this application to ensure proper function.   It would be great if you could update this thread or the other one you linked when the bug has been fixed, or when the expected fix will occur.   Thanks again! Tyler ... View more

@ZhifangWang  and @Anonymous User  I briefly tested the photo upload with several .png files and yes, what you mentioned above does seem to be the case for me.  The .png file appears to upload correctly.   That brings me to the question - is there a work-around for this?  I believe I still have Survey123 connect versions 3.12 and 3.13 installed on my computer.  Would it work for me to go back and re-publish this survey with an older version to get it working again?  Or is it even possible to revert a published survey back to a previous version.   As a side note, I believe I will have to change my URL parameters to remove the "version=latest" in order for this to work.  My survey was originally published with 3.12, then updated with 3.13 and I was still experiencing this issue, but my theory is that because of the "version=latest" parameter, it was using the 3.14 version of the web app.  Would you agree with this part?  Thanks to all for digging into this.  Now to identify a temporary fix to get things up and rolling... Tyler ... View more

@Anonymous User here's the URL: https://survey123.arcgis.com/share/192a4eacc3634ea19d511963dc723076?mode=edit&globalId={globalid}&assignmenttype={assignmenttype}&status={status}&address={address}&priority={priority}&submitdate={submitdate}&duedate={duedate}&description={description}&Dispatcher_Name={Dispatcher_Name}&latitude={latitude}&longitude={longitude}&version=latest As you can see, I do pass several attributes into the survey using the URL parameters.  Again, all this has been functioning perfectly well for 6 months now.  And I have other applications that function similarly that aren't experiencing problems (that I'm aware of at the moment).  Let me give you just a little background on this layer so you understand what it's doing:  I created a work order system for our sewer department.  I have another survey built from this feature layer that is the "dispatch" survey.  From that, we actually create new features that represent a new work order for the crew.  Only attributes pertinent to the dispatch information are populated in that survey.  I have some automatic notifications set up using integromat, so the field crew gets a text telling them there's a new work order.  Then they open up Field Maps to a map that shows only new or in-progress work orders.  They can find the point they're looking for, open the pop-up, then there's a link to this survey.  From this survey, they fill out all information pertaining to the work order, including pictures, then they can mark it as completed and submit.  Completed work orders are filtered out of the map so they only see ones that still need worked.  Then there's a dashboard where you can view all the work orders and the details of each (and there's a third survey that's a "master" editing version that's embedded into this dashboard so that the admins can edit anything they need to).   So that's a brief overview of how this survey ties into the workflow.  I find that knowing the background about something helps me to understand things a little better.   I'm thinking about completely rebuilding this survey from scratch, exactly the same as it is, and publishing new to see if that works.  I can't really afford for this thing to be non-functional for any length of time, especially for unknown reasons.  I've already got the field guys quizzing me about it daily.   Thanks! Tyler ... View more