cancel
Showing results for 
Search instead for 
Did you mean: 

Change default value from 0:00 to 8:00 in Date/Time attributes

Author Name: JAN ZACEK

Hi,

in most case default value 0:00 in Date/Time fields does not make sense. It would be very beneficial, if each of these fields can have own default value preset to meaningfull 8:00 or 9:00 based on which time Organization starts their business.

Thanks,

Jan

Status: Planned

As a workaround today, javascript can be used to set the default value of the date time field onload(). We, however, are tracking this request and will consider adding to our future roadmap.

Thanks,

Neerja, PM, Microsoft 

Comments
D365Ideas_Admin
Regular Visitor
Status changed to: Planned

As a workaround today, javascript can be used to set the default value of the date time field onload(). We, however, are tracking this request and will consider adding to our future roadmap.

Thanks,

Neerja, PM, Microsoft 

n2
New Member
Or 12:00 noon GMT so that the date field does not change when viewed in Time Zones around the world.
D365Ideas_Admin
Regular Visitor
Or the start/end of the current user's own specified working day from their settings, in their own time zone. I see this most likely to be used for setting default due dates on activities, especially as the default filters for the associated activity views no longer include items with no due date (eg "next 30 days" does not include blanks at the top, like it always used to). Default value for the time component should be specifiable per field, just as for a bit field. Perhaps this could be like currency precision - choose a type (system pricing setting, currency, or specify). "Use user's working day", "Specify a local time" Likewise, settings for a default date for the same datetime field would be great, maybe specified as an offset from current date, "default default" of 0. I can't see why you would want negative numbers, but someone somewhere will, I am sure. So maybe we have: Default date: "none" | "specify offset" > [-9999 to 9999] Default time: "none" (not available if date offset is specified) | "use current local time" (combined with date offset for eg 24 hours from now) | "use start of user's working day" | "use end of user's working day" | "specify local time" > [00:00 to 23:59] So now you can combine these for things like: "any date but always 08:00 until overwritten", "tomorrow at start of business", "day after tomorrow at same time as (ie 48 hours' time)" "a week from today by close of play", "28 days from now at 12:00 noon" The defaults should be honoured when activities / records are created by other means, especially workflow (as long as the value is not specified in the workflow as of course it could be)
D365Ideas_Admin
Regular Visitor
Ideally I think this would just store date ONLY, and not even HAVE a time associated with it. Alternatively, allowing admins to turn off local/UTC correction would effectively always display the same date, but it really should just store a date ONLY - no time at all. Barring that there needs to be a way to prevent a date field from being timezone-shifted.
D365Ideas_Admin
Regular Visitor
We do this via JS Code. Maybe not supportet. But it works.
JoeNewstrom
Advocate I
I saw the MSFT Product Team's response that this is not on the roadmap. I love Dynamics (esp. the 2013 release). That being said, significantly lower quality CRM-lite systems (cough-ACT-cough) provide this functionality, and provide the time portion of a datetime as an auto-filling combo-box control. I would ask as a customer that this be revisited, along with the Service Calendar. Between the clunky datetime fields and the Service Calendar, the OOB scheduling is virtually unusable as a field service company. Fixing the issue in this thread and bringing across the SharePoint calendar list control type would do the trick (or something close to it). This was a major sticking point to user adoption and made it hard to convince our business peers to jump on the Dynamics bandwagon with us.
D365Ideas_Admin
Regular Visitor
Agreed that instead of defaulting the time component, the Date attribute should have an option to enable/disable UTC conversion. Much like number fields have min/max values, strings have max length or formatting, date should have UTC conversion opting.
D365Ideas_Admin
Regular Visitor
Thank you for your feedback. This is a great suggestion, and we will consider this in our roadmap. thanks Anusha Shankar