This is stupid but I'm finding the Arcade Intersect function to be fickle - some days it'll work, some days it'll not work.
Intersects will work with $map and $datasource but not Portal. Esri has told me using Portal is an enhancement. That's fine but sometimes it works and sometimes it doesn't. That seems to remove the "science" from computer science.
//this works
var myFeatures = FeatureSetByName($map, myLayer, ['*'], true);
var intersectedZone = First(Intersects($feature, myFeatures));
return intersectedZone["District_N"];
//this works
var myFeatures = FeatureSetByName($datasource, myDataSource, ['*'], true);
var intersectedZone = First(Intersects($feature, myFeatures));
return intersectedZone["District_N"];
//this worked yesterday but not today
var myFeatures = FeatureSetByPortalItem(myPortal, myID, 1, ['*'], true);
var intersectedZone = First(Intersects($feature, myFeatures));
return intersectedZone["District_N"];
Since it worked yesterday, it's been published to a map service and is working fine in a web map. Also, in ArcGIS Pro, I have other Arcade Expressions using this some configuration with Portal and it works wonderfully in ArcGIS Pro (unless I open the expression and try to validate or click OK.
The error is "Invalid expression. Error on line 1. General evaluation error." Sadly line 1 is a comment
//GET THE INTERSECTING LAYER
If I put a "return;" before the Intersect function, it validates. So I know this is the error. Plus, I can also do "return Count(myFeatures);" before the Intersect function and it'll validate and work.
Why did it work yesterday and not today?
