As a User I want to define the Date Data entry format, so that a person filling out the Date Data field in Edit Contents mode is only required to enter dates in format / granularity required, rather than full date, hour, minute, second, milisecond.
This will make it easier for users to fill out Date Data fields when only date, or only hour is required.
JJ O'Brien
| Hosting platform | Server |
Requireing he time or at least just hitting the time value is confusing to the users. I agree that a flag to include or not include time would be helpful
Attachments Open full size
There could be a flag on the existing Date Data macro to ignore the users's time so the value is that is set if more literal. Use Date Only Yes/No. If Yes, then the data is set and used by reports and report info like previously, save as date as the user submited as the CST/CDT time. If No, then perform timezone conversions and save the data with resprect to the server time and adjust for the user time zone. Changing the overall behaviour of this macro after it has been used and implemented for years and years is really causing major issues in our system, and we don't have to consider all time zones.
This flag would emilinate the need for a new macro and provide an option for the new time zone adjustments to be considered or not. Adding a new date macro would be a major, several month transition in our expansive integrated system. Where we can set a flag and leave the underlying infrastructure in place.
Attachments Open full size
maybe also investigate defaulting the time to a value that is not a boundary condition for day. maybe noon although it seems like that might have caused problems before.
Attachments Open full size