Latest Contributions by RichRuh

Hi Brian, I've been working on this with Uma Harano‌.  When you create a Join between two different workspaces, the join has to be computed client-side, so you cannot get a Definition from it.  When both tables exist in the same workspace, sometimes the underlying database can create a database View, which we can use to create a definition.   There is another routine that might help you- BasicFeatureLayer.GetFieldDescriptions() facID_field = currentLayer.GetFieldDescriptions().Any(f => f.Alias == "FACILITYID");‍ Should help you with the specific answer you have listed above. I hope this helps, --Rich ... View more

Thomas, My apologies for not answering this earlier. I spent some time investigating this today. As currently implemented, the OpenRelationshipClass() method only works with feature service databases. We will review this implementation in a future release to see if we can extend it to cover additional database types. And we’ll definitely clarify the documentation as soon as possible. To open a relationship class with an SDE or file geodatabase, you need to use the Geodatabase.OpenDataset<RelationshipClass> method, passing in the name of the relationship class. If you don’t know the name of the relationship class you can find it and open it up using code like the following: IReadOnlyList<RelationshipClass> OpenRelationshipClass(Geodatabase geodatabase, string originClassName,    string destinationClassName) { List<RelationshipClass> relationshipClasses = new List<RelationshipClass>();  IReadOnlyList<RelationshipClassDefinition> relationshipClassDefinitions = geodatabase.GetDefinitions<RelationshipClassDefinition>(); foreach (RelationshipClassDefinition relationshipClassDefinition in relationshipClassDefinitions) {    if (relationshipClassDefinition.GetOriginClass() == originClassName && relationshipClassDefinition.GetDestinationClass() == destinationClassName)    {       relationshipClasses.Add(geodatabase.OpenDataset<RelationshipClass>(relationshipClassDefinition.GetName()));    }    relationshipClassDefinition.Dispose(); } return relationshipClasses; } I hope this helps, --Rich ... View more