-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date Range domain does not work with the Geoform #524
Comments
I'll look into it. I see the issue. thanks |
Hey @zhujingx do you have a public service or something I can use to replicate this bug? |
Sorry, my service is private. Could not share, very sorry for that.
From: Matt Driscoll [mailto:[email protected]]
Sent: Wednesday, January 25, 2017 7:11 PM
To: Esri/geoform-template-js <[email protected]>
Cc: Xia, Zhujing <[email protected]>; Mention <[email protected]>
Subject: Re: [Esri/geoform-template-js] Date Range domain does not work with the Geoform (#524)
ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails.
Hey @zhujingx<https://github.com/zhujingx> do you have a public service or something I can use to replicate this bug?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#524 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ASx7IwnF7hYC4IzDJx7nb4oSqBhCSjLuks5rV-SRgaJpZM4Lc4d6>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a Date field with the Date Range domain set up. It can not display in the geoform for this field.
ESRI support said that there is a bug BUG-000080907: If a date field uses a date range domain in an attribute table, the date is displayed in a UNIX format when editing the date field in a feature service in the ArcGIS Online map viewer.
I am wondering that is there a work around to modify the geform template code to let the date range work.
Thanks
Zhujing
The text was updated successfully, but these errors were encountered: