I wiped out all of the default services that were provided as a sample with the widget. I entered a REST url for a service within a Dynamic Map Service and clicked browse. The widget recognized the REST URL and allowed me to customize the fields. I added settings and reverted to the interface to add more, and noticed the yellow triangle stating that the "Layer not found in the map".
I've used the same REST URLs with the Enhanced Search Widget and they work fine, there are no issues. Any ideas?
There is no requirement to look at the IdentifyWidget.xml for anything, I will just helping you diagnose your issue. What it all boils down to is that you can not use localhost in one place and the machine name in another and have the code understand that both are pointing to the same layer (even though they are). The identify widget checks if the layers that you have configured exist in the map as a base map or operational layer and the means that it does this is by comparing the URLs. The fact that flex is a CaSe sensitive language means that Valhalla and valhalla are NOT equal and thus the widget does not detect that the layer is in the map and obviously the comparison of localhost and valhalla are not equal so same issue. If you have a map service added as an operational layer and its type is dynamic then the widget check if the configured identify layer is a sub layer of that parent map service. So there is the in-depth explanation of what is going on under the hood.
So what are you next steps.
You do need to check into the issue with the fact that you have the web adaptor installed and you still have to use 6080. I would call tech support on this one.
You should start a new configuration of the Identify widget by deleting the old one from the "Widgets in this application" and re-adding it and use "http://valhalla:6080/arcgis/rest/services/WebMap/MapServer" when you browse for layers to add, or if you get number one done then use your new url.
Hi Robert,
Thanks for all the help, I took your advice on item 2 and went through the process methodically with success. I also looked into the Web Adapter issues and am able to connect to my services with the web adapter name and everything now so that is cleared up for me also. Thanks again for helping and developing so much for us to use.
