nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Accessing attributes of a table joined to a feature service via a 'relationship'?

KathrynJones

Hi folks!

I'm relatively new to the Flex Viewer but I'm having fun with it so far. I've implemented the eSearch widget by rscheitlin and have also go the Edit widget to work.

Now to my question: I have a feature service set up in SDE, which is in a 1:1 relationship to a table in SDE. Does anyone know if there is a way to access the attributes of the related table in flex viewer - either in the edit widget or some kind of search/identify widget? I have a feeling the answer is probably no, but best thought I ask anyway.

I'd rather not have to learn the Flex API and programatically do it... but I might have to!

Thanks very much in advance. Any help/advice would be greatly appreciated.

Cheers,
Kathryn

Find more posts tagged with

Accepted answers

All comments

RobertScheitlin__GISP

Kathryn,

Yep, look here:

http://www.arcgis.com/home/item.html?id=4ec33120c9ea4d019fddf722fc34ea3c

KathrynJones

Excellent, thanks for your fast response Robert. I'll look into the widget.

Another related question: in the 'Enhanced Search Widget XML Configuration.pdf' I notice in your explanation about the 'fields' parent element, you write: "If you are using a layer that contains a join than the full join field name should be used"

I hadn't noticed this before I asked my original question. Would this apply to a relationship existing in SDE or only to joins?

Thanks again,
Kathryn

RobertScheitlin__GISP

Kathryn,

The widget does not allow you to specify which related fields are returned or any other configuration of the related info, so it doesn't matter.

KathrynJones

Hi Robert,

I don't understand what you mean sorry. Are you saying you can't return related fields in your eSearch widget, even though your documentation says otherwise?

In the documentation with the widget you write "The fields parent element contains all the individual field child elements that will be used for this particular layer. Everything for the field element is specified as an attribute of the element. The name attribute is the actual field name. If you are using a layer that contains a join than the full join field name should be used."

I took this as meaning you would access a related field like below, where the field in the related table is named 'Client'.

<fields all="false">
<field name="sde.SDE.MyTable.Client" alias "Client" gridfield="true"/>
... etc

Sorry if I'm missing something here! Thanks for your help so far...

Cheers,
Kathryn

RobertScheitlin__GISP

Kathryn,

There is a little confusion here on two parts maybe. One the link I provided that allows you to query related tables is for the Attachment Relate Info Window Widget, not the eSearch. The eSearch allows for specifying JOINED fields but has not support for related tables. The Attachment Relate Info Window Widget does support querying related tables but does not allow you to specify which fields of the relate are returned. Two different widget and there is a difference between a relate and a join.

santa1.gif

MarkMitchell

Robert,

In a feature service edit session, through FLEX. Have you ever configured it or have you seen it configured that after the insertion that you could edit the related data tables. For example, there is an incident. I have a incident feature class and a contractor table (Related). I want to add two contractors working on this incident in the contractor table through my feature service I am accessing from Flex API. Any suggestions or experience related to relates and feature service editor??

Mark
GIS Specialist

BjornSvensson

Robert ... Have you ever configured it or have you seen it configured that after the insertion that you could edit the related data tables.

I know you asked specifically for Robert's advice, but ... in the 3.1 version (planned for December) there will be better support for related records. One of them is that you will be able to view them as part of the "regular" pop-up window. Another is that you will be able to add/update/delete records from a table when editing a feature in a pop-up window.

MarkMitchell

I know you asked specifically for Robert's advice, but ... in the 3.1 version (planned for December) there will be better support for related records. One of them is that you will be able to view them as part of the "regular" pop-up window. Another is that you will be able to add/update/delete records from a table when editing a feature in a pop-up window.

Bjorn,

Thanks!!! I cant Wait!!!!

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.