Date only Field won't display in ArcGIS Experience Builder Tables

[ColinRichardson]

Hello,

I am trying to create an experience builder application and am having issues with displaying my date fields in the tables within experience builder. My date fields have a lock by them when I open the table in Arcgis Online, map viewer, as can be seen in the photo below:

In experience builder when I create a table from the same feature, I don't even have the option to display the dates field.

The only way I could find to actually display the date field in an experience builder table was to upload the field as a date and let the program assign a time. However the time doesn't make any sense for this data as it is related to samples for days, times aren't recorded. I've tried uploading the excel file directly and changing the date field to a string data type but arcgis online will automatically assign a time and I can't assign a date only field when uploading directly because of limitations to that function.

Any help or guidance would be much appreciated been stuck on this for a bit now.

[Elizabeth_Burniston]

@EJCarter - Thank you SO MUCH for posting this work-around!! I used it today and it worked perfectly! 

[AlexandHall95]

Hi,

Is this also true of Dashboards? 

ESRI's guidance documentation seems to have become extremely hard to use and fragmented across an endless number of individual guidance web pages and community forum posts. This should be made very clear that the Date Only type is NOT compatible with most ESRI web applications, or it should have been only put into production when this issue was resolved. 

I feel like the basic product level has massively declined compared to other web based geospatial systems in recent years.

[JoeStefanoni]

My issue is that in Notebook I am not able to create a feature class with date fields when the original data had date only fields even though I specify that that is the field type I want.  Is there a solution to this problem?  When I run the Export Features tool and use the same data set and specifications it works but when I take that same python script and put it in Notebook it doesn't work.  Why would ESRI include this new field type before it was compatible with all ESRI products?