OFS - local field assigning through validation

Dear Colleagues,

I have an issue in which I can't assign value into a local field through validation routine when using OFS.

I'm importing application information from external source(e.g. .xls). My application version has a validation routine in which it takes COMI of one local field and generates another value into another local field. It's fine when such process is from higher local field into lower, but when I assign a value from let's say from 3rd local field of my application into 4th, that value doesn't get written into the record.

Thank you in advance!
Aziz

Moreover I created empty version with just single validation, yet it doesn't function. I am new to T24 so I assume it's a bug or some system process takes place and it clears my local field values which are higher from the local field in which validation takes place.

Did also debugging all the way till eg. R.NEW(AC.LOCAL.REF)<1,FIELD.POS>= R.VALUE
R.NEW has my dedicated value.

One more fact! My validation routine can assign values to any fields except ones which are higher(local fields)

Thanks for your response.

Yes I pass limited local field values through the script and then generate OFS message with routine for a version of my application. That version has validation routine to one local field which generates another value for another local field that comes after.

In general I want to populate values from one local field(imported) into others local fileds that come after in senquence, through OFS.

Just to try I made empty version with just one validation field. Lets say for account application I have validation for field LOCAL.REF:4:1 = 222 and i want to assign 2223 to LOCAL.REF:6:1

OFS.SOURCE just has settings for description, source type = globus, log file dir, log detail, in queue dir and syntax type = ofs. Field val is empty...

T-24 R08.001

I think, if you set OFS.SOURCE feild val = blank then t24 won't validate the ofs message. So, your VERSION validation routine is not executed.

As I know, common variable COMI will populated value during "validating" record in VERSION validation routine.

Thanks Tjondro and Jpb! Indeed, the field.val was to be YES.

Sounds like quite weired...
I am facing the same issue, with newer T24 Release (R.10). Obviously, I have setup FIELD.VAL=YES in F.OFS.SOURCE but my validation routine didn't executed.
Do any suggestion, what should I need to be check ?

Finally, actually validation routine being executed but there is logic to skip/return all during validate or input. This validation routine only accepted form HOT.FIELD browser.