Users will see an error message, but will not be directed to the offending field on the grid.

Customer use case:

We have a custom form for users to request item, add or update.The form has 2 tabs – Item Details and More Info.We have written PeopleCode to validate and throw error if some of the fields are blank.Those fields CAN be initially saved as blank. They are not mandatory on the form. Users are allowed to leave them blank at that point of the business process.This is a request form. Those fields are required at the time of submission of the form, which is done by clicking on a submit button.By clicking on SUBMIT, PeopleCode fires to validate fields. If the offending field sits on second tab of the grid, SetCursorPos should set focus to that field and then an error message would be given to the user.Problem is, SetCursorPos is not setting the focus to the field. Rather, the system stays in the first tab (Item Details) and doesn’t automatically navigate to the second tab (More Info) to set the cursor on the error field.