Latest Contributions by JakeMatthys

Yes, we have experienced this issue (community post ).  We are now at Enterprise 11.3 and this issue does still occur, but very infrequently.  Probably occurring on the order of once a month or quarter and we are receiving 3000+ surveys per month.  We have band-aided the issue by running a job hourly for those webhooks that are mission critical and time sensitive to process any records that may have been missed.  For my organization, we felt that the effort to research and resolve this issue outweighed the cost, so we are living with the minor inconvenience that is causes us.   - Jake ... View more

@ModernElectric  We use FME to load new records into our Workforce Assignments feature layer.  Our assignments come from a different system and we use FME to extract data from the source system, translate the data and load it into the Workforce feature layer.  We have not had issues with assignments not being able to be selected in Workforce.  Have you looked to confirm that those assignments that cannot be selected have a valid geometry (by viewing them in ArcGIS Pro)?   As for the integration between Workforce and Survey123, we use the Assignment Integrations table in the Workforce project to relate the survey to the Workforce Assignment type.  The Workforce app will use this table to create links in the assignment based on the integrations established in the table.  - Jake ... View more

Workforce assignments by default is a point feature service.  It will not support creating a line or polygon geometry for as the assignment.  In our case we pair Workforce with Survey123, where Workforce represents the location that the inspection is taking place (point) and we use Survey123 to record the field observation that took place (in some cases a pipeline observation) and relate the observation to a specific pipe.   - Jake ... View more

You can add additional columns to the Workforce schema.  For example, we have added a 'project_id' column to the schema and we expose that to the users via the 'description' column.  The 'description' value is a concatenation of the 'project_id' column and various other pieces of information.  The value for our users is that they can search by project ID via the search functionality because it works across the description value.  On the back end, we use the project_id column to drive reporting.  You could add additional columns to hold feature id or location information, the rub is that they have to be exposed to the user via one of the native columns that are leveraged by the application. ... View more

Sorry, here is the link to the ESRI post regarding field maps tasks and the early adopter program...  https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here ... View more

Here is the link to the Field Maps beta post regarding tasks and the early adopter program: Field Maps 2025 Updates - Plan and coordinate field work using tasks ... View more

Not sure if this a recommended by ESRI, but we have added additional columns to the Workforce Assignment Schema to meet a similar need.  The additional columns store information that is known a the time of assignment creation and that we want to pass downstream to the Survey123 that will be generated from the assignment.  The caveat is that if you add additional columns to the Workforce Assignments schema, you will not be able to edit them in the Workforce Dispatcher app.  In our case that was ok because we us custom .Net code to create our assignments (and populate our additional add on columns).   ... View more

Following this topic.  My organization also has use case to prevent duplicate submissions based on a key value. ... View more

We periodically delete (move them to a different storage repo) the completed assignments from Workforce (we do 250k assignments a year and the dispatcher map becomes slow and meaningless with that many records).  We have found that when we remove completed assignments, the Workers must reload the Workforce project.  I think the explanation is that records that exist on the replica (on the iPad) no longer exist on the server (because we have deleted them) and it causes replica sync issues.  Our practice is to ask all users to sync by a certain date or risk losing some data because they will be forced to reload the project after the assignment cleanup has taken place.  - Jake ... View more

I believe that all content in the webmap that is consumed on the tablet must have sync enabled.  If not, the assignments/workers data will not sync.  My org has had issues with this from time to time.  I create a copy of the webmap (for backup purposes) and remove all the layers (with the exception of the workforce layers (assignments, workers, etc)) and save the webmap and verify that syncing works.  Then I start adding layers and continue testing.  In the past, I have found that the culprit is a service that has sync enabled, but maybe the GDB level change occurred that affected a column.  Anyway, this method (though long and arduous) can help identify the culprit. Good Luck...  - Jake ... View more

Sounds like you have all the steps covered.  We have webhooks setup on our S123 surveys that trigger FME automations.  It is a stable process that has been running with little issue for the past few years. A few items to check (though you probably have already checked them already) Ensure that the FME Server Automation automation is running Copy the webhook URL from the FME Server Automation and paste it into the S123 Webhook Payload URL You can do some testing Add a logger to your FME automation, that can help expose the payload that is coming in In the S123 Webhook Trigger Events, turn on "Existing Record Edited" and manipulate an existing record, see if you can generate the webhook to fire in this way. The the FME Automation require any authentication? Again, the process you described in the original post looks correct to me, no steps appear to be missing.  Maybe the list I provided will expose something that helps... Good luck.  - Jake   ... View more

Are the sync issues resolved on the mobile device if the user reloads the Workforce project on that device? We periodically delete completed Workforce Assignments as well for performance reasons.  This action will essentially orphan the record that is on the device because it can no longer be synced back to the server.  We have found that sometimes after deleting Workforce assignments, the mobile users need to reload the Workforce project on the mobile device (essentially, this creates a new replica on the mobile device). That has been our experience...  - Jake ... View more

We use python to append additional content to the location field in order to aid field staff by co-locating critical information for the assignment.   ... View more

I would also like to see the connected server name exposed in the Field Maps App (maybe in the profile section).  I find that I open the app for development/testing purposes and need to sign out to choose my server because I do not know which server is currently connected.  - Jake ... View more