Hi all
Is there an explanation as to why assignment form outputs the message that 2 records committed even when doing a correction.
Message is -- FRM-40400: Transaction complete: 2 records applied and saved.
This feature of the assignment form seems to have an effect on any personalzation for eg : the condition 'WHEN-VALIDATE-RECORD' for ASSGT . When we set it up the trigger fires twice as there is always ' two' records to save on this form , any way round this , we only want the message to fire once ."
Thanks in advance
Vin

Hey Vin,

I had a dig around with this a while back- it's worth setting up a SQL trace to show you which tables have been updated in your own environment, but generally a correction on the assignment form updates per_all_assignments_f and per_periods_of_service. I've still no idea why per_periods_of_service is updated, as it seems to simply enter a new row, with exactly the same details as the previous one- perhaps someone else on here may be able to shed some further light..
Cheers
Simon

Presuming you've verified that there are no hooky customisations lurking on that form (either trigger based or user hook based)?
As a work-around, base your trigger code within a package, and have a package global variable.
Set it on first fire, and execute the code you want to run.
On second fire check to see if global is set (as it will remain persistent in your session memory). If its set, unset it and do not run the code.