Latest Contributions by RichRuh

Hello Berend, We've confirmed that this is a bug in the Pro SDK.  The workaround for now would be to refetch the features using the object IDs from the rows. It is too late in the Pro 2.2 development cycle for us to fix it in that release, but we will target a fix for 2.3. --Rich ... View more

Just to confirm, this method will be available in Pro 2.2. ... View more

Bart Van Hoecke‌ and I have spoken offline.  We believe that the new returnServiceEditsOption available in the feature service at ArcGIS Pro 2.0/ArcGIS Server 10.6 will solve his problem. ... View more

Hi Taner, ArcGIS Pro does not currently support plug-in datasources.  This is an active R & D project that we've been working on.  It won't be ready for the summer 2.2 release, but we hope to make it available in a subsequent release. --Rich ... View more

Hi Bart, We have additional questions on what you are trying to do. 1. Does your feature service refer to an enterprise geodatabase that uses versioning?  If so, which kind- traditional or branch? 2. How are you making these edits?  Are you intercepting and adding to the payload to ApplyEdits()?  Or directly editing with ArcObjects?  Are you making these edits before, during, or after the edit operation from the client? 3. What version of ArcGIS Enterprise are you using? If you'd rather not answer these questions in this public forum, please feel free to e-mail me directly at [email protected].  Thanks! ... View more

Hi Bart, We're taking a look at this now.  Could you please provide more information about why you want to disable the feature cache?  What workflows or functionality are you trying to enable? We have no objection in principle to providing access for this, but if you are trying to work around a problem we want to be sure to fix the underlying issue instead. Thanks, --Rich ... View more

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 ... View more

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. ... View more

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 ... View more

Given the FeatureClass, you can get a FeatureClassDefinition object by calling FeatureClass.GetDefinition(). From the FeatureClassDefinition you can call FindField() to find the field index, given the name.  With that and a fields collection from FeatureClassDefinition.GetFields(), you can get a Field object.   Finally, the Field object has a FieldType property. ... View more

Unfortunately, there's no workaround at this time. ... View more

It's planned for 2.2, shipping summer 2018. ... View more