Odd behavior with AGX 1500 Query tool using Esri-recommended map service designs

[danan]

The query functionality in AGX 1500 is very welcome. Thanks to Esri for adding it. However, its implementation is causing problems. We get odd behavior from the new Query tool in AGX 1500 when using Esri-recommended map service designs. For example, a typical Esri-recommended design has the map doc partitioned into group layers organized by scale:

http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=How_to_build_online_base_maps

Problem #1: Confusing presentation in 'select sub-layer to query' dialog box

Using the Esri recommended basemap design approach, when an AGX 1500 user queries such a map service, they're presented with a confusing 'select sub-layer' dialog. It shows the same layer repeatedly but with map scale names attached (see attached screenshot: SublayerToQuery01.JPG).

As a band-aid, we created a map doc / service without using group layers (but retained scale-dependencies) and renamed each layer so it would be more representative the features exposed; e.g. in our case, we have one FC divided into multiple layers using definition queries. At some scales only Interstates are shown; in others, only Interstates and US Routes are shown, etc. It's still very kludgey as duplicate layer names remain. Please see attached image SublayerToQuery02.JPG.

What's the best way to make the 'select sub-layer to query' dialog box more comprehensible and intuitive to users? Life would be easier if, like with the Legend, one could select which layers we wanted users to query on. This would allow us to eliminate duplicates in the 'select sub-layer to query' dialog. Is that functionality scheduled for the next release of AGX? Could it be scheduled for a future release?

Problem #2: "Get Unique Values" function in Query builder works differently in AGX than in ArcMap

In ArcMap, when one chooses a layer to select from that has a definition query on it, clicking "Get Unique Values" rightly returns only values that are valid for the attribute as specified by the definition query. For example, on a layer named "Interstates Routes", there is a definition query of: RTE_1_CLSS_CD = 'I'. In ArcMap, when you query this layer and choose "Get Unique Values" for the RTE_1_CLSS_CD field, you rightly only see a value of 'I'.

In AGX 1500, when you click on the RTE_1_CLSS_CD field for the "Interstate Routes" layer, you get more than just 'I'--you get all the unique values in the FC as if no definition query existed. This means the user can choose values for records that can never be returned by the query (US routes, etc). Is there a workaround for this? Is it a known issue? Will it be fixed in the next release?

Problem #3: Shape field must be checked in map doc for Query icon to be enabled

We're not sure why, but if the shape field is not checked on in map doc (Layer Properties > Fields), the Query icon in AGX will be grayed out. Why is this the case?

To summarize: We're happy that AGX now has Query functionality. But we're struggling with the implementation. We want the user to have a positive, straightforward Query experience. What can we do with the present release to achieve this? And what Query tool improvements are planned for the next release that will make it more user friendly?

[danan]

Don't know if this is related, but I'm seeing an additional odd bit of behavior. In a map service's source MXD, there are six (6) identically named "State Maintained Routes" layers (see attachment: StateLayersFromServiceMxd.jpg).

But from AGX 1500's 'select sub-layer to query' dialog box, only five (5) "State Maintained Routes" layers appear (see attachment: StateLayersFromAgx1500.jpg). Although this isn't even quite what we want, why might there be a mismatch between the source MXD and what's shown in the Query tool dialog?

By the way, we're sourcing the same underlying FC many times in the same map doc because we want to control symbology and content at different scales.

[Anonymous User]

Original User: dananrg

To solve problems 1 and 2 above, we utilized "problem #3" behavior. As well, the mismatch between layers in the MXD and layers present in the 'select sub-layer to query' dialog was our goof (we'd forgotten to turn on the Shape field for one layer).

Here's how we got our desired user experience:

We turned the Shape field off for all but one layer ("State Maintained Routes"). This way, the 'select sub-layer to query' dialog gets bypassed, leading immediately to the Query Builder--with only one layer enabled for querying, there's no longer anything to choose from. And since there is no Definition Query defined on this particular layer, when a user clicks on a field and gets a list of domain values to choose from, this now makes sense contextually; e.g. they are no longer limited by a Definition Query and can search for whatever they like.

My apologies--our mistake. However, it would be nice to see more detailed documentation about the new Query feature. Better documentation, or a cross-reference to relevant ArcGIS Server documentation, would have saved us some time. Our request for Legend-like enable/disable functionality was there all long--it just took a bit of trial and error to discover it.