topic Re: Filter Point Features By Related Table Records in ArcGIS Experience Builder Questions

Filter Point Features By Related Table Records

AKRRMapGuy — Wed, 05 Mar 2025 20:30:12 GMT

We have a table that is related to a Feature Class by a Feature ID. The table contains inspection records, associated with one point in the point Feature Class.

I am trying to make an EB app that filters the points and gives statistics aggregated by the Inspection Table values, such as inspection date. I can't figure out how to get the points to honor the table filters. Is this even possible? I have found some old posts that make it seem the related Feature functionality might end at pop ups?

We are using ArcGIS Enterprise 11.3, and the layers are referenced to SQL Server.

Re: Filter Point Features By Related Table Records

Ke_Xu — Wed, 26 Mar 2025 09:16:23 GMT

Hi @AKRRMapGuy,

If the point layer and table have common fields, you could try to use the Group Filter.

Thanks,

Re: Filter Point Features By Related Table Records

AKRRMapGuy — Wed, 26 Mar 2025 16:03:03 GMT

That's an interesting idea, If I default it to the 'max' date value it might give stats on only the newest records from the table. I am not sure if that is possible, but we will find out. The Feature ID would have to be the link I think, even though that isn't what we are filtering.

Re: Filter Point Features By Related Table Records

Ke_Xu — Thu, 27 Mar 2025 00:54:37 GMT

Hi @AKRRMapGuy,

Group Filter allows the use of expressions. Currently, it is not supported to filter related Data directly by Filter. We will consider this requirement.

Thanks,

Re: Filter Point Features By Related Table Records

AKRRMapGuy — Thu, 27 Mar 2025 20:50:34 GMT

I really appreciate that. This functionality is very important for asset management. This matters for ArcGIS Dashboards too. The maintenance records are not the 'feature'. The maintenance records are related to the feature and contain all of the information about the condition and some other things. The ability to make the newest 'record' interactable both directions via the Feature is a huge deal.

Re: Filter Point Features By Related Table Records

ShengdiZhang — Tue, 03 Mar 2026 06:47:25 GMT

Hi @AKRRMapGuy ,

In the latest Feb 2026 AGOL release, we support selecting and filtering data records using the "Data filtering changes" trigger. This enhancement allows related layers to be filtered automatically when a filter is applied to the parent layer.

Please note that there is currently a limitation for performance considerations: the action will not run if the filtered results from the trigger data exceed 1,000 records.

Let me know if you have any questions or need further clarification.

Thanks,

Shengdi

Re: Filter Point Features By Related Table Records

AKRRMapGuy — Tue, 03 Mar 2026 17:02:30 GMT

Amazing! This sounds exactly like what I need. One point of clarification, when you say filtered results, do you mean filtered out or remaining IE. 1000 hidden or 1000 displayed? Personally, if it runs a little slower, the option to go beyond that really wouldn't hurt my feelings, depending on the definition of performance.

Hopefully this makes it into Enterprise 11.1!

Re: Filter Point Features By Related Table Records

ShengdiZhang — Fri, 06 Mar 2026 08:35:31 GMT

When I say “filtered results”, I mean the remaining results after the filters are applied, not the records that are filtered out. So the limit refers to 1000 records displayed, not hidden.

This enhancement is currently implemented using a workaround. ExB sends multiple requests to filter the related table. During our testing, we observed that the app could crash when the number of returned records was very large. To maintain stability, we introduced the 1000-record limit.

If this enhancement can be implemented on the server side in the future, we should be able to improve the feature and remove this limitation.

Thanks,

Shengdi

Re: Filter Point Features By Related Table Records

AKRRMapGuy — Fri, 06 Mar 2026 17:35:53 GMT

This is amazing news, getting this to work robustly in the whole ArcGIS ecosystem is probably the biggest thing ESRI could do for me right now. This opens up a massive opportunity for new apps that meet multiple of my users requests.

Thank you so much!