Stump the Panel » Site Managers and Site Collection Managers

After edit of a list item -> Return to "launching" web part page

(6 posts)

  1. Magnus
    Member

    Hi,

    I have an issue regarding user friendliness when using list view web parts. To see information in the list it's fine, but when it comes to editing, or rather after editing you're directed to the source list rather than back to the web part page that "launched" the edit properties window. Alright, you can navigate backwards through two clicks back on the browswer but is there a more elegant way to make ShP remember where the edit window was launched from and upon finished editing return to that page?

    Our installation is WSS 3.0.

    Best regards
    /Magnus

    Posted 3 days ago #

  2. Eric Truchon
    Member

    Hi,

    WebParts are a view over lists. When the modification is done, it's done on the list, so when the modification is finish, you return back from where the modification start, meaning you go back to the list.

    This is out of the box way, sorry.

    Eric

    Posted 2 days ago #

  3. ewnash
    Member

    If the web part in question is a listview then Eric is right, you don't have many options. If however you were to convert the listview to an XSLT data view with Designer then you have more control over link behavior and might be able to include a Source tag in the link. I haven't tried that trick specifically but if SPD doesn't scare you off then it might be worth a shot.

    On the other hand, is the current user experience sufficiently painful to make the extra effort worthwhile? My users seem to find breadcrumbs pretty intuitive and I'm careful to design the navigation so that they can always find their way back at a glance.

    Posted 2 days ago #

  4. bburke
    Member

    Using SharePoint Designer, convert your list view to xslt (right-click the view and select "Convert to XSL data View").

    Locate the link to the EditForm.aspx, add the follwing to the link:

    onclick="GoToLink(this);return false;" target="_self"

    It should look like this:

    href="Lists/SupportRequest/EditForm.aspx?ID={@ID}" onclick="GoToLink(this);return false;" target="_self"

    Posted 2 days ago #

  5. Magnus
    Member

    I've created a dataview on a separate web part page (not at the default.aspx) of a list in ShPD, created filters to only display relevant information. One of the columns is a look up field to connect to a product. This field has a hyperlink to display the related product information (to DispForm.aspx). This is where the navigation becomes an issue. User look at the dataview on a web part page, clicks on a link to display product info in list B and then upon close he ends up in an unsorted default view of the product list (list B). I can't see how I could use breadcrumb navigation to help my users.

    Attacking through ShPD seems fun, however my coding skills are limited... can't really find where the EditForm is launched from. Also I tested more and found that web parts with lists at the default.aspx have the functionality I want! Which is after displaying or editing I'm returned to the web part page where I started.

    In a list the title field is a link to DispForm.aspx the related code is:

    Code doesn't seem to be displayed correctly... removed it.

    /Magnus

    Posted 1 day ago #

  6. ewnash
    Member

    @bburke- Thanks, this worked perfectly and I've added it to my black bag.

    @Magnus- When I tested this it worked fine. If you need to show code snippets in this forum just enclose them with the backtick (`) character, typically on the same key as the tilde (~) at the upper left of your keyboard.

    This shouldn't require much in the way of coding skills; just open the page in Designer, use the Split view and when you highlight one of the hyperlinked values in your web part the code view should put you in the right spot. Then just add bburke's snippet and you should be fine.

    Also, I see why the navigation wouldn't be intuitive, as it looks like you're linking to an item in a separate list. In that case your original request makes perfect sense and you're right that you couldn't fix the problem even with the best possible navigation design.

    Posted 1 day ago #

RSS feed for this topic

Reply

You must log in to post.