|
| Posted 1/9/2007 6:12:56 AM |
| | | Ever wanted to call a javascript client function after all records are processed by an ActionPage? Use the javascript code below in your action page.
And set the ClientSideSaveSuccessHandler in the ActionPage code to "SaveSuccess"
function SaveSuccess(result, objecttype, objectid)
{
//alert(result + ';' + objecttype + ';' + objectid);
//
// TODO: check/count if all records were processed?
//
// call javascript method in opener after all records are processed
// _currentRecord and _recordCount are set by c360 in the ActionPage if (_currentRecord == _recordCount - 1)
{ // _opener is set c360 in the ActionPage if (_opener && _opener.test) { _opener.test(); } } return "";
};
NOTE
The test method should be declared in the javascript of the ASP.NET page that executed/openend the action page!!
@Jeremie
I get the impression that the objecttypecode parameter passed to the "SaveSuccessHandler" is set with the index in of the selected record in the grid....shouldn't this be the objecttype? ("0" as ObjectType in ActionPage.SaveData revisited?)
|
|  Posted 1/9/2007 9:46:15 AM |
| | Ever wanted to call a javascript client function after all records are processed by an ActionPage? Use the javascript code below in your action page.
And set the ClientSideSaveSuccessHandler in the ActionPage code to "SaveSuccess" Excellent tip! Thanks for sharing. I get the impression that the objecttypecode parameter passed to the "SaveSuccessHandler" is set with the index in of the selected record in the grid....shouldn't this be the objecttype? ( "0" as ObjectType in ActionPage.SaveData revisited?) You are correct, this is very similar to defect number DE1010 which you had discovered and we fixed in version 3.0.7. I have reported this new problem as defect number DE1523. However, since it may already be too late for the January 23 release. I will try to convince our dev team to fix this defect but I can't guarantee.
|
| |
|