Latest Contributions by RichRuh

You can create an MMPK with data *from* a utility network (e.g., the lines, poles, devices, pipes, etc.), but you cannot yet include the network itself in a MMPK. --Rich ... View more

Hi Mike, This is currently an internal development project at Esri.  It will likely be released over a series of releases- we'll have support for viewing associations before full tracing support is enabled.  We're hoping to release the first pieces of this next year, but I cannot make any release commitments at this time. Just to clarify, are you looking for MMPK support (read-only maps exported from ArcGIS Pro and side-loaded onto a device) or offline sync (read-write maps with sync between a mobile device and the server)? --Rich ... View more

That's a relief to hear!  You had me questioning my sanity for a few minutes. 🙂  --Rich ... View more

Adding DDL (data definition language) operations such as creating domains is on our long-term roadmap for the Pro SDK. For now, using Geoprocessing‌ is the only technique to do this.  I would post in that group to figure out why you are sometimes getting errors. --Rich ... View more

No, this isn't possible with the Pro SDK.  The best you could do is check to see if the feature class design meets your requirements. --Rich ... View more

Do you need to delete and recreate the table, or just clear it out? If deleting all the records is acceptable, you could try Table.DeleteRows(). If you pass in a default QueryFilter, this deletes all the rows in the table.  Alternatively, you could use the Truncate geoprocessing tool. --Rich ... View more

An overview on how to edit geodatabase data can be found here. --Rich ... View more

The Pro SDK doesn't support creating spatial joins.  Using geoprocessing/Python here remains your best bet. --Rich ... View more

If you're starting from a FeatureClass object, just try to cast it to an AnnotationFeatureClass: FeatureClasss myFeatureClass; ... if (myFeatureClass is AnnotationFeatureClass) { AnnotationFeatureClass myAnnotationFeatureClass = myFeatureClass as AnnotationFeatureClass; ... }‍‍‍‍‍‍‍ Is this what you are looking for? --Rich ... View more

You're correct.  `Row.Handle` is not stable.   Under the hood, the Handle property is just a pointer to an underlying ArcObjects object.  When you open the same table twice, ArcObjects reuses the same COM objects, so Table.Handle is identical for both Table objects. With rows, this isn't true.  Fetching the same two database rows with two cursors will create two different row objects (and different Row.Handle values).  Flipping it around, if you use a recycling cursor, all of the rows fetched from that cursor will use the same underlying object, and Row.Handle will be the same for every one. (Since I've seen your other post, I'll also add that Table.Handle will have a different value every time you start ArcGIS Pro.) I hope this helps, --Rich ... View more

As Wolfgang Kaiser‌ states above, you need to use a table name instead of an ID. Other than that your list above looks correct. --Rich ... View more

Anuj, The Pro SDK is implemented in terms of ArcObjects.  While I've never tried it personally, I expect the two APIs would interfere with each other.  It's definitely not supported. --Rich ... View more

Anuj, Matt is correct.  The Pro SDK does not yet support Data Definition Language (DDL) operations directly.  If you are writing a Pro Add-in, you need to use the geoprocessing API.  In a stand-alone CoreHost application, you need to shell out to a Python script. --Rich ... View more