Latest Contributions by BrianFausel

‎02-22-2024

One thing to check if you haven't already is to make sure the layer IDs in the Pro publishing document are consistent. In the Map Properties - General there is a setting to "Allow assignment of unique numeric IDs for sharing web layers". With that checked on you can now manually control the IDs for each of the layers in their General Properties. Look for the "Layer ID" setting. When published the IDs you set for the layers in Pro will appear to the right of the layer name in REST: If you don't control this setting the layers will be ID-ed automatically by Pro. I would think each GP output would result in a different ID number. I've overwritten many services and generally if you keep the layer IDs consistent they will work. Though I haven't done a ton of this with the dashboards so perhaps there is something odd with them. In my experience an overwrite does not change the Service Item ID used within AGOL. As mentioned schema changes are another story!

‎11-28-2023

This sounds like a similar issue I had with attribute and text indexes with a hosted feature service and Experience Builder hosted on AGOL. My searching details can be seen in this thread. In summary it came down to a bug in Experience Builder as I did not have similar issues in Web AppBuilder. It was logged as ENH-000163068 if you want to refer to it. • Synopsis: Experience Builder Search Widget does not honor the Feature layer's Full Text Field Indexes • Status: In Review

‎11-21-2023

I have confirmed with Esri Support that this appears to be a bug in Experience Builder. It was logged as ENH-000163068 if you want to refer to it. • Synopsis: Experience Builder Search Widget does not honor the Feature layer's Full Text Field Indexes • Status: In Review Below is a summary of what I saw while searching for variations of an address string in a text attribute in Experience Builder (ExB) and Web AppBuilder (WAB). In my case the apps and data are all hosted in ArcGIS Online. I haven't done any testing with anything coming from Enterprise. The example address I am searching is stored in the text attribute as "3805 s casper dr" (address number, direction abbreviation, street name, suffix abbreviation). "3805" (left-side start of the string) returns a proper candidate list in all ExB and WAB apps. "casper" (street name in middle of string) returns an appropriate candidate list in WAB (with layer index) and ExB (with layer index). The recent AGOL update causes this search to return NO results in ExB (no index on layer). "3805 s" (direction included) returns partial results in WAB (with index) - 2 of 4 (?), NO results in ExB (with index) and all available candidates in ExB (no index). "3805 casper" (direction left out) returns correct result in WAB (with index) and NO results in ExB (with index) or ExB (no index). I have only tested address-like text strings but would guess there might be a problem with other types of text. In my case the workaround will be to eliminate all text indexes on the feature service. This at least allows my users to enter "3805 s casper" to get results they have been used to seeing.

‎11-07-2023

I have opened a support ticket. In the meantime I tested the searching in the web map JSAPI search as you suggested. I saw the same results you did where the index search appears to work. Interestingly I also tested it in a WebAppBuilder app that also worked the same as the web map. A side-question I have is about the candidate list that appears if a user enters the direction "s" when using the web map JSAPI search. In this example if I just type "3805" I see 4 candidates (which is correct): If I type "3805 s" then I only see 2 candidates and note that they are ones with words that start with "s" later in the string: And finally if I type "3805 casper" it finds the correct one. This is actually the ideal behavior and what I would expect from a full text index. But I am still curious why "3805 s" does not show 4 candidates.

‎11-06-2023

Thanks Russ. I'll investigate the Map Viewer search you mentioned and will definitely contact support to either create a ticket or see if there is one already. Will post any updates I find.

‎11-03-2023

Since the October ArcGIS Online (AGOL) update I have had problems with attribute-based text searching in Experience Builder (EB). All of the items I am dealing with are hosted in ArcGIS Online, including the application and layers. In these examples there are no items coming from Enterprise. Problematic item My Search bar widget in EB is set up to search a text attribute in an hosted feature layer. Problem can also be seen in other Esri apps but I am specifically working with EB in this case. Problem Description I have an AGOL-hosted feature layer with a full-text index defined on an attribute and as a result certain types of searches do not work in EB. Alternatively, if I have a similar but separate feature layer with NO indexes the EB search works as expected. This is the opposite way I would think it would work. I have 2 public EB apps below that demonstrate the issue. In both try searching for the address string "3805 s casper" EB app without indexes EB app with full text index set up In both apps if you type only "3805" you'll see the desired result appear in the candidate list. But if you start typing "3805 s" the results will work properly in the app without the index but will NOT work in the one with the full text index. In this case typing "3805 s" says "no results." The problem has something to do with the search widget breaking change mentioned in the EB blog, as I did not encounter it before the update. I have also read the Searching for Features blog from last November and have not been able to come up with a solution other than to eliminate all attribute indexes. Reading this blog suggests that even a search like "3805 casper" (leaving out the direction "s") should return a proper result when indexes are created. Is anyone else having a similar problem? @RussRoberts

‎09-12-2023

Thumbs up to this idea...especially in the Text widget!

‎09-12-2023

Hi @RussRoberts, we also have a zoning + future land use app example being developed in Experience Builder with the new web map behind the scenes. In our app we are hoping to see an update where the label of the future land use and zoning always appears on screen no matter what zoom scale the user is at. Does the forthcoming update include this? On the map below when you zoom in you'll notice that the purple future land use labels appear static in the centroid, and if the user is not looking at the centroid the label does not appear. Admittedly another issue impacting the display are the address number labels at some scales. But if you zoom in really close to a parcel view the future land use label rarely appears even though there is room for it. Here is a link to the app that is in development: https://experience.arcgis.com/experience/195f09675702436ab78b6cc033c72e07/page/Public-Map-Viewer/?views=Future-Land-Use And the web map: https://newberlin.maps.arcgis.com/apps/mapviewer/index.html?webmap=24fb98cab5564be7b3faab2543cdb3e8 Thanks!

‎01-31-2023

Unfortunately I don't have a solution but I can report the problems I am seeing with the AGOL-version of the Web AppBuilder print widget. Perhaps this can help you troubleshoot. - When the web map includes map services that are hosted by external organizations I see the same error as you. If I turn those external map services OFF the printing works. In your case, it might be related to the source of the layer(s) in your map. Note that there are other threads that mention TLS/SSL Certificates as a potential source of the problem. - Previously I was able to print using the "Advanced -> change Output spatial reference" to something other than default 102100 (WGS84 WM Aux Sphere). Now I see a similar error if I try to change the spatial reference when including tiled imagery services. Since our WAB is hosted in AGOL I am suspecting an update might have broken this. In your case, if you are changing the spatial reference perhaps that is causing the error. - I tried all 3 major browsers with similar results (Chrome, FF, Edge). In either case it is odd that it was working and now not, given you are working in the Enterprise WAB where you control the updates.

‎07-19-2022

Huge thumbs-up to this idea! Being able to share Arcade expressions across the whole AGOL organization would be ideal. But even the minor step of accessing / sharing expressions across layers within a feature service would be helpful.

‎05-25-2022

This solution worked for me. Anyone still trapped on Collector should try adding directly from "Add Layer from Web - Service URL."

‎05-03-2022

If your alternate versions are limited to what layers are turned ON by default you can use the Share Widget in WAB and selecting the link option "Remember layer visibility." This can generate a unique link that can re-create the current visible layers and zoom location. We have used this technique to have a single app that starts with a zoning background in one version and an aerial in another. Looking at the Esri doc note that there are potential issues if lots of layers are involved, as there are certain limitations on URL length. If your alternate versions involve different tools or other configurations across multiple apps we'll have to see if anyone else has any tips.

‎04-26-2022

Ok cool, thanks for the clarification!

‎04-26-2022

I use FME to load tables from external SQL databases to our Enterprise geodatabase (SDE) and also ArcGIS Online. It can definitely do what you are looking for either through truncate-append or change detection updates. There is a bit of a learning curve to FME but they do offer quite a bit of free training and on-demand webinars. My update processes are created in FME Desktop and then scheduled to run nightly/weekly/on-demand via Windows Task Scheduler. Your original post does mention "live," which suggests you might need to see changes instantly. If that is the case, you'd likely need to use FME Server or Cloud along with FME Desktop, which will add more to your purchase cost if you decide to use FME.

‎04-05-2022

Out of curiosity, when you mention "list vs gallery," are you referring to the dashboard elements? The dashboard editor functionality where you click the "plus" icon (top-right) and select "List" or "Details"? And the attachments are not working in "Details" but still work in "List" (unless using hosted feature layers)? If true that is definitely a downgrade 😞 We're about to do an Enterprise upgrade to 10.9.1 and use attachments mainly in the "List" element. I'm hoping the problem you describe is not impacting that.

Online Status	Offline
Date Last Visited	‎03-10-2026 10:37 AM

My Ideas

Latest Contributions by BrianFausel

Re: ArcGIS Dashboards- Overwrite publish from Pro breaks dashboard elements

Re: Multiple things stopped working in the Search widget in last update

Re: Full-text search index on hosted feature layer attribute doesn't appear to be working properly in EB (AGOL-hosted version)

Re: Full-text search index on hosted feature layer attribute doesn't appear to be working properly in EB (AGOL-hosted version)

Re: Full-text search index on hosted feature layer attribute doesn't appear to be working properly in EB (AGOL-hosted version)

Full-text search index on hosted feature layer attribute doesn't appear to be working properly in EB (AGOL-hosted version)

Re: Allow Arcade Expressions in Experience Builder

Re: Label Polygons Beyond the Centroid in New Map Viewer

Re: Print widget issues

Re: Share Arcade expressions within AGO org

Re: Unable to Open Map "Invalid call with current token type"

Re: Use config url parameter within the WAB interface (to edit widgets config)

Re: Upgrade Dashboard for Enterprise 10.9.1 to show attachments in Details

Re: Join two SQL Databases and Share the Resulting Layer in Enterprise Portal

Re: Upgrade Dashboard for Enterprise 10.9.1 to show attachments in Details

Re: ArcGIS Dashboards- Overwrite publish from Pro ...

Re: Hosted Feature Layer - Create Index taking hou...

Re: Multiple things stopped working in the Search ...

Full-text search index on hosted feature layer att...

Re: Use config url parameter within the WAB interf...