We're publishing layers to our open data portal that have Date Only field. However, these don't show up in the table view for users -- we have to direct users to download the CSV to access these fields.
An example:
- https://data.detroitmi.gov/datasets/detroitmi::business-licenses-current/about is the open data portal page
- https://services2.arcgis.com/qvkbeam7Wirps6zC/arcgis/rest/services/bseed_active_business_licenses/FeatureServer/0/query?outFields=*&where=1%3D1 is the feature service, which shows the "expiration_date" field .. but this doesn't appear on the Hub Site in either the table view or the column list
Why does this data type remain unsupported? When should we expect Hub to support this data type?
Hi Everyone! I know this forum is a little older, but I wanted to jump in to let y'all know that there is an Enhancement logged on this issue to allow "Date Only", "Timestamp" and "Time" fields to appear in ArcGIS Hub datasets.
This enhancement is currently listed as, "Under Consideration", which means that members of our development team have reviewed this request, and are further considering implementing it.
Since enhancements are ultimately decided on by our development team, they need user traction and visibility to make their way to becoming an implemented feature.
If anyone on this forum ever has an Esri Support ticket on this issue, please ask the analyst you are working with to attach your case to the following enhancement (ENH-000176852) to increase its visibility further.
Thank you all for bringing attention to this, and fingers crossed this will be considered going into the future! 🙂
I don't think all ESRI apps support the date only or time only field schemas yet. They're introducing it in more apps as the development cycle moves on, but you'd have to upgrade to whatever version it's implemented in. At least that's my experience. Generally AGOL gets updates first.
unfortunately, no. Esri doesn't seem to particularly care about this aspect of Hub any more
Hi @jmcbroom I seem to be having the same issue. Just wondering were you able to get an answer from ESRI support or find more information about getting around this bug?
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.
