Latest Contributions by RichRuh

One additional thing to think about... If you want to make use of a particular field in a tracing operation, you need to create a Network Attribute, and only one Network Attribute can be assigned to a single field.   If one of these fields has different uses for different asset groups, you're going to have a hard time coming up with a Network Attribute name that makes sense.  Let's continue with John's example above.  If you wanted to run a trace that used KVAR for capacitors (I don't know if this is an actual use case, just go with me here) and also wanted to run a different tracing operation that looks at KVA for transformers, what would you name this Network Attribute?  If you name it KVAR, you're going to confuse the Transformer trace people.  If you name it KVA, you're going to confuse the capacitor people. My recommendation is that if you want to create a Network Attribute on a field, you shouldn't reuse that field for other purposes in different Asset Groups. This only really applies if your users are using the Trace geoprocessing tool user interface.  If you've built geoprocessing models or SDK tools for tracing (and you really should), then users won't see the names of the Network Attributes and you don't need to worry about this. --Rich ... View more

Bryan, I don't know the answer to your question about how to use the Oracle.ManagedDataAccess control inside a Pro add-in.  I'm not familiar with the control. An alternate implementation you might consider is to use the Database class from the Pro SDK.  This allows you to directly access relational databases that may or may not be ArcGIS geodatabases. --Rich ... View more

Just to clarify... John Alsup wrote:   Related tables cannot participate in tracing at this time.  There are future plans for Non-spatial objects, but no firm release date for that capability.  The non-spatial objects would allow for participation in tracing. Non-spatial edges and junctions are intended to better model telecom facilities.  There's no plan to provide access to related tables in tracing. ... View more

Naresh and Justin, Joins create a virtual feature class, which does not have a corresponding definition.  When you add a join to a layer, the original feature class is replaced with this new virtual feature class. Here's the technique for getting the definition from a joined layer. 1. Get the (virtual) feature class from the layer using FeatureLayer.GetFeatureClass() 2. Get the join from the virtual feature class using Table.GetJoin() 3. Get the origin table from the join using Join.GetOriginTable() 4. Get the definition from the origin table Here's a code sample: private TableDefinition GetDefinitionFromLayer(FeatureLayer featureLayer) { // Get feature class from the layer FeatureClass featureClass = featureLayer.GetFeatureClass(); // Determine if feature class is a join if (featureClass.IsJoinedTable()) { // Get join from feature class Join join = featureClass.GetJoin(); // Get origin table from join Table originTable = join.GetOriginTable(); // Return feature class definition from the join's origin table return originTable.GetDefinition(); } else { return featureClass.GetDefinition(); } }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I hope this helps, --Rich ... View more

Are you updating each row in its own EditOperation? Or all you calling modifyOp.Modify() 600,000 times for the single call to new EditOperation()? ... View more

Hi James, I would check out the ProConcepts Editing help topic. This snippet can probably be modified to solve your issue. I hope this helps, --Rich ... View more

Go ahead and try it; it looks like it should work. We are investigating adding the ability to iterate through datasets of a file system data store, but that would be Pro 2.5 at the absolute earliest. --Rich ... View more

Hi Gintautas, If you have a Geodatabase object, you can call Geodatabase.GetDefinitions<RasterDatasetDefinition>.  This will return a list of RasterDatasetDefinition objects. I can tell you how to obtain a Geodatabase object if you tell me where you are starting from (e.g., FeatureLayer). I hope this helps, --Rich ... View more

Hi Mike, What kind of database are you trying to run this against? Thanks, --Rich ... View more

This is fixed in Pro 2.4. ... View more

Hi Jorma, We've taken a look at your code, and from what we can see, everything looks fine. One thing we noticed is that the two tables you are editing are non-versioned.  How about the tables/feature classes that have relationship classes with MVK_KUVIO?  You cannot edit both versioned and non-versioned tables in the same call to Geodatabase.ApplyEdits(). If editing MVK_KUVIO is triggering an update to a related table that is versioned, this could be the source of the error. If this isn't the case, you may want to log this with technical support. I hope this helps, --Rich ... View more

Hi Jorma, Would you be willing to share a code sample?  There should not be any restrictions like you have described, although it's always possible that there is a bug in this area. Thanks, --Rich ... View more

The routine you are looking for is Version.Refresh From the feature class, get the Geodatabase.  Geodatabase.GetVersionManager() will get you a VersionManager.  VersionManager.GetCurrentVersion() will get you a Version object. --Rich ... View more