Latest Contributions by RichRuh

Both the REST call and ArcPro SDK is doing the same work, like updating multiple subnetworks. REST call is super fast taking about 1 minute. while ArcPro SDK taking about 8 to 10 minutes to update the subnetwork on first time. Second time the processing time is decreasing to 3 to 4 minutes. That's why I'm focusing to the REST call.  When you call the Pro SDK to update a subnetwork, how long does the REST call take? Also I noticed that if we are updating subnetwork for branch version from SDE.Default I'm not sure what you mean here. Are you updating the subnetwork on the branch version or the default version? ... View more

To run the subsequent trace, you would want to set a new starting point at the result of the first trace. Does this help? ... View more

Try keeping the traversability section of the trace configuration the way you normally would for an upstream trace, and enter a Filter to stop at overhead fuses. ... View more

The time difference here is alarming and unexpected.  Do you have fiddler installed? I'm wondering if you could examine the call to update subnetwork that is generated by the Pro SDK and see if it matches what happens when you manually call it?  Is the Pro SDK updating multiple subnetworks? --Rich ... View more

Branch versioning does not support multiple concurrent editors against a single version. When you are updating a subnetwork with a direct REST call it's creating a second editing session. That's the source of the schema lock errors. Have you tried using the Pro SDK to update the subnetworks rather than REST?   ... View more

While I don't work on the geoprocessing team, I have not heard of any plans. There really shouldn't be any problem working with the default ("memory") memory geodatabase. If you're concerned about memory usage, you could always delete the tables that you have created when you are finished with them. Creation is a bit tricky at the moment, because the code to do so is different depending on whether or not you have run a geoprocessing tool using "memory" already.  Here's the workaround we shared at DevSummit: Geodatabase geodatabase; try {   geodatabase = new Geodatabase(new MemoryConnectionProperties()); } catch {   geodatabase = SchemaBuilder.CreateGeodatabase(newMemoryConnectionProperties()); } (We're fixing this at 3.1) ... View more

Dkuida, The Pro SDK allows you to create multiple memory geodatabases, each with an arbitrary name, as you have shown in your code above. Geoprocessing, on the other hand, only supports one memory geodatabase, called "memory", which can be created with either of these two lines: MemoryConnectionProperties() MemoryConnectionProperties("memory") Ken's reply shows how to create and use this memory geodatabase with geoprocessing. --Rich   ... View more

Hi Brett, Just to confirm- you're using the EditOperation class to duplicate the features, right?  Could you send us the EditOperation code that you use in your tool?   Thanks, --Rich ... View more

Yes.  Attribute rules are written using a scripting language called Arcade, which provides a function called GetNextSequenceValue().  More information on attribute rules can be found starting here. --Rich ... View more

I'll add that you should take a look at attribute rules.  These are scripts that you can configure on a geodatabase that run in response to edit events on specific feature classes or subtypes.  Doing a spatial query and assigning a value to an attribute is exactly what they are designed to do. Attribute Rules also work cross-platform, and will fire outside of ArcGIS Pro (e.g., runtime and server) --Rich ... View more

This snippet shows how to calculate the Sum and Average of a set of fields. ... View more

Hi Shabina, Table.Search doesn't support functions such as "Min()". Check out the Table.CalculateStatistics method instead. API class reference Conceptual doc I hope this helps, --Rich ... View more