Hello experts,
I'm using JDev 11.1.1.7.0
This thread is based on a series of implementations that started with :
How to update detail table cascaded LOV when the Master table's LOV changes?
The Idea was to update rows In the detail table "VendorPrices" when the "MesureId" attribute changes in the master table "Products".
@"Timo" suggested to use an end of valid date (like it's used for history columns) which i already have so i decided to use a flag column instead.
Now The Only thing left was to add a validation to the detail table so we don't end up with duplicate valid vendorPrices.
Which lead us to:
EO Validation rule NotIn Query Result Backfires.
Now we are here**.**
In the detail table EO I added a validation method to prevent the user from inserting a row with values that exist in another custom VO that i created.
The custom VO "MyVendProdValidator" uses this query:
SELECT VENDOR_ID ,PROD_ID
FROM VENDOR_PRODUCTS VP
WHERE
VENDOR_ID = :P_VendId AND
PROD_ID = :P_ProdId AND
IS_VALID = 0
Now when i open my app the first view that shows is ProductsView ... i choose a product from the table and then click Edit that navigates to productNew.
When try to insert a new row with a value that exists and click save the validation works and shows a message preventing me from saving until i correct the value and choose one that doesn't exist.
Now the problem is when i correct the value and click save it navigates to the ProductView as it should.
But when i choose a product again and insert the wrong value it doesn't show the message and navigates to the ProductView as if nothing happened.
The record doesn't get commited in the database but it don't let the user know that this happened which i think makes the validation partially useless.
This view is a part of a task flow:
This is the message (Is this how it should look like??):
So any ideas how to fix this?
Thanks for your time.
Gado