AnsweredAssumed Answered

Accessing M-N and 1-M related table records in Portal Pop-ups

Question asked by mlashendock on Mar 17, 2020
Latest reply on Jun 11, 2020 by xander_bakker

Hello, I'm an Arcade newbie trying to modify the pop up for the parcels in a web map that serves as the basis for a Portal web application. The parcels feature layer in question has a pairing of relationship classes set up to other tables in the published Map Service.  This Service, called "TL_Parcels_Activities" is added to the web map and called "Tidelands Activities" in the Contents. 

Tidelands Activities


It contains six different items with a different definition query on the parcels source data, a feature class in our geodatabase called "TL_Parcels".


TL_Parcels has a Many-to-Many relationship to the PI Numbers table, which, in turn, has a One-to-Many relationship to the Tidelands Activities table.There is also an additional 1-M relationship set up to a Site ID table.  All of these tables and relationship class tables were included in the Map Service and show up in the web map.

TL Parcels Activities

The Related Records show up in the pop-up to open the related data in tabular form well enough...

Parcel Popup

... but I was hoping to use Arcade to get the related info to appear in the pop-up directly, without having to click and read in the attribute tables themselves.

I found some good examples of script suggestions on GeoNet for some 1-M situations that I tried out. I think folks were using these for AGO, which I understand has some quirky differences from the Portal environment. I started with this sample:  How do you reference another field from a related table in Arcade? 


My initial attempts kept giving me the error:
"Execution Error:Runtime Error: Identifier Not Found. $map"


I found an example that focused on the GlobalID that I decided to run with and still got the same problem.

Get 1:M related objects using Arcade 

// read the GlobalID of the feature
var globalid = $feature.GlobalID;
// create a sql expression to filter the asset table
var sql = "gis_id = '" + globalid + "'";
// Access the Activities based on the name in the map
var ACTIV_view = FeatureSetByName($map, "TL_PINumbers");
// filter the assets using the sql expression
var ACTIV = Filter(ACTIV, sql);

// get the count of the related Activities
var cnt = Count(Activities);
// create a variable to hold the resulting text
var ACTIV_info = "";
// validate if there are any related records and handle accordingly
if (cnt > 0) {
// there is at least 1 related record, create activity info
ACTIV_info = cnt + " Activities:";
// loop through related records
for (var activity in Activities) {
// create text using name and description (you should modify this to match your needs)
var ACTIV_text = " - " + + TextFormatting.NewLine + Activity.description;
// add the text for this activity to the activity info
ACTIV_info += TextFormatting.NewLine + ACTIV_text;
} else {
// no related records (or the sql query did not work)
ACTIV_info = "No related Activities";

return ACTIV_info;



With these I could never access the $map from the Globals tab. Despite the fact that all of these other things were in the same web map, all I could see were the $feature for all of the fields in the Parcels feature class.


As a test, I separately published a Hosted Feature Layer of the parcels/relationships which shows the two related tables, but not the relationship classes themselves, within the service.

Hosted Feature ServiceThen I added that to my web map and tried to use the same Arcade expression on that layer.  $map was now accessible to me in the Globals and the code seemed to get past that sticking point, but gave me an Execution Error: Filter cannot accept this parameter type.


I'm not always exactly sure what the sample scripts are asking for everywhere, so I'm not fully sure I'm putting the correct info where it belongs. I also know that I will probably need to do more to this to add all the attribute info I want to display and probably to get the script to go to the next level for the other 1-M relationship between the two tables.