Hi,
I am not sure if it is a bug but I was going through and cleaning up our map services on our 10.1 server. Under "Capabilities" I was unchecking Data. This should only prevent someone from being able to modify the Data. But, in our Flexviewer 3.2 app using the 3.2 api, clicking on the map resulted in no popups after the change. I went back and allowed the Data capability and the popups once again showed up. In our Javascript app the popups worked whether Data was checked or not, which is how it should be. Query is the only thing that should affect a popup right? Anyone else experience this and is this fixed if I use the new api? Is the new api compatible with the 3.2 version of flexviewer?
Thanks,
Luci
I am not sure if it is a bug but I was going through and cleaning up our map services on our 10.1 server. Under "Capabilities" I was unchecking Data. This should only prevent someone from being able to modify the Data. But, in our Flexviewer 3.2 app using the 3.2 api, clicking on the map resulted in no popups after the change. I went back and allowed the Data capability and the popups once again showed up. In our Javascript app the popups worked whether Data was checked or not, which is how it should be. Query is the only thing that should affect a popup right? Anyone else experience this and is this fixed if I use the new api? Is the new api compatible with the 3.2 version of flexviewer?
Thanks,
Luci