Latest Contributions by LindseyStone

I think ESRI overthought the Basemap Gallery Widget and showing the default Basemap in the Widget.  Currently the Basemap Gallery widget automatically displays the default Basemap that was saved in the Web Map no matter which Basemap Settings was selected. The problem I have is if I have Synchronize with the Basemap Gallery setting of your organization.  Then I have the same basemap twice.  For example if I have my map set to my 2025 aerials it shows that as the first selection in the Widget.  But my 2025 Aerials is also in my Basemap Gallery.  So now that basemap is listed twice.  In addition the first listing which is the Maps default Basemap shows just a small display of the map and not the actual Basemap Thumbnail that was set for it. The workaround I have found is I could set the Widget settings to configure Custom Basemaps and only choose the ones out of my Gallery, except for the default Basemap of the Map so there is not two listed.  Then to fix the thumbnail issue is a set the Thumbnail of the Web Map to the same as the Basemap. I don't think is a viable solution for the below reasons. I prefer for it to sync to the Gallery so if I add a new Basemap to the Gallery (say we fly new aerials and create a new basemap, I want it automatically load into all applications),  instead with Custom Basemaps selected I would have to go one by one to each of my Experience Builder applications and add it as another Custom Basemap to show.  I have a LOT of Applications and that would be time consuming and I could potentially miss one. I also have a few web maps that are being utilized in both an Experience Builder applications and in Field Maps.  If I set the thumbnail of the web map to the Basemap thumbnail so it shows "pretty" in Experience Builder then this is the same thumbnail that is being displayed in Field Maps, making it incredibly confusing for the end user.  For example my 2025 Aerial Basemap Thumbnail says 2025 Aerials over the Aerials.  So in Field Maps they would see that thumbnail next to the Words Water Network Map. We had similar issues via Web Map Viewer Classic and WebAppBuilder where it would duplicate the web map's basemap with the Gallery Basemaps.  The solution was if the Basemap was named exactly the same way as the Actual Basemap in the Gallery it would ignore the default basemap and don't show duplication.   I would be fine with a workaround like that if it worked,  otherwise there needs to be an option within the Basemap Gallery Widget settings to ignore default basemap so it doesn't show.  I saw on one post it is always shown so the end user can go back to the original basemap and that makes sense.  But how many of us is using custom basemaps in the majority of our applications that aren't in our gallery.  So giving us an option to check would take care of both sides of ones that are custom and ones that are just a gallery basemap. Picture of how I have mine set up with an appropriate Thumbnail for the Webmap for my Field Maps User but still showing a duplicate in the Experience Builder Widget.  Again Not Ideal. A couple other posts on this same issue in the Questions Section. https://community.esri.com/t5/arcgis-experience-builder-questions/basemap-widget-in-new-experience-builder/m-p/1598321#M18070 https://community.esri.com/t5/arcgis-experience-builder-questions/basemap-gallery-items-duplicated-how-to-remove-one/m-p/1473943     ... View more

With recent release of Enterprise and ArcGIS Online the Search,  Map Layers, and Table Widgets are now compatible with Subtype Group Layers.  I suggest that the Print Widget also be compatible with Subtype Group Layers.  Currently if I have a map that contains these Subtype Group Layers the print fails.  Many of my maps are information that contain Utility Networks that best load with Subtype Group Layers.  My end users sometimes will put up an area that shows where the utilities and then Print it via the Print Widget to be used as an exhibit attachment to a document or sending information to others.  At least that is what they did in WebApp Builder.  By not having the Print widget compatible with Group Subtypes,  then these types of maps I can't utilize the Print widget making my new Experience Builder Applications with less options than my old WebAppBuilder Applications. ... View more

The ability to Filter not only one field but multiple fields in Field Maps is a very helpful addition to the App.  However,  I think it would be nice to be able to have a setting to adjust the order of the field list in the Filter Window.  To me it appears that the field order in the Filter Window is based on the order the fields were created in the dataset, which sometimes doesn't make sense or helpful to the end user. I recommend that in the Layer Filter settings where you select Off, Selected Feature Layers and Fields, or All Features and Fields that there is few more options.  First option where you can check "Honor Form Order" and it is in the order that you set up the Form.  Second option is where you could drag and reorder the fields in the layer Filter settings.  This would be useful in the case where if the end user filters on the same set of fields all the time, then you could drag them to the top so they are not scrolling for them, but still giving them the option to filter on the other fields if they need to. ... View more

I'm on Enterprise 11.3 and trying to convert some of my map from WebApp Builder to Experience Builder and running into a lot of compatibility issues.   First I had my maps that I published to my Portal 11.3 as Map image Layers set up with Subtype Layers.  However, when doing this I noticed that the Map Layers widget, Search widget, and Table widget doesn't recognize anything within a Subtype Layer.  So I tired another map, and have a Group Layers created in my Pro Project, then added individual layers with filters that represents each subtype.  Now when I try this in Experience Builder, the above widgets work,  but NOW it doesn't show my legend.  But it shows the legend in the Subtype layers. What are we expected to do if Subtype layers don't work with all widgets and Grouped Layers don't work with all widgets.  Are we to have no grouping whatsoever in order for Experience Builder to work correctly? Has anyone else seen this,  or know when this is going to change.  Is there a table or documentation of what each widget that works with subtypes or group layers? ... View more