Latest Contributions by TonghuiMing

The problem with grouped raster/imagery layers should be fixed with today's AGOL 10.1 upgrade. Please check again. Thanks. ... View more

@BigLouC Since usually, the responsive limit depends on the screen resolution (a certain px value), there could be different behaviors, especially when users have varied devices. There is a similar support issue, BUG-000146629 - they have trouble showing the designed responsive portrait interface in landscape mode. ... View more

Hi, I cannot find any information about support case '02965357'. Is there a 'BUG-xxxxxxxxx' number that I can refer to?   Here is one that I mentioned earlier that fix this in AGOL 9.3: BUG-000136230 ... View more

It would be expected in Enterprise 10.9.1 since we fixed the bug after that release, but dev 1.7 should work fine. Is it possible to share the map data that you are using? Thanks. ... View more

Hi Ashok, we are still trying to locate the issue but have not yet successfully reproduced it. Are you still using Enterprise 10.6.1? Notice that we fixed the previous issue (ExperienceBuilder Online Error: s.getCurrentQueryParams is not a function) in 9.3/AGOL 2021 Oct release/Dev 1.6, while 10.9.1 Enterprise is equivalent to Dev 1.5 code - see https://developers.arcgis.com/experience-builder/guide/about-versions/ for a reference - which means, only the next upcoming enterprise version will pick up on that fix. I have tried several data reported by users earlier, which contains grouped tiled layers in the latest prod environment (same as dev 1.7), and it works fine too... ... View more

@DaveKazemi It does happen in the ExB map widget and the altered points are somehow missing. We will take a look at it and see what is going wrong here. ... View more

@RhettZufelt - after investigation, here are some complications to your case - If the values are just labels, then there could be a way to sort them naturally, such as the following case: However, it is values that are being used for Filter > SQL in your case, thus, it may be the current designed behavior - since it says string field value by the starting 'W', it could not use the numeric logics, which will honor the natural sort order. A workaround might be, to use 01 to distinguish 10+ numbers. Hope it could help. ... View more

@giladuzann @DanPatterson - This issue should have been fixed and the selection change will take effect. Could you please double-check? Thanks.   ... View more

@sroberts_uuF21 I see. Thanks for clarifying it. We will take a look. ... View more

@sroberts_uuF21 In ExB, you could try the following steps inside the Map Layers widget:   ... View more

@RhettZufelt It appears to be the current sorting mechanism and we will take a look at it to see if it can be enhanced. Thanks for bringing it up. ... View more

@hijivir Have you tried the Data action > Show on map feature (Data action for ExB ) for your Query widget? It is designed to highlight features of your query results on the map for display purposes. I am getting a little confused about the query & map structure you have. You mentioned it is shapefile, but I assume you added the data into ExB as a Web Map, and prior to that it should have been published as a feature layer or other acceptable data format? If so, then there should not be any different from using a feature layer directly. ... View more

Hi @Anonymous User - this is an issue that we know of and there is also a Support issue (BUG-000141100) open. We will take a look at it. ... View more

@SBerg_VHB @RhettZufelt Yes, this is something on our radar and we are targeting to fix it soon. Thanks for bringing it up. ... View more

If that's the case, is it possible to provide their problematic browser (FF) versions as well? ... View more