Basemap Gallery widget not displaying correct custom basemap options

02-22-2018 09:32 AM
Occasional Contributor II

I'm experiencing odd behavior in the Web AppBuilder Basemap Gallery widget. Here is a breakdown of the situation.


  • The ArcGIS Online organization has a group setup that contains the Esri vector basemaps (web maps).
  • This group's web maps (the vector basemaps) are configured to show in the organization's Basemap Gallery (done through Organization > Edit Settings > Map > Basemap Gallery setting).
  • A web map was created that uses the Topographic map by Esri as the basemap (Item ID = 588f0e0acc514c11bc7c898fed9fc651).
  • The web map was shared to create a Web AppBuilder app, and the Basemap Gallery widget was configured with the option to "Configure custom basemaps".
  • Five of the web maps (basemaps) were imported from the "Organization default", and the Basemap Gallery widget configuration was saved.
  • ISSUE: When opening the Basemap Gallery widget, six basemap options appear. In the screenshot below, none of the options have been chosen yet. The map is still displaying the basemap setup in the web map.

  • ISSUE: When the Topographic basemap option is selected, the map displays what appears to be the basemaps hillshade layer but not the reference layer.

  • ISSUE: When the second Topographic options is selected (the one I do not believe should be there because it is displaying the thumbnail for the web map being used in this app), the map displays what appears to be the correct basemap.

I have configured this widget many times before, and have observed this behavior only recently, and in one other Web AppBuilder app that I've configured. Below is the Basemap Gallery widget configuration used.

Have any others discovered this behavior? What can be done to fix the configuration of the app (or the web map basemap or the organization basemap group)? Am I overlooking a piece involved in this? Is this a bug introduced in a recent update to Web AppBuilder, and if so, is there a workaround and will the issue be resolved in an upcoming update?

I've included URLs to the content below.


This is not an urgent issue, but more of a nuisance. It will be helpful to know if there is currently a workaround or resolution to it.


Thanks Community!



15 Replies
MVP Emeritus


   I have seen this before when using a non-default esri basemap in your web map. The basemap gallery tries to add your web maps basemap it does not see it as a standard esri basemap and then it does not get selected in the gallery but is added and at times adds something that is a duplicate of another basemap. It seems to be an error that needs to be reported.

Occasional Contributor

I am also having the same issues with organizational basemaps.  They show up in the web maps but are not available in the Web Appbuilder basemap widget.

MVP Emeritus


  You should call esri tech support and file a bug on this.

Occasional Contributor III

Mike, we are experiencing the same issue where a custom basemap is added to the Basemap Gallery selector and available in a Web Map but not available when you bring that Web Map into a Web App. We think it might be do to projections but we have the custom basemap defined with the identical projections as the Esri basemaps. Did you find a solution or identify a bug? We have not put in a ticket with Esri yet but believe that might be the best course.

Occasional Contributor

I have been working with tech support and identified it as a bug.  BUG-000113736  It has been marked as "In Production Plan".   The bug that has been identified with my case relates to the services requiring tokens as cached services on ArcGIS Server and then saving credentials for the services on ArcGIS Online.  

All of my custom base maps in my base map group set as the organizational default show up and work in all Web Maps but do not all show up in the Web Apps.  My issue is that only one custom basemap shows up in the Web App and through testing it is the one that is selected as current in the Web Map that is in the Web App.  All other custom base maps do not show up.  If I switch the custom base map in the Web Map, that new custom basemap will show up in the Web App but not the others or the one that previously was available.   All custom basemaps have the same projection and caching schemes.  I also demonstrated this to ESRI tech support and they recreated the problem and it has to do with the custom basemaps requiring tokens.

There is no current workaround for this issue if you use secure services from ArcGIS Server.  If you are having the same issue I would contact ESRI support so they see it is impacting more people.

Frequent Contributor

Hello all - I would say this issue has cropped up again.  I just upgraded to Enterprise 10.7.1 on Saturday August 17, 2019.  Our custom basemap gallery has living atlas content (Human Geograpy) coming from a send-recieve collaboration group pair between portal and agol.

When signed into either org or portal, my custom basemaps appear in the basemap gallery widget in my 2.11 and 2.12 wabs.  If not signed in, the basemap gallery in the wabs bounces to the default esri basemaps.

Frequent Contributor

Hi again -  has anyone seen a resolution to this?  Because we have living atlas basemaps configured as part of our basemap gallery.  This has become an even greater issue when using the 3D Wab because there is no configuration for the 3D basemap gallery widget.  In 2D, I can at least configure and hard code in our Enterprises' basemaps from our basemap gallery, but cannot do so in 3D.  

0 Kudos
Frequent Contributor

An update - this is also an issue in Pro.  Public basemaps in our custom basemap agol group won't load to Pro if those webmaps are Collaborated.  I think that because we do not allow anonymous access to our Portal, that this is what is causing the hiccup for both the WAB and PRO.

If I save a copy of one of my collaborated webmaps, that removes the Collaborated tag (status, icon, whatever).  Then that webmap WILL load to Pro from the basemap ribbon tool.  I'm wondering if Kelly Gerrow‌ has come across this yet?  

0 Kudos
Esri Frequent Contributor

Hi Dave,

Sorry for the late reply and this isn't something I have come across yet, but based on your testing and description, it sounds like a bug. I'll pass this along to the team, but I think it is best to get this logged with tech support so you can track the status of the bug.



0 Kudos