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

Notifications

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) / AX2012 Do not allow Da...
Microsoft Dynamics AX (Archived)

AX2012 Do not allow Dates to overlap - time effective framework

(0) ShareShare
ReportReport
Posted on by Shashi s 1,203

In the Valid Time State/Date Effective Framework, is it possible that overlaps are not allowed.

i.e. if a record exists for the date range 01-March-2012 To 10-March-2012

And if the user enters a record with the date range 01-March-2012 to 12-March-2012, Ax should not allow this.

Currently it lets the user to save the record and updates the existing record to 01-March-2012 to 05-March-2012

*This post is locked for comments

I have the same question (0)
  • Muhammad Usama Aziz Profile Picture
    Muhammad Usama Aziz on at

    At the table where you have enabled Date Effective framework, go to the Indexes node, select the index which acts as Date Effective index and change the ValidTimeStateMode to NoGap.

  • Shashi s Profile Picture
    Shashi s 1,203 on at

    But that will still change the Previous record as per the explanation. Im trying to lock it so that any other existing records will not be affected

  • Muhammad Usama Aziz Profile Picture
    Muhammad Usama Aziz on at

    when your are updating or creating the record, change the update mode to correction. it will automatically adjust the gap with the previous record.

  • Shashi s Profile Picture
    Shashi s 1,203 on at

    I think you have misunderstood my question.

    I dont want any of the existing records to be affected.

    I might be trying to achieve something this framework was not built for.

  • GeneM Profile Picture
    GeneM on at

    Shashi,

    From the following AX 2012 Help topic on MSDN....

    http://msdn.microsoft.com/en-us/library/gg843767.aspx

    "EffectiveBased – forces the update process to switch to CreateNewTimePeriod for each row that spans the current date-time; otherwise to switch to Correction."

     

    Or from the following white paper:

    http://download.microsoft.com/download/4/e/3/4e36b655-568e-4d4a-b161-152b28baaf30/using_date_effective_patterns_ax2012.pdf

    "EffectiveBased:
    When updating a valid time state table in EffectiveBased mode, if the record being updated is a current record, the record is updated in CreateNewTimePeriod mode. If the record being updated is a future record, the record is updated in Correction mode. If the record is a past record, the record cannot be updated.    "

     

    I am not certain I understand the precise question. Maybe you want to keep the current record unaffected by automatic adjustments to ValidFrom and ValidTo? Perhaps the following use of the ::EffectiveBased enum element might be added to what ever code is at issue:

    xrecMyTable.ValidTimeStateUpdateMode(ValidTimeStateUpdate::EffectiveBased);

     

    Thank you.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans