Unable to Open: Assignment types table is missing from map

[mackenzie_firstname]

Hi there! 

We use Workforce with ArcGIS Enterprise, and today one of our mobile workers came across this issue when trying to open the map (screenshot attached). It was their first time signing in and trying to open the map.

Unable to Open: Assignment types table is missing from map

We've previously had this issue and fixed it by reinstalling Workforce. However they tried this a few times and this doesn't seem to fix it. 

We do have sync enabled on the layer, and it all other users can open the map.

Any help would be greatly appreciated 🙂

[CraigGillgrass]

@mackenzie_firstname Do you have a pre-planned Map Area setup for this project?  Or are the workers creating their own map areas when they download the project?

Craig

[Bertodiem]

No

[Bertodiem]

Greetings, were you able to resolve this issue?, I am getting the same error in the new workforce version.

[CraigGillgrass]

Hello, are you using Online or Enterprise?

Do you have a pre-planned Map Area setup for this project?  Or are the workers creating their own map areas when they download the project?

[mackenzie_firstname]

Hi @Bertodiem,

Apologies for not posting an update on this. We carried out some tests for this user such as getting them to sign into a Test account, and also removing/adding back the Workforce project layers and tables to the Map Area we defined, but the error was still occurring. 

We use ArcGIS Enterprise and FME for some background tasks, and the issue was that the GlobalID for one Assignment Type was not matching the corresponding Assignment Type field on the Workers Layer - because one of our background tasks was making it lower-case. Once we had fixed that, the worker could now see their assignments. The reason all other users could continue to see their assignments was because this user was the only one who had assignments with the affected assignment type.

Hopefully this helps in some way! 

[StefanUseldinger]

We also had this issue. In our case, the message was misleading. Our network application security manager blocked all HTTPS requests to the Workforce Feature Service. We saw this by inspecting the Workforce logs. Great feature