https://www.esri.com/arcgis-blog/products/ops-dashboard/announcements/introducing-data-expressions-i...
For yours, you mention that there are shared fields between them, Job ID and status. Is the category field shared between them as well?
Here's what the expression could look like:
// for single-layer services, the layer index is almost always 0, but we will explicitly state the index for each, in case you have other values. the index number corresponds to the URL, /FeatureServer/X, X being the index
// list out all layers to add to dashboard
var layers = [
{id: 'itemid of layer', idx: 0},
{id: 'itemid of second layer', idx: 0},
// and so on
]
// establish output schema
var out_dict = {
fields: [
{name: 'jobID', type: 'esriFieldTypeString', alias: 'Job ID'},
{name: 'status', type: 'esriFieldTypeString', alias: 'Status'},
{name: 'category', type: 'esriFieldTypeString', alias: 'Category'}
],
geometryType: '',
features: []
}
// loop through our layers and push features into dict
for (var l in layers) {
// get featureset
var fs = FeatureSetByPortalItem(
Portal('your portal URL'),
layers[l]['id'],
layers[l]['idx'],
['job_id', 'status', 'category'],
false
)
// push features into dict
for (var f in fs) {
Push(
out_dict['features'],
{ attributes: {
job_id: f['job_id'],
status: f['status'],
category: f['category']
}}
)
}
}
return FeatureSet(Text(out_dict))
With so many layers, this is likely to be a long-running expression. I would pause and test it every few layers as you build the layers array, to see if the performance becomes an issue for you.
- Josh Carlson
Kendall County GIS
