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