web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Default value in date ...
Microsoft Dynamics AX (Archived)
Unanswered

Default value in date effective table for ValidFrom is not equal to session date time

(0) ShareShare
ReportReport
Posted on by Oleg Abapolov 39

Hi,

Let's assume that session date and time (DateTimeUtil::getSystemDateTime()) is different from system date (DateTimeUtil::utcNow()), for example the user sets new session date and time in SystemDate form

Screen-Shot-2015_2D00_03_2D00_16-at-15.08.19.png

When a new record is created in date effective table, then system date and time is used as default value, for example in DirPersonName table:

Screen-Shot-2015_2D00_03_2D00_16-at-15.08.36.png

However when the user clicks "Today" button then session date is set to ValidFrom field:

Screen-Shot-2015_2D00_03_2D00_16-at-15.08.46.png

It is somehow inconsistent, isn't it?

Could you please explain or suggest the reason behind such behaviour?

Thank you.

*This post is locked for comments

I have the same question (0)
  • dolee Profile Picture
    dolee 11,279 on at

    Hi Oleg,

    It looks like when Microsoft design the Date Effective Pattern, they decided they will use the actual datetime as default value.

    On the other hand, the date picker control has been there since many versions ago and the logic it uses is to look at the system datetime for "Today". Note that this control is something general for the whole client UI, so one can argue using the system datetime make more sense.

    In fact, there are other examples of such inconsistency as well. In a date control, the Date picker would pick the system datetime as "Today", while typing "t" > "tab" would gives you the actual datetime.

    Having said that, there must be someway for the user to choose the session datetime over actual datetime, otherwise the whole session datetime concept would be meaningless. Having a context sensitive date picker would create other kinds of confusion as a different "Today" will be used in different context and users might not understand the reasoning behind it.

    I'd say the current state is just a result of a group of seemingly unrelated decisions made at different times. However, if you have ideas that can improve user experience, definitely let Microsoft knows! =]

  • Oleg Abapolov Profile Picture
    Oleg Abapolov 39 on at

    Hi Dominic,

    Thank you very much for the reply.

    As the user I would expect using session date and time in all cases described:

    Today button, "t"+tab, default values for "date time state enabled" fields, etc.

    Based on functions cross-references it seems that my expectation is right:

    systemDateGet() - is used about 4000 times

    today() - about 500

    DateTimeUtil::getSystemDateTime() - about 500

    DateTimeUtil::utcNow() - about 500.

    However I do agree with you that most probably it is a set of unrelated decisions made.

    Best regards,

    Oleg Abapolov

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans