topic Re: Trouble Selecting from FeatureLayer containing Definition Query in ArcGIS Pro SDK Questions

Trouble Selecting from FeatureLayer containing Definition Query

MikeRatcliffe — Wed, 04 Apr 2018 16:11:12 GMT

My Definition Queried featurelayer clearly contains the field# "Material;" however, my Select() returns the exception: "GeodatabaseFieldException," field does not exist or is unaccessible.

The source FeatureLayer is a Complex Edge from a Geometric Network...(Problem?)

If I first remove the Definition Query from the FeatureLayer, the Select executes properly (Material = CI).

Select Method is supposed to drill through Definition Queries appropriately:

"...If there is a definition query set on the MapMember, the Select() method will automatically work on the subset of rows in the MapMember that meet the definition criteria. You specify an additional query that will be applied after the MapMember's definition query by passing valid QueryFilter object for the QueryFilter parameter.
If the MapMember has any joins, this Select() method takes that into account.

To ensure maximum robustness, callers should explicitly dispose of the returned ArcGIS.Core.Data.Selection in either a using statement or a finally block."

Can someone point me in the right direction?

Re: Trouble Selecting from FeatureLayer containing Definition Query

RichRuh — Thu, 05 Apr 2018 18:48:22 GMT

Hi Mike,

I set up a similar situation and tried to reproduce your issue. I have a map in Pro which contains a feature layer that points to a feature class that is a complex edge in a geometric network. The feature layer has a query definition set up on it (Phase Designation is Equal to 4).

I then wrote an add-in that grabbed that feature layer and executed a Select() and a Search() on that layer. Both worked fine.

bool DoTest(Layer myLayer)
{
   FeatureLayer featureLayer = myLayer as FeatureLayer;
   string definitionQuery = featureLayer.DefinitionQuery; // to confirm that it is set when stepping through debugger

   // Create a query definition
   QueryFilter queryFilter = new QueryFilter
   {
      WhereClause = "FEEDERID = 'GR-202'"
   };

   int searchCount = 0;
   using (RowCursor cursor = featureLayer.Search(queryFilter))
   {
      while (cursor.MoveNext())
      {
         searchCount++;
      }
   }

   using (Selection selection = featureLayer.Select(queryFilter, SelectionCombinationMethod.New))
   {
      int selectcount = selection.GetCount();
   }
   return true;
}

Could you send me some information about what you are trying to do? If you are using a QueryFilter, is it possible that you are using the same field that appears in the definition query? Could the layer definition be hiding the table field that you are trying to use?

Thanks,

--Rich

Re: Trouble Selecting from FeatureLayer containing Definition Query

MikeRatcliffe — Thu, 05 Apr 2018 19:31:25 GMT

The FeatureLayer represents water mains, Definition Queried by DATASET = ABANDONED.

Here is a sequence of step that lead to the issue:

1. Grab the search layer from the active map

2. Populate a list of field names from it using List<FieldDescription>. (I am absolutely making available the same field from the Definition Query to the user, which is "DATASET.")

3. User selects which field to search/select. Based on selected field, it is routed to an appropriate whereclause and fieldtype for conversion that sets up the actual feature selection.

4. DATASET = Abandoned is a CodedValueDomain. Fields with CodedValueDomains are sent to an IList<string> of codedvaluepairs.values, which are then selectable by the user.

5. Finally, a spatialqueryfilter is applied to a FeatureLayer Select().

If I do not SetDefinitionQuery(""); select() returns the exception: "geodatabasefieldexception," field does not exist or is inaccessible. *I get this exception when trying to select out of any fieldtype (string, integer, CodedValueDomain, etc.). *Seems none of the table fields are accessible through the Definition Query.

If I grab the DefinitionQuery before setting it to nothing, and re-instate it after the selection, the features are selected without the original DefinitionQuery, but show VISUALLY as you'd expect with the DefinitionQuery intact. (cheating). Not what I need.

Re: Trouble Selecting from FeatureLayer containing Definition Query

RichRuh — Thu, 05 Apr 2018 20:21:38 GMT

Could you send me a short code snippet showing me how you are building the WhereClause and other properties of the QueryFilter that you are passing into FeatureLayer.Select()?

Thanks.

Re: Trouble Selecting from FeatureLayer containing Definition Query

MikeRatcliffe — Fri, 06 Apr 2018 12:16:26 GMT

.cs provided (not necessarily short...) Thanks.

Re: Trouble Selecting from FeatureLayer containing Definition Query

RichRuh — Fri, 06 Apr 2018 22:49:25 GMT

Mike,

I've looked through your code and haven't found anything obviously wrong.

My understanding from our conversation above is that if this line is present the code works, and if it is commented out the call to FeatureLayer.Select() throws an exception:

srch_lyr3.SetDefinitionQuery("");

Is this true? If so, that would seem to be a bug, but I cannot reproduce it to be sure. It's not a generic problem with the API, but could be some combination of your database and map. At this point, your best approach is to submit this to technical support. They'll probably want a data sample and a smaller code sample that demonstrates the problem. I'll contact our liaison with technical support to let them know they can work with me on this issue.

Sorry I cannot help more.

--Rich

Re: Trouble Selecting from FeatureLayer containing Definition Query

MikeRatcliffe — Mon, 09 Apr 2018 11:46:30 GMT

Thanks, Rich.

Yes, you are correct. Exception if "srch_lyr3.SetDefinitionQuery("");" not in place.

I'll attempt to reproduce on a smaller scale, and submit as possible bug to technical support.

Re: Trouble Selecting from FeatureLayer containing Definition Query

MikeRatcliffe — Thu, 19 Apr 2018 13:42:37 GMT

The issue was with my handling of SQL Syntax in the whereclause for the queryfilter. When a codedvalue data type is String, the value must be enclosed in SINGLE QUOTES.

failed syntax: WhereValue = Form1.GVar.ms_attfn + Form1.GVar.Oper8tr + Form1.GVar.ms_v;

proper syntax: WhereValue = Form1.GVar.ms_attfn + Form1.GVar.Oper8tr + "'" + Form1.GVar.ms_v + "'";