When entering data to a multi-occurence form, the displayed data - prior to data input - always displays the previous record's data. This seems to be standard Baan functionality - as an example for a type 2 form, see standard session tcmcs0118m000 (Item Signals), which behaves this way.
Having tried many UI script options (before.field, before.display, before.input, before.display.object etc.), plus having considered DAL object and property hooks ('set.object.defaults' and 'fieldname.set.defaults' are only executed for DAL.new or DAL.update, so cannot be used in this case), it seems that the standard program always reverts to this default last, after having executed everything else, prior to data entry.
Does anyone know how to initialise all data input fields as null, prior to entry of a new record in this case? (At table level, specific defaults can be set, but not blank defaults.)
Having tried many UI script options (before.field, before.display, before.input, before.display.object etc.), plus having considered DAL object and property hooks ('set.object.defaults' and 'fieldname.set.defaults' are only executed for DAL.new or DAL.update, so cannot be used in this case), it seems that the standard program always reverts to this default last, after having executed everything else, prior to data entry.
Does anyone know how to initialise all data input fields as null, prior to entry of a new record in this case? (At table level, specific defaults can be set, but not blank defaults.)