I like the port of the identify widget to take advantage of the Application Builder GUI. I have run into some issues with the widget, the last 2 having to do with the GUI, and the first one, I don't know.
1. I went through all my layers in my 3 services, as I have probably over 150+ total fields that identify uses. I've found a few that simply refuse to identify (I get a blank instead of <null>, even when there is data in that record). With the new GUI, I've removed the fields and added them back in, and there is still nothing. This fixed most, but not all of them (7 still broken).
I verified that the REST field names match the ones in the widget and in the geodatabase. I'm not sure what else would do it. A few of the nonworking ones have subtypes, a few are dates, a few have coded domains, none of them seem to share anything in particular. I've checked and rechecked spellings. One strange thing is that 2 of them that were not working, I changed from using the name to using the alias for the name (had to manually edit the xml), and they started working, but the others did not respond to that. I updated to 10.2 for desktop, but not Server yet, if that matters. This seems to be some kind of issue where the name is not being recognized, or there is some confusion over the name & alias in the actual table vs. the name and alias in the xml.
In essence, many of my fields still use the alias as the name like the widget used to use, and they still work, and others I've had to change to the name to work, while others respond to seemingly nothing at all.
2. I noticed something else: After adding a new layer and associated fields with the new GUI, I find that it adds an extra "/4" at the end of the URL after the /3 that was there already (the real layer ID). So it doesn't work unless I go in manually and delete it in the XML, otherwise it keeps coming back with that /4.
3. And lastly there is the issue of the warning signs on every layer that I have... those yellow triangles with the exclamation point ("layer not found in the map"). I don't know if this is related to anything, but I'd like to get rid of those. Most things work just fine, so they clearly are found in the map...clicking "Remove warning layers" wipes out everything, so that doesn't seem to be working right. My map extent clearly has at least 1 layer visible in the default zoom, but even that layer has the yellow triangle.
1. I went through all my layers in my 3 services, as I have probably over 150+ total fields that identify uses. I've found a few that simply refuse to identify (I get a blank instead of <null>, even when there is data in that record). With the new GUI, I've removed the fields and added them back in, and there is still nothing. This fixed most, but not all of them (7 still broken).
I verified that the REST field names match the ones in the widget and in the geodatabase. I'm not sure what else would do it. A few of the nonworking ones have subtypes, a few are dates, a few have coded domains, none of them seem to share anything in particular. I've checked and rechecked spellings. One strange thing is that 2 of them that were not working, I changed from using the name to using the alias for the name (had to manually edit the xml), and they started working, but the others did not respond to that. I updated to 10.2 for desktop, but not Server yet, if that matters. This seems to be some kind of issue where the name is not being recognized, or there is some confusion over the name & alias in the actual table vs. the name and alias in the xml.
In essence, many of my fields still use the alias as the name like the widget used to use, and they still work, and others I've had to change to the name to work, while others respond to seemingly nothing at all.
2. I noticed something else: After adding a new layer and associated fields with the new GUI, I find that it adds an extra "/4" at the end of the URL after the /3 that was there already (the real layer ID). So it doesn't work unless I go in manually and delete it in the XML, otherwise it keeps coming back with that /4.
3. And lastly there is the issue of the warning signs on every layer that I have... those yellow triangles with the exclamation point ("layer not found in the map"). I don't know if this is related to anything, but I'd like to get rid of those. Most things work just fine, so they clearly are found in the map...clicking "Remove warning layers" wipes out everything, so that doesn't seem to be working right. My map extent clearly has at least 1 layer visible in the default zoom, but even that layer has the yellow triangle.