Latest Contributions by TonghuiMing

@GarySchells Customization of fonts and colors for widgets is now supported in the latest AGOL Oct release (new theme settings). ... View more

This has been supported in the latest AGOL 2025 Oct release, and the searched layer will be automatically expanded if inside a group. ... View more

This has been supported with the ExB's new themes in the recent AGOL 2025 Oct release. ... View more

@EMiller_2 The original issue is resolved in the latest AGOL Oct update. Let us know if you still encounter any problems. Thanks. ... View more

Hello @Tiff  Sorry for the delay - things have been hectic for the past weeks. I've checked your app, and here are my findings: - When I tab through the elements, #5 is actually the focus of the outer section view: - #8 is the inner section view And yes, setting the padding will expose the focus ring (this was suggested inside the doc and blog). Glad it works out.   For the problematic #9, yes, we've noticed it in some cases too - somehow the rich text (text widget) grabs an extra focus, and it shouldn't - if there is no link configured inside. This is something we need to investigate further. I will create an issue, and feel free to create a support ticket if you need to track the progress. Make sure to pinpoint it as about the Text widget (there are some different cases regarding hidden focus, and most of them are not from the same reason - I will need to further check the reason): Hope it helps, thank you. Tonghui ... View more

It would be helpful to provide the sample app for us to check. ... View more

@JeffreyROLAND Whether the zoom feature displays depends on your web map or layer's setting for the minimum time accuracy, as well as the time step setting. See my example of min time accuracy = 1mon, step = 2mon, full extent=2 years, the zoom buttons display as expected: This needs to be adjusted by your time-related settings. I am unable to reproduce it on AGOL.   However, if you did not change the app settings or web map/layer settings, and the app upgrades with this change, it would be helpful to provide the sample app for us to take a look. ... View more

Hi @BrandonGuo, thanks for sharing. I can see what you saw in this app. Some notes -  We can access one layer but not the map, which seems to belong to your org We've found some unexpected mismatch between your app configuration UI vs. the app config - not sure how this comes up, we will take some time to debug. Very weird Then, just to confirm - when you publish the layer and enable the time extent, have you checked the following box saying "Data is a live feed", and then add an interval to refresh and update the feature? The reason I ask is that your data did get updated to 9/5, but in your service, the extent does not pick up the latest changes:   Tonghui ... View more

Hi @BrandonGuo - sorry to hear that. Do you have the sample app with data that we could take a closer look at? ... View more

Hi @AveryBick  Thanks for the information. This workflow rarely occurred in our previous user feedback. I did some testing, and it seems like you can only generate something on the fly inside the Map Viewer, based on style customizations - but not saved to the map, which is ready for other applications to use.   Here is when you publish a time-aware layer, using ArcGIS Pro, what the configuration and the layer property look like - notice that it successfully contains a valid time info     See that when I tried checking the layer property outside MV from your data, there is no time info to be found:   Thus, what I suspect is that - Through this particular doc workflow, you might be able to create a new feature collection, time-aware, inside MV, which can only be used inside the Map Viewer. It does not update the layer property, and that's why ExB cannot obtain any time info to be used for the Timeline widget.   You might want to publish the layer/map from Pro using the previous configurations, if possible. ... View more

Hi @RakeshKumar, thanks for sharing the detailed document! It helps us with the quick identification of the issue. This lies in - while this widget uses the API widget, the default core behavior is to always show the legend not only for each layer, but also at the group level, without an option to disable them. This does look confusing, and I will add your case to the issue. We will reach out and see if we can get this enhanced. I believe that if the first-level/group-level legend can be disabled, then your case can be achieved. A similar scenario - https://community.esri.com/t5/arcgis-experience-builder-questions/layer-list-contains-duplicate-and-redundant-legend/m-p/1305005#M7495    Thanks for bringing this up. ... View more

@Teri_Dane I tried your workflow and it works fine - custom SQL inside List widget > filter tool, when it is applied, the map zooms as expected:   The second part you described is a bit confusing to me.   The data filtering changes message is in this flow: Data filtering changes (filtering as the message) > Map zoom/pan (map extent change as action) As for the framework-level, it is: Data record selection (selection as the message) > flash or filter based on the selection (action)   If there is another filter, then it would be when a filter happens (message), then another filter happens following that (action). This does not make much sense to me.   Could you provide more information about what you observe and what you want to achieve, with a sample app? Looks like a bug or configuration issue based on the current information.   Thanks, ... View more

@JonathanHall3, could you provide some screenshots or a sketch for illustrations? ... View more

@Tiff, if Nicole's detailed comment above still does not solve your case, it might be helpful if there were a sample app that could be shared. ... View more