We have been migrating over from AGOL to enterprise. In one of our field maps, when we try to add a new related record to the water meter related table the the parent meter id (meterno is its name in the feature class table) will not populate using the following arcade expression.
Everything nlooks right but is there some difference in terms in portal vs online?
Thank you.
Tim
// Get the feature set for the related wMeters feature
// and return only FacilityID
Solved! Go to Solution.
Not the table name, the relationship class. In the expression editor, you can look in the Profile Variables to find the related table:
Clicking on the related table will show you the correct text to put into the function. It may be the table name, but may not. You can see the relationship class name in the Feature Service definition on your server.
There is definitely a difference between the two. AGOL always has the latest version of Arcade, but Portal's Arcade version is fixed. This means that improvements and functions you might have used in AGOL can stop working on an older version of the same tools.
I don't see anything particularly telling in your expression, but what's going on with the second parameter of your FeatureSetByRelationshipName function? Shouldn't the relationship class have a name?
This script was written by my predecessor so I am not sure why they did not include the name of the related table. I did try including the related table name and still did not work.
Not the table name, the relationship class. In the expression editor, you can look in the Profile Variables to find the related table:
Clicking on the related table will show you the correct text to put into the function. It may be the table name, but may not. You can see the relationship class name in the Feature Service definition on your server.
Thank you! This solved the problem.
Here is the correct code.