Latest Contributions by BrianFausel

Hi @Jianxia , I will continue to monitor the situation but I have not encountered the problem in the last few weeks. All of the web browsers seem to be working -- including Chrome and at 2 different offices. The popups are working fine and clearing of cache has not been necessary. If I see it happen again I will open the support ticket. Thanks! ... View more

Looks like the sample shown at this link references www.arcgis.com so perhaps it will be worth investigating. https://developers.arcgis.com/arcade/function-reference/portal_functions/ var features = FeatureSetByPortalItem( Portal('https://www.arcgis.com'), '7b1fb95ab77f40bf8aa09c8b59045449', ... View more

Thanks @Ke_Xu , I'll monitor this thread for updates. The popup issue has been sporadic since this original post and so far only affects Google Chrome for me. I cleared my cache once a few weeks ago and then the popups worked again. Then I saw them stop working on a later day but then most other days it has been working fine. Today they are working as well. So far I only had to clear the cache one time two weeks ago. As far as changing the Arcade script to www.arcgis.com -- I'm not sure if that will work for me but I can investigate it if the problem resurfaces. In my maps the Arcade popups reside in the hosted feature layer's visualization tab and the web map has the layer set as "All properties are stored in the source layer" (i.e. not in the web map itself). Then I use the FeatureSetByPortalItem to call other tables from the hosted feature layer using Arcade.  I'd have to test to see if www.arcgis.com can take the place of how the code is currently set up: var tbl = FeatureSetByPortalItem( Portal('https://{organization_name}.maps.arcgis.com/'), '{portal_item_guid}',   ... View more

@Jianxia I saw this same issue today in all of my Experience Builder apps. As Jordan mentioned I cleared the cache in Google Chrome and the popups then worked. Also, they appear to work fine in Edge and Firefox. Here are 2 public ExB apps that had the problem: https://experience.arcgis.com/experience/5a9316203c744ada97ec5054b26f9e0f https://experience.arcgis.com/experience/96455f2b215b4d5c8bb4b2052375626a All you would need to do to reproduce is zoom in and click on any parcel.     ... View more

So far the updated labeling has been good for my apps. Thanks for adding the enhancement, was worth the wait! ... View more

Hoping for perhaps Fall 2025 AGOL update? ... View more

This will be great! Hopefully in the fall update of AGOL? ... View more

Sorry about the delayed response. Today I figured out why my indexes were not able to be created. I forgot I had a "test" joined view layer set up referencing the original layer where I was trying to create the indexes. Once that joined view was gone the indexes worked again. ... View more

I just tried creating attribute and full text indexes on a test layer and it also appears that I cannot create them either. After selecting some fields and then clicking "Create index" sometimes I saw a red error "unable to create index." Sometimes I've even seen green "success." Other times I did not see any message. In all cases, after refreshing the settings page the indexes do not exist. I don't have time to contact support today but will need to do this in the near future. In my case it is happening on a hosted feature layer in ArcGIS Online that is shared publicly. Editing is not enabled, it is read only. It was created from ArcGIS Pro publishing to ArcGIS Online. If anyone else has the problem I'd be curious to see how you created your hosted feature layer. I also have an identical legacy feature layer that was indexed before the ArcGIS Online update and that one is still working fine. The attribute and full text indexes are the same as they were before the update. I am worried that if I try to re-create the indexes on that version there will be a problem. ... View more

Awesome, looking forward to it! ... View more

Hi @ShengdiZhang I checked the single letter search again and it looks like it works as you describe in Experience Builder and not in Web AppBuilder. Because we are moving forward with all ExB apps that fix will be good for us. Also, in the cases of the old WAB apps our users have the workaround of not including the direction and then the search still works for them. Thanks, Brian   ... View more

It is possible to upgrade enterprise and file geodatabases, though it would be to whatever Enterprise equivalent that Pro 3.3 is (looks like Enterprise 11.3). I would think a geodatabase created in 11.x will not work in ArcMap. If the geodatabase was not upgraded, I have had issues opening layers in ArcMap if you set up newer Pro-related functionality (attribute rules, for instance). Once you remove the advanced functionality then the layer works in ArcMap again. ... View more

I recently asked the Esri AI Chatbot (in Support app) about the single-character string search problem. It's answer was that the search "doesn't recognize incomplete or single characters as valid search terms." Not sure where the AI sources that but it was an interesting response. ... View more

I recently asked the Esri AI Chatbot (in Support app) about the single-character string search problem. It's answer was that the search "doesn't recognize incomplete or single characters as valid search terms." Not sure where the AI sources that but it was an interesting response. ... View more

I have seen this same searching issue with single characters in a text field. I'll be curious to see if this is confirmed to be a bug. In my case it happens across all Esri apps I use (Web App, Experience, Instant) and the searching layer is hosted in ArcGIS Online. I can't say if the problem also happens with an Enterprise-sourced layer. There are only 2 workarounds I know of. Unfortunately I don't think either of these will work for you: 1) Tell the users to include other parts of the intended search result. In your case I don't think that will work given your lot strings. In my case the problem is a direction letter abbreviation in between address number and street (entering "3805 s casper" does NOT produce results, "3805 casper" does). So I have been able to live with the issue for now... 2) The problem seems to be created when you set up a full text index on the AGOL hosted feature layer. I have found that if you delete the full text index, now the search will work assuming the user enters the exact string. They will even be prompted with the candidate suggestions. This might work for you with the lot field. However, by eliminating the index you loose the enhanced searching. Also, when you configure a new search in the Esri apps (ExB, Instant) a new full text index will be created automatically by AGOL when one does not exist on the layer field. ... View more