RowInsert
When a user adds a row of data to a scrollarea or grid, the Component Processor generates a RowInsert event.
Important things to Note
- Rowinit is also executed when a row is inserted, so write specific code for the inserts. If the RowInit and RowInsert code is same, the code will run twice.
- The RowInsert event triggers PeopleCode on any field on the inserted row of data.
- Do not use a warning or error in RowInsert.
- RowInsert does not trigger PeopleCode on derived/work fields.
- RowInsert PeopleCode can be associated with record fields and component records.
RowDelete
The RowDelete event is initiated whenever a user attempts to delete a row of data from a page scroll area. Use RowDelete PeopleCode to prevent the deletion of a row (using an Error or Warning statement) or to perform any other processing contingent on row deletion.For example, you could have a page field called Total on scroll area level zero whose value is the sum of all the Extension page fields on scroll area level one. If the user deleted a row on scroll area level one, you could use RowDelete PeopleCode to recalculate the value of the Total field.
- The RowDelete event triggers PeopleCode on any field on the row of data that is being flagged as deleted.
- RowDelete does not trigger PeopleCode on derived/work fields.
- RowDelete PeopleCode can be associated with record fields and component records.
- When the last row of a scroll area is deleted, a new, dummy row is automatically added. As part of the RowInsert event, RowInit PeopleCode is run on this dummy row. If a field is changed by RowInit (even if it’s left blank), the row is no longer new, and therefore is not reused by any of the ScrollSelect functions or the Select method. In this case, you may want to move your initialization code from the RowInit event to FieldDefault.
RowSelect
The RowSelect event is initiated at the beginning of the component build process in any of the update action modes (Update, Update/Display All, Correction). RowSelect PeopleCode is used to filter out rows of data as they are being read into the component buffer. This event also occurs after a ScrollSelect or related function is executed.
- A DiscardRow function in RowSelect PeopleCode causes the Component Processor to skip the current row of data and continue to process other rows. A StopFetching statement causes the Component Processor to accept the current row of data, and then stop reading additional rows. If both statements are executed, the program skips the current row of data, and then stops reading additional rows.
- PeopleSoft applications rarely use RowSelect, because it’s inefficient to filter out rows of data after they’ve already been selected. Instead, screen out rows of data using search record views and effective-dated tables, which filter out the rows before they’re selected. You could also use a ScrollSelect or related function to programmatically select rows of data into the component buffer.
- In RowSelect PeopleCode, you can refer to record fields only on the record that is currently being processed. This event, and all its associated PeopleCode, does not initiate if run from a component interface.
- In previous versions of PeopleTools, the Warning and Error statements were used instead of DiscardRow and StopFetching. Warning and Error statements still work as before in RowSelect, but their use is discouraged.
- RowSelect PeopleCode can be associated with record fields and component records.
The post Understanding Peoplecode – RowInsert, RowDelete, RowSelect Events appeared first on Everything Technical.