return to correct page after insert/update/delete

Not sure how to word this, (which may be why I can't find it in the forum).

Say I have 200 entries on my table.
On my DA results page, my results are paginated in 10's

If I choose to update record 34, this will be on page 4 of my results.

On editing my record, my dataasist server behavior redirects to the results page, but always to page 1, whereas I want to go back to my original page

I looked at the option to pass the original querystring, but this doesn't seem to work.

I think I have a hand coded a workable solution, if i set the querystring to a session variable on the results page and use this to append the redirecturl on the insert/edit/delete page, it seems to work OK

Is this something which has to be hand coded, or am I just missing something obvious form the DA interface?

This is something my client has been asking me to fix for ages, so a solution would be greatly appreciated - I was about to post the same question. I have a site that has around 400 products at any one time and updating them is a nightmare. At the moment I use the back button in the menu bar to take me back to the right spot in the results listing.

I have a hand-coded solution if you are interested.

However, personally, I decided I only want to use this approach for a record edit/update.

For an edit, the number of records stays the same, so the pagination is bound to be identical.

For an insert, there will be an additional row in the recordset after insertion, which MAY occur on the next page

Similar issue for a deletion

Here's what I did

On my results page, just before my doctype declaration, i set a session variable equal to the querystring

<?php
if (!session_id()) session_start();

  $_SESSION["QueryString"] = $_SERVER["QUERY_STRING"];

?>

On my update page, at the bottom of the update trigger code, i replaced

if ($WA_keepQueryString && $WA_redirectURL != "" && isset($_SERVER["QUERY_STRING"]) && $_SERVER["QUERY_STRING"] !== "" && sizeof($_POST) > 0) {
      $WA_redirectURL .= ((strpos($WA_redirectURL, '?') === false)?"?":"&").$_SERVER["QUERY_STRING"];
    }

with

if ($WA_keepQueryString && $WA_redirectURL != "" && isset($_SESSION["QueryString"]) && $_SESSION["QueryString"] !== "" && sizeof($_POST) > 0) {
      $WA_redirectURL .= ((strpos($WA_redirectURL, '?') === false)?"?":"&").$_SESSION["QueryString"];
    }

Yes, that's going to be the easiest way to solve the problems.

the issue is that the page number is not passed to the update page as a part of the query string, so cannot be passed back after the update is complete.

I will log this as a bug in the bug base to have it investigated for a future update.

Thanks very much - will give the handcoding a try

Just a brief update on this. I used the code detailed above for returning to the correct place in the results table from my detail page. So on my results button I would put the following link: <a href="items_Results.php?<?php echo $_SESSION["QueryString"]; ?>#<?php echo $row_WADAitems['ItemID']; ?>.

I've got a subscribers table and I'm trying to get the update behaviour to return to the correct spot in the subscribers table by using the same method. However I can't seem to get the syntax right. I've used the code snippet as detailed for the update behaviour. Should this line remain the same?: $WA_redirectURL = "tbl_contacts_Results.php";
as it doesn't seem to work - thanks for your help.

you will need to edit this line:
$WA_redirectURL = "tbl_contacts_Results.php";


to pass the querystring session and the recordnumber:
$WA_redirectURL = "tbl_contacts_Results.php".$_SESSION["QueryString"]."#".$row_WADAitems['ItemID']."";

the code for the record number will be different for your page, it will be the same variable used to pass the record number to the update behavior.

Thats great - thank you Jason, just didn't have quite enough dots and "" - just for the record I needed to add '?' after the .php to make it work.

Thanks folks :) I too just had a client ask me to do the very same thing.

Sorry bout that, forgot the question mark. glad to hear it is working.