Latest Contributions by ShengdiZhang

Hi @andrewdc_tt , Could you share a sample app with me? If so, please also share the print service and the data used in the app. Thanks, Shengdi ... View more

Hi @MelanieNeedle , I can access your print service now and reproduce your bug. However, as I said earlier, the print success if using the default AGOL print service - https://utility.arcgisonline.com/arcgis/rest/services/Utilities/PrintingTools/GPServer/ I think this bug is probably due to something related to your print service. Thanks, Shengdi ... View more

Hi @MelanieNeedle , Sorry, I missed your earlier comments. I cannot access the print service in your sample app, so I used the default AGOL print service for testing. Everything works as expected on my end. When I enable layers in the Map Layers widget, the print output includes all legends correctly.     Could you provide a bit more detail about the issue you encountered and what you were expecting to see? Thanks, Shengdi ... View more

Hi, I tested your app and what you’re seeing is expected behavior. Before the February 2026 AGOL release, the Print API did not support dynamic legends, so all features were always displayed in the print output. Dynamic legend support was added recently. However, because this app was created before that release, the print widget still uses the previous settings and behavior to avoid introducing unexpected changes. If you’d like to use the dynamic legend, you can simply remove and re-select the print service in the print widget to update the template settings. After doing this, the print output will include only the features that are visible in the legend by default. If you prefer to include all features in the print legend, you can enable "Always show all features" in the print template settings. Please let me know if you have other questions. Thanks, Shengdi ... View more

@JasonBOCQUET  Dev Edition 1.20 will be released on March 25. ... View more

@LJackson29Experience Builder is data-centric. If you only want to filter certain widgets, you can create a data view and apply the filter there. Then, select that data view for the widgets where you want the filter applied.       ... View more

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 ... View more

Hi @John_Hall , Are you using the default AGOL print service? The legend in the printout should only include features that are visible within the map's extent by default. Would you mind sharing your app and data with me? My username is she10946. Thanks, Shengdi ... View more

Hi @SanchezNuñez @Laura , In the latest Feb 2026 AGOL release, the “Data filtering changes” trigger now supports selecting data records. When using this message action, if “Enable filtering for layer source search” is activated, all search results can be selected at once. If you do not want to filter the results, you can create a data view and use that as the search source instead. Then add the message action and point it to the original layer as the action data. Please let me know if you have other questions. Regards, Shengdi ... View more

The trigger "Data filtering changes" supports selecting or filtering data records from the Feb 2026 AGOL release. ... View more

This feature is supported in the latest Feb 2026 AGOL release. ... View more

Hi @cboyerTucson , 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 ... View more

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 ... View more