Add exisiting records from a List to a geometry via relationship

Question

Hi,

I have 2 tables:

- 1 geometry (point) table (in this case for addresses), no further attributes except metadata

- 1 table without geometry with all the content attributes (in this case vacancies per address)

- there is a 1:m relationship class relating these tables via globalid and a guid reference attribute

The list already contains several records and the idea is to be able to relate selected records to a given (created od selected) point on the map.

This works fine in ArcGIS Pro, by selecting both the given point and the records in the list to be added (via the "Attribute" pane and right-click "add selected to relationship". However I can just not find any way whatsoever to do this in Portal applications, such as the MapViewer or Experience Builder.

Is there any way to achieve this in the Portal environment?! Creating new related records works fine, but the issue really is that it is impossible to access the list for relating exisiting records.

GIS-KompetenzzentrumBern · Answer

Hi Iguillen,

Thanks for the answer. This may well be helpful later on in the process I am working on. You explain how I can manage to simultaneously select items in separate tables, if I read you correctly. However the explanation of how I can bring the existing items in the separate tables (geometry and list with attributes) in relation to one another in a Map Viewer or Experience Builder seems to remain unanswered. Since the Items in your view (Table C) are already related items. Otherwise they wouldn't be included in your view . Or am I missing something?

Iguillen_abt · Answer

Hello, I'm working on a similar case. I'm developing an application in Experience Builder that uses four related tables and three types of geometries. It has been a challenge to find an appropriate solution, but I have finally managed to configure the integration of the filtering and list widgets as follows:

I created a joined view, which I called "TABLE C," which in your case could be the combination of a geometry table (e.g., points), which we will call Table A, and a table without geometry containing all the relevant attributes, which we will call Table B. I used this joined view to configure the list and filtering widgets.

I configured the filtering widget (with Table C) to filter the elements that are then displayed in the list widget (also with Table C). Then, I set up the actions of the list widget to select the data records (framework) from both Table A and Table B. This way, when selecting an item in the list, the associated records from both tables are highlighted.

I hope this explanation is helpful and close to what you need.