Write accessor methods in your class to handle the Delete boolean flag. In your action class, you can add logic to delete the record after the form is mapped to the intake object. This way intake easily maps the checkbox for processing purposes, but doesn't really affect your object.
For the multiple records/rows, you just repeat the $intake.mapTo() in your template, and the form processing in your action. You have to supply an array form field outside of intake that contains the querykey's for the records to be processed. I am pretty sure you can find more detail about this in the turbine-user archives. Chris > -----Original Message----- > From: Neil Stevens [mailto:neil.stevens@;firstlightassociates.co.uk] > Sent: Thursday, November 14, 2002 5:20 AM > To: Turbine Users List > Subject: Can some intake fileds have no mapToProperty > > > Hi, > > Do all fields in a group have to be mapped? I added a 'Delete' (boolean) > unmapped field to my group, without setting the mapToProperty, > but I get an > error :- > > ERROR -- Property, Delete for class, ....PriceCategoryLevel could not be > found in the turbine log. I don't want this field mapped! > > I am just trying to have multiple rows in one form of a table that can all > be updated or deleted in one hit. > > Should this have worked ? > > Neil > > > -- > To unsubscribe, e-mail: > <mailto:turbine-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:turbine-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org>
