Latest Contributions by KyleGruber

Michael, Got everything working perfectly with Create Relationship Class, with one exception.  Is it not possible/valid to have multiple relationship classes with the same destination table?  It seems when I try this and try to export an MMPK, I get an Error 2698:  No Permission To Perform The Operation Upon The Datasource.  I have tried removing all traces of the relationship classes (the tables from Contents, and the tables in the geodatabase in the catalog), but I'm still getting the error.  I also can't find any documentation on this particular error code. EDIT:  Resolved the error, but it does seem that creating multiple relationship classes that have the same feature as the destination table causes the MMPK creation to fail.  The following errors show up in ReplicaLog, and the source table of the second relationship class is the feature that always fails to copy. <ReplicaMsg time='7/12/2019 3:55:12 PM' type='LOG_MESSAGE_TYPE_WARNING' code='102014' elapsed='642.520000 seconds' method='GeoDBDataTransfer::Transfer' objectClassName='ESN' replicaName=''>Failed to copy dataset ESN.</ReplicaMsg> <ReplicaMsg time='7/12/2019 3:55:12 PM' type='LOG_MESSAGE_TYPE_WARNING' code='102015' elapsed='0.007000 seconds' method='GeoDBDataTransfer::Transfer' objectClassName='ESN' replicaName=''>Conflicts detected but resolve conflict is set to false. Bailing out.</ReplicaMsg> ... View more

This makes sense, actually.  The beginnings of the stack trace (going from the bottom, up) look like a typical OutOfMemoryException in WPF.  This indicates there's likely some sort of memory leak with dynamic rendering. ... View more

This has seemingly been confirmed as a bug by ESRI technical support (#02345493), and I have to assume it is on the Runtime side as the locator seems to be correctly built with this information from ArcGIS Pro.  Any idea if this is on the radar or being looked into? Edit - Sorry, just noticed the case was converted to a bug (#BUG-000123297) which I think answers my question. ... View more

Michael, Thanks as always for the confirmation! ... View more

I created a relate in Pro. Now looking at that, I'm guessing I need to be using the Create Relationship Class tool under the Data Management extension instead? ... View more

Michael,   Thanks for the information.  The synchronous code was just laziness on my part for the repro app, I'm using the proper await/async functionality in the real app and getting the same result. I don't know if the creation of the MMPK would be doing some sort of check on the validity of the relationship before including it in the package, is there some sort of validation that can be run on a relationship?  Basically the purpose I'm using it for is when an address gets geolocated, I want to pull all the fields in other layers that need to be included in the response.  So I see a relationship from the ESN layer for instance that provides the ESN ID information for the address geocoded from the Centerline layer, and I have a standard name that our clients can use to identify that relationship that I can reference in code.  Does that make sense, is there a better way to accomplish this? Also, it's curious that when I import the MMPK into ArcGIS Pro, the relationship shows under the layer properties. ... View more

Michael, Repro project can be downloaded here: https://helpdesk.alertts.com/content/Debugging/ArcGISReproApp2.7z I also have a case open with ESRI technical support (#02346594) Thanks, Kyle ... View more

John, Here's a shot in the dark suggestion, have you tried making the calls synchronous instead of asynchronous to see if it makes a difference? Change all await calls to .GetAwaiter().GetResult() So if you're doing await RouteTask.GetRouteAsync(), it would change to RouteTask.GetRouteAsync().GetAwaiter().GetResult(). Just to clarify, I'm not suggesting this as a solution to the problem (I would never advocate running things synchronously on the UI layer), but if it helps it would at least isolate the issue to the async/await functionality. ... View more

Lets maybe try phrasing this issue/question another way.  If I geocode an address from a street address locator (ie. 705 Main St from a street segment with a range of 700-800 Main St), is there a way to work my way back to the original layer/line segment that came from?  I can't seem to find any link between a LocatorTask and the original FeatureLayer it was built from. ... View more

Mike, Thank you, no worries, just wanted to know if this was a confirmed bug and was in the queue! ... View more

Michael, Any updates on this?  I know you guys are extremely busy, I'd just like to know if this is still being looked into.  Causing a pretty major problem in our workflow.  I think I may have thought of a potential solution of manually creating a composite locator by creating a collection of LocatorTask objects tied to the locator files, but obviously this isn't perfect (doesn't tie in the priority logic built in with a Composite Locator), I will let you know how this goes. Thanks! ... View more

Just curious if anyone else has run into this, this is effectively preventing distribution of multiple locators no matter how they were created or how they're packaged (composite or individual) if a new style locator is present.  The new locators are amazing, but obviously this is preventing simple things such as finding intersections with a center line locator when you already have an address point locator. Michael Branscomb‌ Just wondering if a bug has officially been logged for this, or am I possibly just doing something completely wrong here? create locator arcgis pro 2.3 arcgis runtime sdk .net‌ composite address locator‌ ... View more