"Use URL Parameter" to make visible Layers

[deleted-user-CQZbjNeBXm49]

Hi all,

Please as anyone been able to use the instruction here "Use URL parameters" to make visible certain layers with their maps (dev: On-premise server deployment)? kindly guide someone in need.

Baba

[BBulla]

OK.  I think I understand now.  Each one has it's own specific parameters.  

Thanks for your help.

[deleted-user-CQZbjNeBXm49]

B,

I have spoken to the tech support from ESRI on this and they informed me that for a WAB Dev, the parameter to use will be the "?config=", where you had need to create new main config_name.json that will be referencing a new web map also or LocalLayer_config. See discussion here https://community.esri.com/thread/181279

Baba

[Mehretab]

It is a good workaround though it requires you to create webmaps and associated config files for each use case (the number of operational layers you need to show in individual URL )

It would have been great if the URL to services (operational layers) works directly like in the portal viewer.

Robert Scheitlin, GISP, I wonder what is the dataSource object in the config.json all about? there is a url parameter and is indicating some sort of Layers...

Mehretab

[RobertScheitlin__GISP]

Mehretab,

  Datasources are layer that are added to the application but NOT the map. They are available to widgets that use datasources like the infographic widget.

[Mehretab]

Thanks as always Robert.

cheers!!!  

[RyanDavison]

If anyone is still interested in turning layers on and off using url parameters and you're using the WAB developer edition, I've modified the url parameter handler module so you can toggle layers and sub layers on and off. I needed this functionality in an app I built and couldn't find a solution anywhere else. I posted about how to use it at https://ryandavison.net/toggle-layer-visibility-using-url-parameters-in-web-app-builder-developer-ed... . There's a link at the bottom of the post to the updated module on Github.