I have seen something about this in the past, but have been searching for hours and not found what I need.
Problem:
when multiple users are entering records into an "editable" grid, the records are "jumping'. ie they enter record, and when they "save" the record appears to be lost to them (it's really just on the LAST page).
I have tried setting the fields in the Grid Update to only add new record on last page. However, that only puts it at the bottom of the CURRENT page. I cannot seem to force the new record to FIRST move to Last page, THEN add new record.
I have tried doing an ajaxcallback in CanNewRowsShow with variations of the following: (I have also tried other Client Side, as well as some ServerSide, all to no avail)
REturn this javascript from callback: (which the 'alert' works, but doesn't seem to do anything prior to 'alert')GoToLastPage= "var rowNum = GRID1_GridObj._rowsInGrid; {grid.Object}.setSelectedRow(rowNum);alert(rowNum);"
OR embedding this directly in the callback and only returning 'alert' [again, alert then works but does not go to last page]
AND I have also tried just returning :
gotolastpage="{grid.Object}.pageNavigate('last');"
AND I have tried just putting {grid.Object}.pageNavigate('last'); directly in CanNewRowsShow, in which case
This just seems like an everyday thing that people would want to do (go to last page before doing new enters) and should not be this difficult.
It's probably very simple, but I just can't make it work.
Problem:
when multiple users are entering records into an "editable" grid, the records are "jumping'. ie they enter record, and when they "save" the record appears to be lost to them (it's really just on the LAST page).
I have tried setting the fields in the Grid Update to only add new record on last page. However, that only puts it at the bottom of the CURRENT page. I cannot seem to force the new record to FIRST move to Last page, THEN add new record.
I have tried doing an ajaxcallback in CanNewRowsShow with variations of the following: (I have also tried other Client Side, as well as some ServerSide, all to no avail)
REturn this javascript from callback: (which the 'alert' works, but doesn't seem to do anything prior to 'alert')GoToLastPage= "var rowNum = GRID1_GridObj._rowsInGrid; {grid.Object}.setSelectedRow(rowNum);alert(rowNum);"
OR embedding this directly in the callback and only returning 'alert' [again, alert then works but does not go to last page]
<<%js%
{grid.Object}.pageNavigate('last');
%js%
{grid.Object}.pageNavigate('last');
%js%
AND I have also tried just returning :
gotolastpage="{grid.Object}.pageNavigate('last');"
AND I have tried just putting {grid.Object}.pageNavigate('last'); directly in CanNewRowsShow, in which case
1)FIRST the new record row is added to users current page
2) THEN the pointer is moved to last page.
2) THEN the pointer is moved to last page.
This just seems like an everyday thing that people would want to do (go to last page before doing new enters) and should not be this difficult.
It's probably very simple, but I just can't make it work.
Comment