Save Data Added From Add Data Widget For Future Map Sessions

07-27-2017 07:52 AM
Status: Open
New Contributor II

Data added to the Online Map through the Add Data Widget gets cleared out every time a new session is opened.  It would be nice for this customization to be saved for future sessions similar to the way Bookmarks are saved.  This way, users will not have to customize their web maps every time they visit the site.


I really need this functionality to be added to one of the COTS widgets please, as the current UX is not good for our users.  They would be more open to using the Add Data widget, if they could 'save' the layers they have added via the Add Data widget along with their current visibility settings in the Layers List (for re-use) later on.  At present, our GIS team need to create and support multiple targeted web apps because of this limitation, as the organisation has over 2,000 GIS layers that are of use to various groups,  It'd be great to get this request escalated and into the future road map for Esri to develop please.

Nice to have functions that we'd also love to have included with this enhancement are:

- enabling WAB admins to configure admin 'workspaces / custom sessions' (as well as user level ones)

- enabling users to save and share their 'workspaces / custom sessions' with others

- enabling users to save and restore any graphics that had been added to the map using the Draw widget when they saved their 'workspace / custom session'

by MVP Regular Contributor

This makes sense when your web app covers a wide audience base and you only provide the common tools and data in the web app with the assumption that the users will add their own data... It makes it easy for the developer but for the users, it's annoying that they have to add the same data every time they fire up the application ! Some users have to keep their application alive for days which annoys the ICT people in the department 


Also data added via the Add Data widget does not seem to save when you share a link that remembers layer visibility, which is frustrating