topic Re: Feature not being created due to date field type in ArcGIS JavaScript Maps SDK Questions

Feature not being created due to date field type

Aeseir — Fri, 12 Aug 2022 04:23:30 GMT

Very simply I am trying to enrich a feature on creation by adding a createdAt datetime. However when I add this additional attribute, the feature does not get created.

I am learning how to add this attribute so that in future I can filter features by date and/or create heatmaps.

Code is very simple:

//feature layer setup const featureLayer = new FeatureLayer({ geometryType: "polygon", title: "Test Feature Layer", source: [], objectIdField: "UniqueId", spatialReference: { wkid: 102100 }, fields: [{ name: "id", alias: "UniqueId", type: "guid" }, { name: "description", alias: "Description", type: "string" }, { name: "createdDate", alias: "CreatedDate", type: "date" }], outFields: ["*"], popupTemplate: popupTemplateDetails, }); // adding feature var polygon = this.addPolygonGraphic({ id: e.id, description: e.description, createdDate: new Date(2019, 4, 25) }, rings); this.areaFeatureLayer.applyEdits({ addFeatures: polygonFeatures }); function addPolygonGraphic(attributes: { [key: string]: any }, rings: any) { var polygon = new Polygon({ rings: rings, spatialReference: { wkid: 102100 } }); var graphic = new Graphic({ geometry: polygon, attributes: attributes }); return graphic; }

What am I missing here?

Re: Feature not being created due to date field type

JohannesLindner — Fri, 12 Aug 2022 06:27:46 GMT

I don't know about the Javascript API, but in Arcade (which seems to share a big part of the feature set declaration with the JS API), you have to supply an integer (epoch, number of milliseconds since 1970-01-01) to the date field.

This is how it would look in Arcade:

Number(Date(2019, 4, 25))

Re: Feature not being created due to date field type

Aeseir — Fri, 12 Aug 2022 06:45:13 GMT

That was it, i had to convert it to number, which is annoying

Re: Feature not being created due to date field type

Aeseir — Sun, 14 Aug 2022 06:22:17 GMT

@JohannesLindner how do you manage the time offset due to timezones, epoch ignores timezones

Re: Feature not being created due to date field type

JohannesLindner — Mon, 15 Aug 2022 05:41:32 GMT

Again, no idea how to do it in the JS API.

Arcade has the functions ToUTC() and ToLocal(), which convert your local date to UTC or vice versa.

Re: Feature not being created due to date field type

Aeseir — Mon, 15 Aug 2022 06:07:09 GMT

See that's how i started with initially, passing the date format, but for some reason it is not accepted by argcis. Only epoch number is accepted.

Re: Feature not being created due to date field type

DavidNyenhuis1 — Thu, 15 Jun 2023 19:26:46 GMT

With this week's update to Arcade and ArcGIS Dashboards, date fields in feature set constructors now just work. You no longer have to wrap dates with Number() if you pass the dictionary into the FeatureSet() function (which as of this release accepts a dictionary as opposed to only text based JSON).

Instead of:

return FeatureSet(Text(dict))

Do this:

return FeatureSet(dict)

Learn more in this blog post.

NOTE: For Enterprise users, this update is targeted for 11.2