Hi @johnny thanks a lot for your reply, indeed, database triggers seems to be the way to do it.
Now, there is an other concern, basically, on a car, the revision happens every 10.000 Km and the car can go let’s say to 500.000 Km.
Witch makes 50 different alerts to set if you go 10K per 10K. Is it a way in your opinion to just make it happen every 10k instead of set it individually?
The condition on the trigger on the Car/Vehicle data type should be:
Car before’s Mileage / 10000:floor < Car now’s Mileage / 10000:floor
That essentially puts each 10,000 km into a unit and returns yes when the car before the change was below a 10,000 km threshold, and the car now is above a 10,000 threshold.
What I mean @georgecollier is that the calculation has to be in between 2 different metrics.
Miles - on one hand
Last revision - on the other
I don’t want the alert to be displayed every 10.000 Miles, i want the alert to be displayed 10.000 Miles after the last revision, depending on the car’s growing mileage.
So basically, there is the “Car Miles” witch is growing with time, but the “Last Revision field” is not.
So how to trigger the alert 10.000 km after the Last Revision, but depending on the Mileage?
(If you still struggle to understand, i can go through the workflows and explain deeper).