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; } } }

Add Inspection/Related Record: Bring Value from Feature Class to Related Table? Arcade?

ArmstKP

When clicking the blue add button to add a related record/inspection, it brings the globalid/guid value forward into the related table, but what if I want the feature class park name value to populated the related table as well in the park_name field?

Find more posts tagged with

Accepted answers

Anonymous User

Just as a follow-up, we've identified two issues related to FeatureSetByRelationshipName.

1. If your relationship contains a "." in it, then the Android and iOS apps fail to successfully execute the expression. This also occurs in Pop-ups. This is under investigation but probably won't make the next release.

2. In the Arcade editor, if the related layer/table does not have any features it, when you attempt to test it or save an expression that used FeatureSetByRelationshipName the editor fails to execute the expression with "Execution Error:Cannot read properties of undefined (reading 'toString')". The reason it fails is due to how the Arcade Editor evaluates the expression when the foreign key field value is null. When Field Maps or Map Viewer launch the Arcade editor, they need to provide a sample feature to represent $feature. It will query to find the first feature in the layer/table and use that. If there are no features, it generates a sample feature using the default values of the field. In this specific case, if your related table has no features in it, this sample feature will likely have a null value for it's foreign key field. A simple workaround is in the Arcade Editor edit $feature using the > icon and then the pencil/edit icon and add any value to the foreign key field (it doesn't matter what). Then you should be able to test and save it. This is not planned to be fixed in the next release.

Anonymous User

Check out the second example in this blog post. It should be exactly what your looking for, just change the layer name and attribute name.

All comments

dougbrowning

Just make a query

var sql = "PointID = '" + $feature.PointID + "'";
var tbl = Filter(FeatureSetByName($map,"Points", ['DesignLat'], false), sql);
return First(tbl).DesignLat

chill_gis_dude

We are in 11.2 Enterprise, so maybe the fix is in a later release?

Thank you for the suggestion! You don't have an example I can look at, do you?

dougbrowning

I thought it was fixed? If not just use FeatureSetByName and then wrap that in Filter(). Works about the same.

chill_gis_dude

Does anyone have a workaround for this if there is a "." in the relationship class name?

ArmstKP

We aren't using offline areas.

This looks to be the related error in the log:

Anonymous User

Are you using offline areas by any chance?

If you go to Profile->Troubleshooting->Logs do you see any messages with "Arcade" in them? The error is probably logged there.

ArmstKP

@Anonymous User I used that code and it worked when I clicked the "Test" Button. I saved it and then opened up Field Maps 22.2 and I get in red text, "Failed to calculate"

Anonymous User

Check out the second example in this blog post. It should be exactly what your looking for, just change the layer name and attribute name.

ArmstKP

@MobiusSnake Could you give me a small example to go off of?

MobiusSnake

Arcade should do it. I've set up this kind of thing in Pro using GDB attribute rules but the same approach should work with a calculated expression in Field Maps. Use the foreign key GUID to find the parent record with a feature set, get the first record of the feature set and pull the field you want off that feature.

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.