Error on grid sorting

Hi all,

I have a grid (named grdEfolder) in a form, with ordering fields enabled.

When i click on a column of the grid on web client, instead of ordering the rows, it show me an error:

"An error occurred in this process. Please report the problem to your administrator."

In ELOG table was logged this error:

EDescription=Failed to execute deployed method 'WhenUserSelectsRow', using entity 'grdEfolder'.

EDetails=Failed to execute deployed method 'WhenUserSelectsRow', using entity 'grdEfolder'.
The given key was not present in the dictionary.

The grid is populated from Query business object.

The fields of the grid are mapped to the properties of Business Object.

There isn't any BO property or grid field name with duplicate name.

On the "When user select row" section of grid, there are two assignments:

Local.SelectedFolderID=Fields.grdEfolder.SelectedRow["EFOLDERID"].ToString()

Local.SelectedEmapName=Fields.grdEfolder.SelectedRow["EMAPNAME"].ToString()

Any help would be appreciated

thanks

Max

Find more posts tagged with

BPM

Comments

Jerome_Pearce

The problem is caused by using an unsupported method to get the grid data. You need to use the ProcessContext.UserInput[n] approach, bearing in mind it takes the column index from the BO, not the grid itself.

What you are doing is making the client try to get the values from the selected row when the selected row does not exist. Just one example (of so many) why you need to use the supported methods..

BPS_Pid

Thanks, with this approach (ProcessContext.UserInput[n]) it's OK.

It would be useful to have an "access by name" approach for BO Properties and grid fields.

Now i've a strange behavior:

if i click on a column header to sort the grid, it seems that the "When user selects row" script" is executed.

But i haven't selected any row!

The grid has "is dependent" and "has dependants" both checked, because i need to populate it after a click on a button and populate more grids (and other fields) when i select a row on the first grid.

It could be a 9.2.1 bug?

thanks