Query layer support?

[TrevorHart1]

We have an Job MXD which contains a query layer.

When the MXD data sources are remapped (to the Job version) the query layer reverts back to the base feature class rather than alter the query layer.

For example my query layer contains 1 feature class plus 2 tables combined via joins. When the MXD is remapped all I get is my feature class. In this case I actually get errors as the label expression comes from one of the tables.

Is this normal behaviour? This suggest to me that query layers are really supported?

EDIT BTW simple querying a single table or view works fine, so if I combine the above query into a view and use that for the query layer defintion it appears to work fine.

Thanks

[RaghavendraSunku]

We will try this out on our end and update you with what we find.

Thanks,
Raghu

[Jean-GabrielHasbani]

For example my query layer contains 1 feature class plus 2 tables combined via joins. When the MXD is remapped all I get is my feature class. In this case I actually get errors as the label expression comes from one of the tables.

Hello Trevor,

we have found that
1) depending on your service pack version of ArcMap and WMX, joins could be removed at reconnection (observed with ArcMap 10 sp 3 and WMX no sp)
2) joins are never remapped (bug TFS ID 16620). They will persist with the user saved in your template MXD and the destination table is not remapped either. Ex: In your MXD, you have Layer1 joins Table1 via GenericUser. Boths Layer1 and Table 1 are in your MXD. You start your job as CurrentUser, remapping on MyVersion. You will have MyVersion.Layer1 (via CurrentUser), MyVersion.Table1 (via currentUser), the join from Layer1 to Table 1 is via GenericUser pointing to SDE.DEFAULT.Table1

Jean

[AlisonGaiser1]

Anyone know if this has been fixed by WMX 10.2.2? We continue to experience this problem since an upgrade from 10.0 to 10.2.2.

Thanks,

     A

[AlisonGaiser1]

It appears that this is a known bug with ArcMap. Here is the NIM - NIM095174

Thanks,

     Alison