Latest Contributions by JakeMatthys

Thanks for the information Craig...  - Jake ... View more

Hello Jeff (or anyone at ESRI with Workforce), Do we know what future version of iOS will no longer support Workforce Classic?  In other words, if we are using iOS devices with Workforce Classic, is there a possibility that we could get forced off of Workforce Classic before Dec 31st 2021 because of a iOS update? Thanks,  - Jake ... View more

Thanks for the information Jeff...  - Jake ... View more

Thanks for the information Phil.  I will go to the EAC to check it out.  - Jake ... View more

Thanks for the help Matthew.  It is looking like I will need to allow the survey publish process to create a new feature service, but it turns out that creating a new feature service will not negatively affect my downstream workflows, so I will proceed with publishing.   Thanks,  - Jake ... View more

Hi Matthew, Where would I look for the URLs used within the survey/form itself?  I looked in the form.info file (as downloaded from Survey123 Connect), but there is no ServiceInfo section.  Although, when looking at the form.info file for the published form (downloaded with AGO Assistant), there is a ServiceInfo section with a HTTP url for the feature class. Let me know where to look of the URL used with the survey/form itself. Thanks,  - Jake ... View more

Hi James, Thanks for the feedback.  Adding those itemID entries to the operational layers in the map resolved our issue.  I am highly confident that we did not remove those itemID entries yesterday, but now that they are present, Workforce dispatcher seems to be working.   Thanks again so much for the help.  - Jake ... View more

Hi James, "craig_sp" has been added as a dispatcher to our project.  You should have received an invite. Thanks,  - Jake ... View more

Hi James, The Chrome dev tools does show a console error: workforce-web-662ca690a546cd6b33a277fb980d1260.js:487 Uncaught (in promise) TypeError: Cannot read property 'renderer' of undefined     at d._prepareMap (workforce-web-662ca690a546cd6b33a277fb980d1260.js:487)     at new d (workforce-web-662ca690a546cd6b33a277fb980d1260.js:485)     at i.createComponent (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:6769)     at Object.create (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:1490)     at Object.evaluate (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:3559)     at Object.evaluate (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:3446)     at Ne.evaluateSyscall (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:3699)     at Ne.evaluateInner (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:3691)     at Ne.evaluateOuter (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:3691)     at mt.next (vendor-976bcedddd661ffdfc8ce1d28fa151c4.js:3823) The Dispatcher map only contains the workers and assignments layer.  The Dispatcher map can be viewed in both map viewer classic and map viewer beta.  Yesterday, the Dispatcher map had a broken layer, I removed the layer using AGOL Assistant in hopes that it would resolve the Workforce issue, but it did not. ... View more

Hello, Our organization also began experiencing issues with Workforce Dispatcher yesterday (08/04).  When we open our Classic Workforce project in Dispatcher we get a blank screen (no map, no list of assignments).  We will submit an ESRI helpdesk request.  Just wanted to chime in that we are also experiencing issues with a Classic Workforce project that has Survey123 integrations. Thanks,  - Jake ... View more

Thanks Craig, I will monitor and elevate if the situation does not improve ... View more