I feel like this shouldn't be so difficult...
I'm experiencing an interesting (not really, more like frustrating) issue with the Flex Viewer (v3.0) and eSearch Widget (v3.0.16).
Everything was working normally one week ago, but now I'm seeing really strange behavior from the widget and my layers.
I have five layers being used in the eSearch widget. Three polygon and two line feature classes, the data all located in the same geodatabase, and all layers are in one map service. When the map launches, a search parameter is passed through the URL and the map zooms to a specific extent based on that URL parameter. The respective data is highlighted and search results display in the Fixed DG. The problem comes when I try to use the widget gui to search another data layer.
When I use the symbology tags for each layer individually (in the eSearch.xml) I see this behavior...
-From the Search Layer drop-down menu in the gui, layers 1, 2, and 4 all work as expected. When I select a feature from one of the layers in position 1, 2, or 4, I see highlighted spatial data on the map, as well as search results (and related results) in the Fixed DG.
-When a search is performed on the data posted in the 3rd position (doesn't matter which data layer it is), the viewer returns search results in the DG and zooms to the extent but does not highlight the feature on the map.
-The 5th data layer on the list, when searched, highlights the feature in the map but there are no search/relate results returned.
It does not matter which data layer is in any of these list positions, it's always the third layer in the xml that zooms but doesn't highlight, and it's always the 5th, or last, layer in the xml that highlights but does not return search results. I reordered my data layers in the xml to test this.
When I comment out each individual layer symbology tag and use the symbols tags at the end of the eSearch.xml, I see this...
-all layers (1-4) work normally and highlight, zoom, and show search/relate results.
-Layer 5 does nothing. No highlight, no zoom, no search results. Though really what happens is it "highlights", but not with the color that is referenced in the xml. The viewer instead redraws the selected feature on top of all other data layers, but in the same symbology that is referenced in the map service (so it looks like nothing has happened). If I do a search on this last layer, then turn off all the layers, the "selected" feature remains in the map, drawn in the map service color.
All the data layers are good and the services are running. The related tables are there and the relate exists, I can query in REST and get results/relates for all the data layers.
Everything worked as expected with v3.0.14(f) of the widget, but since I've updated (twice) things have gone wacky (I've made no other changes to the project other than updating the eSearch widget). I've tried troubleshooting the solution many different ways.
I have added a clean, unedited eSearch widget (v3.0.16) file into my Flex project (uncompiled version) just in case the problem was in one of the few mxml edits I'd made, but the problem persists. I tried to go back to the version of eSearch (3.0.14f) that I knew worked, but now that doesn't work either. I am at a loss as to what to attempt next. I'd really rather not start from the beginning again, building an entirely new project but I don't know how else to figure out where the problem is. It doesn't make sense to me that it's an API problem, since it's only one or two of the data layers that aren't working right and as I said above, the data isn't the problem, that I can tell. I really don't know what to do.
Does anyone have ANY thoughts or ideas as to where to go from here????? Thanks.
I'm experiencing an interesting (not really, more like frustrating) issue with the Flex Viewer (v3.0) and eSearch Widget (v3.0.16).
Everything was working normally one week ago, but now I'm seeing really strange behavior from the widget and my layers.
I have five layers being used in the eSearch widget. Three polygon and two line feature classes, the data all located in the same geodatabase, and all layers are in one map service. When the map launches, a search parameter is passed through the URL and the map zooms to a specific extent based on that URL parameter. The respective data is highlighted and search results display in the Fixed DG. The problem comes when I try to use the widget gui to search another data layer.
When I use the symbology tags for each layer individually (in the eSearch.xml) I see this behavior...
-From the Search Layer drop-down menu in the gui, layers 1, 2, and 4 all work as expected. When I select a feature from one of the layers in position 1, 2, or 4, I see highlighted spatial data on the map, as well as search results (and related results) in the Fixed DG.
-When a search is performed on the data posted in the 3rd position (doesn't matter which data layer it is), the viewer returns search results in the DG and zooms to the extent but does not highlight the feature on the map.
-The 5th data layer on the list, when searched, highlights the feature in the map but there are no search/relate results returned.
It does not matter which data layer is in any of these list positions, it's always the third layer in the xml that zooms but doesn't highlight, and it's always the 5th, or last, layer in the xml that highlights but does not return search results. I reordered my data layers in the xml to test this.
When I comment out each individual layer symbology tag and use the symbols tags at the end of the eSearch.xml, I see this...
-all layers (1-4) work normally and highlight, zoom, and show search/relate results.
-Layer 5 does nothing. No highlight, no zoom, no search results. Though really what happens is it "highlights", but not with the color that is referenced in the xml. The viewer instead redraws the selected feature on top of all other data layers, but in the same symbology that is referenced in the map service (so it looks like nothing has happened). If I do a search on this last layer, then turn off all the layers, the "selected" feature remains in the map, drawn in the map service color.
All the data layers are good and the services are running. The related tables are there and the relate exists, I can query in REST and get results/relates for all the data layers.
Everything worked as expected with v3.0.14(f) of the widget, but since I've updated (twice) things have gone wacky (I've made no other changes to the project other than updating the eSearch widget). I've tried troubleshooting the solution many different ways.
I have added a clean, unedited eSearch widget (v3.0.16) file into my Flex project (uncompiled version) just in case the problem was in one of the few mxml edits I'd made, but the problem persists. I tried to go back to the version of eSearch (3.0.14f) that I knew worked, but now that doesn't work either. I am at a loss as to what to attempt next. I'd really rather not start from the beginning again, building an entirely new project but I don't know how else to figure out where the problem is. It doesn't make sense to me that it's an API problem, since it's only one or two of the data layers that aren't working right and as I said above, the data isn't the problem, that I can tell. I really don't know what to do.
Does anyone have ANY thoughts or ideas as to where to go from here????? Thanks.