topic Re: Arcade Data Expression Not Creating FeatureSet in ArcGIS Dashboards Questions

Arcade Data Expression Not Creating FeatureSet

HaydenHarrison1 — Tue, 18 Feb 2025 19:16:38 GMT

Hello,

I am trying to create a data expression that would query a feature layer containing work orders (WOs) and determine how many "outstanding" WOs (aka older than 7 days) we've had over the last 5 years. I am able to loop through the dataset and get a count of all outstanding work orders but can't get it to create a featureset to use in a chart widget on a dashboard. The output is a blank featureset. Version context: enterprise portal is on 11.1. Any input is greatly appreciated.

Re: Arcade Data Expression Not Creating FeatureSet

KenBuja — Tue, 18 Feb 2025 19:32:34 GMT

You're building the array of filterFeatures, but you don't add that to finalTable.

var finaltable = { fields: [ { name: "WorkOrderID", type: "esriFieldTypeString" }, { name: "InitiateDate", type: "esriFieldTypeDate" }, { name: "ActualFinishDate", type: "esriFieldTypeDate" }, { name: "DaysToComplete", type: "esriFieldTypeInteger" } ], geometryType: "", features: filteredFeatures }; return FeatureSet(finaltable);

Re: Arcade Data Expression Not Creating FeatureSet

HaydenHarrison1 — Tue, 18 Feb 2025 19:59:46 GMT

Hi Ken,

Thanks for responding. When I edited the code to your above suggestion, I got an invalid parameter error.

Re: Arcade Data Expression Not Creating FeatureSet

KenBuja — Tue, 18 Feb 2025 21:01:02 GMT

I ran your code using my own data and discovered that you have to convert daysToComplete to an integer (line 34). Otherwise, it ran correctly (with some field name changes and a different minimum days)

Re: Arcade Data Expression Not Creating FeatureSet

HaydenHarrison1 — Tue, 18 Feb 2025 22:28:35 GMT

Changing the daystoComplete worked! I can now see the featureset. However, the date fields aren't populating. Thoughts?

Re: Arcade Data Expression Not Creating FeatureSet

KenBuja — Wed, 19 Feb 2025 14:05:01 GMT

The field names in the dictionary ("startDate" and "endDate") are different than the attributes in the array ("InitiateDate" and "ActualFinishDate")

Re: Arcade Data Expression Not Creating FeatureSet

HaydenHarrison1 — Wed, 19 Feb 2025 15:06:31 GMT

Unfortunately the feature set will not populate unless I use "startDate" and "endDate".

Re: Arcade Data Expression Not Creating FeatureSet

KenBuja — Wed, 19 Feb 2025 15:26:11 GMT

What I mean is that the attribute keys have to be the same as the Dictionary field names to be mapped properly

attributes: { WorkOrderID: Text(wo["WorkOrderID"]), // Ensure it's string InitiateDate: Date(startDate), ActualFinishDate: Date(endDate), DaysToComplete: Floor(daysToComplete), OBJECTID: (wo["OBJECTID"]), Description: (wo["DESCRIPTION"]) } -------------------- fields: [ { name: "WorkOrderID", alias: "Work Order ID", type: "esriFieldTypeString" }, { name: "InitiateDate", alias: "Initiate Date", type: "esriFieldTypeDate" }, { name: "ActualFinishDate", alias: "Actual Finish Date", type: "esriFieldTypeDate" }, { name: "daysToComplete", alias: "Days To Complete", type: "esriFieldTypeInteger" }, { name: "Description", alias: "Description", type: "esriFieldTypeString" }, { name: "OBJECTID", alias: "OBJECTID", type: "esriFieldTypeOID" }, ],