Hello,
That is correct that by default, the calculated fields are not reflected in database.
If you want to store some value in such field, you will need two things:
- processing callback, to calculate the value of the field and set the value (on actions add and edit)
- use a calculated field that will force RB to create field in database to store the value for it - you can do that through the param for calculated field:
'param'=>Utils_RecordBrowserCommon::actual_db_type('text',16)
If a calculated field has database field created along with it, you can:
- set the value using the processing callback
- use that value in display_callback
- use that field in other RecordSets
An example module that creates calculated field with database field is Premium/Projects/Tickets - the Ticket ID field.
Kind regards,
Arek