Zum Hauptinhalt gehen

Relationships

Kommentare

10 Kommentare

  • Permanently deleted user

    I should mention that many of my relationship classes are Many-to-Many (eg. one feature can related to many documents, one document can relate to many features).

    0
  • Permanently deleted user

    hi-

    There is another type of relationship that is needed and that is table to table to feature.  say for example we have plant locations.  there is a table with the scientific name for plant. and there is another table which does not relate to feature, but is keyed on the scientific name.  so we need to be able to link table to feature and table to table, and then report it.

    J

    0
  • Permanently deleted user

    Relationship classes are not supported by default in Essentials. Only Joins made in ArcMap will show up in your data.

    You can manage complex relations with Workflow. In this case it is not necessary to create the relation in ArcMap, but simply serve the related tables from your ArcGIS Server instance so that they can be queried. You can then build the relation and query the tables 'on the fly' using your workflow logic. Although you could also query a relation created in ArcMap from a workflow, this is probably the easiest approach.

    0
  • Permanently deleted user

    Hi Dominic,

    Unfortunately you cannot access attributes from a relationship in the layer details, such as the feature label and description; they will currently only be available in their own tab in the Feature Details window.

    You can manually get attributes from a relationship in a report by using a workflow. You would have to get the values using the RelationshipQueryTask, and then send the resulting data to the report via the TemplateReport activity. However, this will get complicated if you also want to view a map image in the report, or include attributes of the original layer, since by using the TemplateReport activity, all of the data to display in the report has to be passed in through the workflow.

     We do have improvement requests filed to make integrating attributes from a relationship in a report as easy as it is to do with regular data links, but for now, you may find the following code gallery sample helpful in getting you started: https://support.geocortex.com/using-a-workflow-to-generate-a-multi-layer-report-with-map-1

    -Victoria

    0
  • Permanently deleted user

    Dominic, the limitations Victoria is taking about are because of the way ESRI implemented their database-like routines. If you are using ArcSDE (Oracle or SQL) to store this data, there is an option. Using a layer view to combine the data together at the database level will create what appears to be a feature class, but really is a view of a feature class and a related table. Use the command line "sdetable -o create_view" with appropriate command lines to create it. This would then be usable like any feature class in Essentials, if included in the map service. The only trick to make the view spatial is to include the "shape" and "objectid" as columns in the field list.

    Hope that helps.

    ~S

    0
  • Permanently deleted user

    Agree,

    We have the same requirement for this feature.

     

    Thanks

    0
  • Dan Griffin

    Hi Shawn,  Just wondering if this approach might work for enabling Instant Search on related tables?

     

     

    0
  • James Landwehr

    +1

    0
  • Permanently deleted user

    Hi Dominic,

    Did you solve this issue, sice I am having the same issue here.

     

    Thanks,

    Ahmad

    0
  • Permanently deleted user

    Hi Ahmad,

    At the time we decided to change to way we wre going to acces the data and use the "Data Connection" instead.

    But I think I will need to revisit soon as we are working on a new project the would require relates to be included.

    Regards,

    Dominic

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.