Workforce Additional Fields - even in new autoupdate layer

[JulieCulligan]

Hi Everyone, 

is it possible to add additional fields to the Workforce layer without corrupting the layer?  I don't need to see them in the workforce window, but would like to be able to update them in another app and have it land in the same layer.  any workarounds are appreciated, working in the latest version of enterprise. 

[Scott_Sambell · Accepted solution]

Hi Julie.  Yes, we do this on all our Workforce "Assignments" layers and build our own dispatcher interfaces in Experience Builder to populate them, then concatenate and format them in the description field so the field worker can see them in the app as well.

So, yep, you are fine to add as many fields as you want in the Assignments layer.

[JakeMatthys · Accepted solution]

Hi Julie, I can also confirm (like Scott) that you can add additional columns to the Workforce Assignments layer.  We have additional columns that we expose via integrations with Survey123.  One thing we have learned though is that you should not attempt to change the symbology of the Workforce layer (make the symbology based on one or more of the additional columns).  Symbology will behave in a webmap, but not the native mobile app.

- Jake

[IanGallo]

We've added a simple extra layer(s) of dots slightly bigger than and behind the assignment symbology to help staff differentiate between different assignment types on the map. 

[IanGallo]

Works well for us to and makes the app/feature service significantly more useful, especially in dashboards/experience builder.