Latest Contributions by TylerBragg2

@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

Hi @Anonymous User , and thanks for your reply! The survey was published via Survey123 Connect (I think originally with v3.12).  I downloaded v3.14 Connect and re-published the survey.  No change on iOS device, Android, or from Windows desktop.  None will allow the upload.   There are no filters or constraints on the image questions, other than that I have them in groups.  I have three groups that allow 5 photos for one group, 10 photos for the other two groups.  This was done for a very specific reason, being that I need allowance for several photo uploads, but I don't want to use repeats for a number of reasons.  By doing it the way I have, I can set the groups to be collapsed by default (thus taking up minimal space on the survey), but the users can expand the groups and add up to 25 photos if needed.  By doing it this way, I can reference the individual photos for feature report generation.  This has worked perfectly up until now (well, last week).  You will see this in the attached xls form.   Again, I'll note that this survey is designed to be opened up in edit mode from Field Maps.  The feature is already created elsewhere, then the field staff use this survey to go in and add pertinent attribute data to the feature layer.  No related tables or anything like that on this one, so it's pretty straight-forward.   Thanks! Tyler ... View more

Ha! That's great!  That was much quicker than I expected, but that's a good thing.  Appreciate it Aaron.   ... View more

@Anonymous User  I just wanted to follow up with you to let you know that I found a workaround for the problems I was having with Workforce.  It's a long story, but there were several issues with Workforce preventing me from doing all the specific things we want/need to do.  As a result, I ended up designing with an entire work order system from "scratch."  This system is based on one feature layer for "work orders."  I have three surveys built off that feature layer in Survey123, with each geared towards the specific user group that is involved (dispatchers, field workers, admins).  I built a "Dispatch Console" in Dashboards that functions as the primary access to work orders from the office (similar to the Workforce web app).  This console contains the dispatch survey, as well as an "edit mode" version of a different survey to allow editing of the data.  The field workers access the work orders from Field Maps with a simple map that shows new or in-progress work orders.  I configured the pop-up of this map to contain a link to the "edit version" of a third survey that allows them to collect all the data we need for that work order.  In addition to all this, I used Integromat to automate three different processes - First is to send a text to the field supervisors whenever a new work order is created, second is to automatically look for a certain "flag" field (yes or no) in the data and if "yes" it will create a specialized work order report (feature report) that we are required to submit to another agency, and third, you can manually trigger a report for any work order by selecting a different flag field in the dispatch console, then the report is created and is automatically uploaded to our Sharefile server (and a confirmation email is sent to certain staff).  One additional advantage this system provides is the ability to be able to dispatch a new work order from the field.  The same survey that the dispatchers use from the console can be used by the field supervisors right from their phones.  Very simple.  Our staff seems to be thrilled with it so far.     I just wanted to pass this development along to you as some closure to the issues we had discussed and to let you know that this is possible to achieve a work order system similar to, but separate from Workforce, in the event you run into anyone else with a similar need.  I'd be happy to show you the system if you ever felt the need to see what I'm talking about.     Thanks again for all your help previously.     Tyler ... View more

That's exactly what I needed to know.  Thank you! ... View more

Thanks for the info Aaron.  Sounds like it will be a waiting game then.  Do you have any recommendations for a workaround to extract the attributes from a feature in a Workforce assignments layer?  It would be so easy if the payload of the webhook would include, at a minimum, the objectid of the feature that was updated, but it doesn't give any specifics.   I was just looking at the payload information as I'm typing this, and I see that it does give the "lastupdatedTime." Now I'm wondering if it would be feasible or reliable to use the HTTP module in Integromat to query the assignments layer for features with the same "lastupdatedTime."  There should only be one feature with that updated time, right?  Am I thinking correctly?  If I could query using that, then I could extract attributes for the feature with that exact updated time.    ... View more

Thanks @Anonymous User!  I assume an "internal issue" could take quite some time to resolve?  Or does it depend?   ... View more

@MikeSlattery  Unfortunately, my response to this post is not an answer to your question, but rather is support for your initial problem.  I, too, am receiving replica errors when running the same process in Integromat, built from the same guide you referenced above.  Specifically, my error is coming in when making a request to the StatusURL, and my error reads as follows: "Unable to synchronize replica...Error in processing replica sync request"  In my situation, my webhook is set up on a Workforce assignments layer (which is Sync enabled).  I need to extract attributes from a workforce assignment once it is marked as "complete" for further processing and report generation.  This wasn't an issue with the previous version of Workforce, but since they upgraded to the "offline compatible" sync-enabled version I'm experiencing this issue.  I can't seem to get past this in order to extract the needed attributes for my process.  Since your last post on this was in January, I'm curious if you found a solution to the problem?  If not, hopefully someone else can chime in with some guidance.   Tyler ... View more

@SunnyCorrao the case is still open with ESRI Support Services.  It's been frustratingly slow and fruitless thus far.  Nobody can seem to figure out the issue.  My last update was on 7/8/21 via email from the technician working on the case.  Here is what he said - "After collaborating with our internal resources, we have determined that this "Failed to Submit" behavior is a defect. I am currently logging this defect and will send the information to our development team. I will reach out soon with more information on the defect and steps for following its progress."  I have no idea where we go from here or what the process is to fix a "defect."  But I guess I'll just have to wait and see.  I would have thought the behavior would be fairly easy to trace from their end, but evidently not.   Tyler ... View more

I'd like to see this feature as well.  I have a date field with conditional visibility based on a "status" field.  When the user updates the status field to "Closed", they must enter the "date closed", and I would like for the date field to auto-populate based on today's date so they don't have to select it manually.   ... View more

@JamesTedrick  are you able to shed any light as to where the webhook action takes place - on the server or the client?  I have a survey where this issue has occurred multiple times, and it happened again this morning.  This is a public survey where the survey is completed via the Survey123 web app - so surveys are ever submitted via the Survey123 mobile app.  I have a webhook set up in Integromat to automate some processes with the submission data and there have been serval times where it appears there was no trigger for the process after a survey response is submitted.  Since this keeps happening, I need to figure out what is going on and resolve the problem.  I'm not sure where to look at this point to determine why there was no action.  I have checked in Integromat, but there are no errors for this submission - it just appears as if it didn't receive any notification of a new survey submission because there is no record of it at all.  There seems to be some confusion/disagreement as to where the webhook is generated.  I assumed that it must be from the server, since that's where the webhook is configured (and also given that feature level webhooks are set up from the server as well), but I may have assumed incorrectly.  Can you clarify?  I think this will help me get an idea of where to look.  Then there is the question of a webhook log - is there somewhere that has a log of each webhook action?  Any help would be appreciated.   Tyler ... View more