Dashboard Selector for Related Records?

[Kara_Shindle]

Is there a way to have a selector populated with fields from a related table, that when one is selected, filters the related locations on a map?

I have a Dashboard I'm working on building for our county Vector Control guy.  We have tick dragging locations on a map, and a related table of Drag Reports, where he enters the tick species that are captured at a drag.

He wants a filter on his dashboard that will

so like say I wanted only the drag sites that i caught Dermacentor variabilis, I could selected that specie and only the spots where that species has been found will pop up on the map

Seems to me that this should be possible with field mapping but I have not been able to get this.

I have it wired in the opposite direction, where selecting a map location filters a list of related reports, but I've not had success coming up with some combination of widgets that allows him to select a related table field to filter the map.

Any suggestions?

Thanks!

[Kanin]

Hello Kara,

ArcGIS Dashboards support configuring a Selector from a related table (e.g. table B) and sending the filter action to a layer in the map (e.g. feature class A), as long as you configure the key field as the filter field, which is depends on how the relationship class was created.

Usually, the GlobalID & GUID field is used.

Best regards,
Kanin

If this answer solved your question, please mark it as the answer to help others who have the same question.

[Energy4all]

Can you give us any more insight into this?

[KimberlyK]

Hey @Kanin - I realize your reply is several years old but there are many of us still looking for this solution. The work-around that creates a secondary list widget to filter the data on the map is clunky. Would you please give us an example and specify the widget type for what you describe because this is still an issue in Dashboards. Thank you.

[JoshSaad]

I've got a similar situation (I think).  I've got a dashboard showing emergency generators, and an indicator showing the amount of fuel used, which comes from a related table.  I'd like to filter the amount total when selecting a generator or multiple generators from a list.  When I try to configure the Filter in the list, the GlobalID field isn't in the list of available fields to filter by.

My relationship maps the GlobalID field from the Generators point features to a GeneratorID field in the GeneratorMaint table.

[jessneuner]

Hello -- 

I've got a similar question -- 

We are using GlobalID and GUID to link the related table to the parent. 

I'd like a selector based on the related table (category field) that then filters the parent... but i'm having trouble figuring out how to choose that option in the filter -- it seems like it wants a category field in the parent table ... 

i tried a version that added a join to the related table, but the dashboard didn't seem to like the join ... 

Is this possible?  Thanks for any help or direction you can offer!

[Chris_Kell]

Hi Jess,

Did you ever get this to work?  I'm trying to deploy a selector on the child table and have it affect other selectors and widgets on the dashboard.

Thanks

Chris

[jessneuner]

Hi Chris -- 

Not yet.  I have a thought to try data expressions for this use case -- but so far navigating 'backwards' in a 1-M relationship has stumped us. 

jess

[Chris_Kell]

Hi Jess,
I've had some success with creating a relationship class on desktop then sharing/publishing the individual layers to portal/ago. On the dashboard side, the closest I've come is using a selector with categories set to "Features."
[cid:image001.png@01D9824B.D8014420]
Doing this has allowed me to define the actions appropriately, but the "Features" definition creates a selector value for every row in the feature service.
I'm researching baseing the selector on a "Data Expression," and I've opened a case with Tech Support. I'll keep you posted.

-Chris

[KimberlyK]

Hey @Chris_Kell - I am in search of this same solution to eliminate multiple identical attribute names using the Features category but still retain the ability to use a related field to select from the feature layer. I created a related table data expression to provide the data to the selector, but I have yet to find a widget configuration that works. Did you ever find an answer to this issue? Would you please post it if so? Thanks.