Pop-up Configuration in Map Viewer not persisting to Field Maps App but works from Classic

kmsmikrud · ‎06-15-2021

Hello,

I am working on configuring pop-ups for map layers that are reference layers within the map and not being edited. I have the pop-up configured how I would like it in the New Map Viewer. For the editable layers I have the forms configured in the Field Maps web app and they look good. However when I open the web map in Field Maps app the configured pop-ups (saved in the New Map Viewer) are not retaining any of the formatting and just show default. The pop-ups configured in the Classic Map Viewer look good.

I am also having an issue regarding pop-ups for arcade FeatureSet pop-ups not showing in the Field Maps app but show both in the New Map Viewer and Classic Map Viewer. For the map saved in the New Map Viewer and then opened in the Field Maps app this arcade pop-up expression does not show. For the map saved in the Classic Map Viewer and then viewed in the Field Maps app the pop-up expression shows like I want. The original reply to an existing post is here.

Is anyone else having this experience? I feel like its tedious configuring all the pop-ups that I shouldn't have to do this in both Viewers (Classic/New) and I thought since the New Map Viewer has moved out of beta basic functionality in formatting pop-ups should be there.

Thanks!,
Kathy

FMBAdmin · ‎10-14-2021

Hi Aaron,

I appreciate the response, thank you. It was my understanding related tables could be configured in the form viewer as well, but if I select it in the web app, it does not have the capability to configure the fields in the related table, only the fields for the feature class it's related to (plots in this case). Does it matter what the relationship class is based on? For this example, it's a one to many based on plot number and not on the GlobalID. In the attached snip - those fields displaying are for the feature class, Plots, not the TreeTable which is what I am trying to configure. I am a bit confused on that one. Thanks for any insight!

Anonymous User · ‎10-14-2021

@FMBAdmin

It sounds like you want to create a single form that uses fields from both the parent layer (plots) and the child table (trees). That workflow is not supported (it's on the medium-to-long-term roadmap though).

You have to configure a form on the plots layer and a form on the trees table. In the mobile app you can use the relationship icon to add a new tree record which will be related to the plot. Does that make sense?

FMBAdmin · ‎10-14-2021

Hi Aaron,

Yes in the mobile app they enter the trees per plot via the related icon - that is our existing workflow (I mean until a gridded repeat view in Survey 123 exists someday...)

I was looking at configuring the tree table as a form so I could make the entries required or have certain fields not be visible if it's a no tree plot for example, but it looks like I will be doing it in the schema instead at least for the required portions.

Even after configuring the form for the plots, it says there are no fields available to configure for the tree table. It's got to be something on my end, I'm just not entirely sure what? I attached another snip. I appreciate the insight.

Thanks.

Anonymous User · ‎10-14-2021

In your last screenshot, there are no fields listed because all of those fields have already been added to the form. If you remove a form element, the field will show up on the right side as a field that can be added to the form.

FMBAdmin · ‎10-14-2021

Right I understand that. I'm probably not explaining this well enough, sorry! The fields for Plots are showing in that screenshot even though the TreeTable table is selected. The fields for the TreeTable do not show as configurable or even appear anywhere in the Field Maps interface.

The fields in the related table aka TreeTable are vastly different than the fields for Plots. The fields that should be showing for a TreeTable form are PlotNumber, TreeNumber, Species, DBH, Status, Fate, Age, Defect, Height, Remarks, then editor tracking fields. In the form builder, the only things that will appear are the attributes for the layers, not the table. I hope that explains it more.

GISManager4 · ‎09-28-2021

Can you review my Custom URl and see if I am having same issue?