The FeatureTable widget displays NULL date values as 12/31/1969 (i.e., 0 in Unix Time, adjusted for my local time zone).
Is there a workaround for this?
I have created a Plunk that demonstrates this issue.
FWIW, per this thread, Kelly Hutchins says that dateOptions was disabled but never responded when prompted on an update about the matter.
Thanks for looking into this.
Jeff,
I see what you are saying.
I checked out featureTable API Reference and looks like there isn't anything to control the display if the date value is null-able.
There is something called dateOptions but there has to have a date to use that and format it.
Let me see what I can do.
Thanks,
Akshay
The issue is on the client side. The map service is correctly returning null. It's the FeatureTable widget that is converting the null values to 1/1/1970 UTC.
Hi Jeff,
I believe they have fixed this bug in Server 10.3 and above. There are few things you might want to check.
1) your server version
2) Check if the field is set to not null-able.
3) If you have imported the date filed for older shapefile into database and published it to server.
If anything doesn't work then try using a string field instead of Date.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
