Can anyone tell me if it is possible to have WAB automatically update dynamic services? Right now when we overwrite an existing service with updated features we have to go back into web appbuilder reload the service to get the latest changes. Then we have to rehide layers based on the updated layers in the map (mxd). This breaks the popups configured, layer list, queries, searches, and attribute table (not all the time, randomly). So i simply open locallayer to refresh the latest changes published (rest services). Then i have to go and verify that each of the previously mentioned tools functions correctly in WAB. Then i go to the WAB install directory server->apps-> app number and copy the widget configs for each one over the configuration we are using on our IIS web server. I sure was hoping there was an easier way to have WAB automatically reread the latest changes in the rest services. Any input would be greatly appreciated.robert scheitlin
Solved! Go to Solution.
Hmm... I have to say that my data schema hardly ever changes so I don't run into this issue. Why is your schema changing so often? Normally the data manager sets the fields, domains, etc (Schema) for your data and once that is well established then you start publishing map services that will consume that data and then apps that consume those services. It should be rare for the data schema to change once the service has been published.
So to answer your question though. No there is not an easier way for this to occur.
We have over 100+ sites published to 8 AGS's. The sites that are hosting SDE and/or Geodatservices never change. We simply load data and use definition queries to limit feature layers. For this it works perfectly. As for the line of work, we are an engineering service company and have many GIS Specialists updating/managing sites throughout the organization. Our engineers and project managers will ask during meetings to update the viewer with new data from KMZ or CAD files (expected turnaround 10-20 minutes). We have really spoiled these guys and they demand instant access. The short version is that this data is converted and added to the service, thus causing all these problems. And really, it's not a huge problem, it's an easy fix. It just causes a lot of extra work for myself and our GIS developer as we have limited access (for other GIS users) to such tools and we have to be the ones responsible for fixing these issues. It would be a fantastic option to have LocalLayer reread the dynamic rest service and mimic the service. The service rarely ever matches what was published in the MXD (Hide Layers, etc.) I can easily open LL and let it reread the service and then copy and paste the "hide layers" in the locallayer for the app in WAB and then paste those into the live site fixing the problem. I was just hoping this was already an option that i was overlooking.