"Editing of the content is disabled." Error for Related Table in Field Maps

521
3
06-06-2022 11:54 AM
CharlieFredericks1
New Contributor

Hello! 

I am working with traffic sign maintenance app within Enterprise and published from Pro. I have two point layers, one for signs and one for posts; each point layer has a related table (and relationships) to track maintenance activities and the tables are set up exactly the same, named "Sign Activities" and "Post Activities". When I go to set up the form in Field Maps, I can create a form for both tables. However, the "Post Activities" table is greyed out and gives the error, "Editing of the content is disabled." (See TableDisabled-FieldMaps.jpg screenshot). The "Sign Activities" table (and form) work perfectly in the Field Maps web and phone app, however, the the "Post Activities" table does not appear in the phone app at all (See PhoneApp_RelatedTableNotAppearing.jpg screenshot). 

I have been unable to find any other posts citing the same issue, and those that were similar did not solve the issue, so any help or ideas would be greatly appreciated! 

Thanks! 

3 Replies
gradstudent527
New Contributor II

Have you created everything within the fieldmaps/arcgis online vs creating a map in Arcpro uploading it and then adding tables ect? I ran into a similar issue with feature classes not appearing and it was because I was adding them to maps I created in Arc Pro and shared as online maps then added my feature layers to.

Have you enabled offline for everything? could it be a possible issue with that?

0 Kudos
JasonKerby
New Contributor

I am having exactly the same problem. I am pretty sure I solved it before, but have no recollection on the specifics. I created the map and tables in Pro then shared to AGOL. WFL settings show editing enabled for the entire feature layer, but 2 of the many tables have the "editing of the content is disabled" status. Don't suppose you surmounted this one and can share? Once I've got it licked, I'll post an update.

0 Kudos
JasonKerby
New Contributor

So, it turned out that the two tables which were not editable (and so not configurable in Field Maps) did not have relationship classes established. Once I created the relationship classes, the tables became reachable for editing and all is well.

0 Kudos