Enable referenced Feature Layer for task

[AndreasHall]

Hi, I am trying out the new tasks functionality in Field Maps. I want to use a EGDB layer published as a Referenced Feature Layer as my task layer. I get this message:

I am the owner of the layer and it has editing enabled. I have manually created the fields that are needed:

I have enabled sync:

Is there something that I am missing?

I am on Enterprise 11.5.0.

[AndreasHall]

I have now added some missing domains and enabled Replica Tracking. Perhaps some more things that I have forgot already. Still not working.

[Faiez]

This works in ArcGIS Online but not in ArcGIS Enterprise because Field Maps applies stricter ownership and permission rules in Enterprise. Tasks are not supported on referenced ArcGIS Server feature services or layers published from an Enterprise geodatabase. Publishing the layer as a hosted feature layer may resolve the issue. 

Good luck!

[AndreasHall]

The communication I have received from Esri INC says it is also supported for existing feature layers that are referenced or hosted. The documentation is not super clear on this but there are mentions of ArcGIS Server Manager there: Prepare tasks—ArcGIS Field Maps | Documentation.

[PiyaliKundu2 · Accepted solution]

Hello @AndreasHall - It appears your Due Date field is incorrectly entered. The field name should be esritask_duedate (duedate being one word). You entered esritask_due_date (with the underscore).

Please try deleting the field and re-adding it, and let us know if that works.

[Faiez]

@PiyaliKundu2 

A user can have a display name with spaces, but the field name can’t include spaces or special characters. The display name is what the user sees, and the field name is used for machine processing. Would there be any problem if the user changes the field name?

[PiyaliKundu2]

Hello @Faiez - I'm a bit confused - which scenario are you referring to when asking whether changing a field name would be okay? 

With regards to the Field Maps tasks, the field names for the required esritask_ fields must be spelled specifically as stated in the documentation. This is purely because, with this currently release of the capability, Field Maps Designer looks for those fields in the data to build the tasks configuration off of - whether it is by adding them in the enabling process, or the owner of the data manually adding them and the domains prior to enabling.

Once tasks is enabled on the layer in Designer, the fields that are required for tasks to function appropriately on mobile are esritask_status, esritask_type, and esritask_assignee. The data owner could technically get rid of the fields for priority, due date, description, and notes and use their own fields for those concepts in the workflow.

In the future, we are considering adding the capability to allow users to "point" the tasks enablement process to their own existing fields, so they wouldn't have to add any additional fields if they didn't want to.

Hope that helps explain things a bit better.

[Faiez]

Hello @PiyaliKundu2 

Thank you very much for your clear explanation. What I meant to ask is what happens if a user sets the field alias (display name) as “Due date” and the field name as “Due_date” before creating any tasks in ArcGIS Field Maps as shown below:

[PiyaliKundu2]

Based on your screenshot, nothing would happen. Your screenshot shows that you already have the field esritask_duedate in the schema which is the field we are looking for in order to enable tasks.

After enabling tasks, you can use your other Due_date field if you'd like instead. Just make sure to reference that field in the Form and task configuration as you build your layouts and actions. The esritask_duedate field is only required to enable tasks in Field Maps Designer. You don't need to keep it in order for tasks to be used in Field Maps mobile - so you can use your other Due_date field instead after tasks has been enabled.

[AndreasHall]

Thanks, this seems to have solved the issue. Interesting that a wrongly spelled optional field had this big impact.