Select to view content in your preferred language

Related table entries on mobile don't reflect form configuration

646
2
Jump to solution
07-24-2023 07:18 AM
MSFIVolunteers1
New Contributor II

I created a layer and related table (in Pro, published to AGOL) that have the same fields and should have the same form configuration - these record similar activities performed periodically on a set of points.

I configured the layer form in FM Designer with a number of contingent-visibility questions and saved the configuration both to the map and to the layer. I then configured the related table identically, again saving the configuration to both map and table.

The layer presents properly on a mobile device, with contingent visibility as specified. But a related entry for the same point simply shows all the fields, as though the form wasn't configured at all. Why doesn't the related table form configuration show?

On a possibly-related note, I'm confused about managing the layer properties - whether I should specify that the properties are stored in the map or in the "source layer" for both the layer and the related table. BTW, in FM Designer I get the message that "related records are not currently supported on mobile", which led me to play with managing the layer properties per some prior Forum messages. But the error message remains, although I can see and add related records (without form configuration as noted above) on a mobile.

I suspect this is "operator error" on my part. Any guidance about how I can get the related entries to show the proper form configuration?

Thanks for your help,

Dan

 

 

0 Kudos
1 Solution

Accepted Solutions
ChrisDunn1
Esri Contributor

Hi Dan,

The issue you are running into with the related table form is actually a known bug that is actively being worked on. The public bug details are available here: https://support.esri.com/en-us/bug/in-arcgis-field-maps-designer-when-saving-the-form-to-a-bug-00015...

As for whether you should save the form to the layer or the map - it really depends on if you are going to need different forms for each map (in which case you'll want to save the form to the map) or if you are going to re-use the layer with the same form in multiple maps (in which case you'll want to save it to the layer). You can find more details here: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/reuse-forms-in-arcgis-field-maps...

I hope this helps!

Chris

View solution in original post

2 Replies
ChrisDunn1
Esri Contributor

Hi Dan,

The issue you are running into with the related table form is actually a known bug that is actively being worked on. The public bug details are available here: https://support.esri.com/en-us/bug/in-arcgis-field-maps-designer-when-saving-the-form-to-a-bug-00015...

As for whether you should save the form to the layer or the map - it really depends on if you are going to need different forms for each map (in which case you'll want to save the form to the map) or if you are going to re-use the layer with the same form in multiple maps (in which case you'll want to save it to the layer). You can find more details here: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/reuse-forms-in-arcgis-field-maps...

I hope this helps!

Chris

MSFIVolunteers1
New Contributor II

Thanks, Chris. I tried the workaround in the bug report and it works.

Dan

0 Kudos