compare a new record with exisitng valid Time StateTable records

(1) Share

Report

Posted on by Lakshmi Karambakkam

1,307

Hi,

I have a table with Valid Time State field type set to Date. I have to write x++ logic to to validate ValidFrom and ValidTo of a new record with the exsiting records and get a validate info if date range is not appropriate rather than system throwing an error.

Lets say, I have three records for an item and vendoraccount with different date ranges.

ItemID	VEndAccount	ValidFrom	ValidTo
00008754	100098	12/1/2019	12/1/2021
00008754	100098	12/2/2021	5/6/2023
00008754	100098	5/7/2023	Never

I have to add a 4th record for the same itemid and vendoraccount with validfrom and validTo.

Is there a function or a keyword that checks right away than manually checking using a while loop query?

while select validtimestate(dateNull(),dateMax()) setuptable
where setuptable.VendAccount == this.VendAccount &&
setuptable.ItemId == this.ItemId
{

}

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Martin Dráb 239,880 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

You said you want to "check right away than manually checking using a while loop query", but what is it that you want to check? Why can't you use the normal behaviour of the framework? Which ValidTimeStateMode is your index using?

Was this reply helpful? Yes No
Lakshmi Karambakkam 1,307 on at

Like
a
(0)

Report
Copy link

Link copied!

ValidTimetateMode is set to No Gap.Since I am writing this code in Data Entity during import project so the records in import file are inserted into the valid Time State table.

Was this reply helpful? Yes No
André Arnaud de Cal... 305,946 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Lakshmi,

What would be the difference for someone using your data entity if you have your own validation or the system default validation? In case there are wrong dates provided, the system should prevent inserting the records anyway. Do you want to present another error message compared to the standard error? If so, why should someone using your entity get a different experience compared to standard data entities having date effectiveness enabled on the underlying tables?

Was this reply helpful? Yes No