I can't figure out why workforce and survey123 won't open an existing point on a form!! Our survey form is a feature service in portal which meets all the requirements. We created a project in workforce, assigned our survey form to the integrated app section, set the Workforce Field to [ID] and the survey123 question Field to [email] for testing purposes. Every time I go to the IOS Workforce app, open an assignment, reroute us to survey123 an entirely new survey will be opened verses checking for an existing one. I am working with an ESRI rep and he doesn't even understand why this is happening.
FYI - I did create another enterprise gdb environment with the esri reps attachment and I am still have the same problems getting workforce to open an existing feature.
Portal v10.6 | federated
Esri - Notes
It was a pleasure talking with you the other day! I am glad we were able to hop on a screen share and troubleshoot the behavior we are encountering.
Just to recap:
I have been testing on my end and unfortunately am encountering some issues with the feature service published on my end. I have created the survey using the existing feature service and published the survey to my Portal. I have configured the Survey123 custom submission URL in a web map for use in Collector. I collect the point in collector and click the link to go to the survey. Once the survey opens I fill out the information as we did on the screen share, but when I submit the survey the submission hangs on "TestReportServicsTested" related table. I had captured the web traffic when submitting and it seems that the requests that are being made are made for every single other service in the server and not the table of interest.
Moving forward as I am working through the testing limitations encountered I have a couple of tests to try to obtain a better idea of the behavior encountered.
If you have any questions or updates please feel free to contact me via phone by calling 888-377-4575 and referencing this case #02309159, or simply by replying to this email.
Solved! Go to Solution.
If I might ask, how is the inspection data stored? The primary paradigm that we support in Survey123 is having separate asset tables (which store basic data that rarely changes with asset - id, date installed, basic characteristics) and inspection tables (which store a point in time evaluation of the asset). The two can then be related through the use of a common id - this pattern works with Workforce currently.