Can we use 'CrudOperation' variable with 'before command'

If it’s purely validation driven, any particular reason you want to do it at CRUD action level rather than just override Check_Upate___ for ContractItem ?

Hi ​@SimonTestard 

The requirement is to check multiple records together before saving, for example the sum of a specific attribute of all the records should be 0.

Check_Upate___ executes separately for each record that was modified if I understand.

Ok that makes sense.

If your code note working ? It should be, it follows the right syntax

Although I’m not used to Stringify so I can’t tell you much about that use, if you trace/log/error output the  CContractItemString within the action, do you have the data you need for your validation?

I get the values of the attributes of the records that I pass to CContractItemString.

But the CrudOperation value is null inside the bulkexecute’s conditional statement.

And considering its a bulk execute (some records might be create and some might be update), I tried passing the CrudOperation value into CContractItemString as well hoping it would pass the type of action for each record, but on the plsvc side I still have it as null.

so what you’re saying is that if instead of calling the PLSVC action, just as a test, if your command calls, let’s say, info("${CrudOperation}"), the resulting toast has no value ?

If that is the case, have you tried with a regular execute rather than bulkexecute ? If CrudOperation has a value with execute but not bulkexecute, it might simply not be compatible with bulkexecute ?