locked
No item exists error when I click edit link in DataView

    问题

  • I modified my Customers DispForm.aspx to include a CustomerOrders

    and CustomerReservations DataView. Both of my DataViews show the 

    edit and delete links for the Orders and Reservations related to a Customer.

     

    Both of the DataViews work fine, except for one strange problem in

    CustomerReservations DataView.  When I open Customer Item that

    has an id of 300 or less, I can click edit and delete and I see the expected results.

     

    EDIT RESERVATION ITEM FAILS WHEN THE CUSTOMER ID > 300

    When I open Customer Item with id greater than 300, I click delete on the CustomerReservation DataView

    and it works. However, when I click edit on a CustomerReservation Item, I get this error.

    No item exists at http://site/subsite/Lists/Customers/DispForm.aspx?ID=450It may have been deleted or renamed by another user.

     

    So I copy and paste the http://site/subsite/Lists/Customers/DispForm.aspx?ID=450 link on IE and

    it displays the Customer Item with no problem.

     

    Now is this a SharePoint bug, or is there something wrong with the way I added

    the DataView on SharePoint Designer?

     

    Any insight into this matter is greatly appreciated.

     

    • 已移动 Mike Walsh FIN 2009年2月4日 5:59 DVWP q (Moved from SharePoint - Development and Programming to SharePoint - Design and Customization)
    2007年10月26日 2:56

答案

  • I've had similar problems, when going from a list view, to an item display view, to an edit view.  essentailly it doesn't like the ?ID= all of a sudden, if you use a different query string identifier...  ?CustomerID=450 for example it will work fine - very odd.

    For sharepoint own views that will pass an ID to your form, you can have two parameters to catch this ID as well.

    not sure why it happens but there doesn't seem to be many other peeps having this trouble when i googled.

    Pete
    2008年2月29日 11:42

全部回复

  • I've had similar problems, when going from a list view, to an item display view, to an edit view.  essentailly it doesn't like the ?ID= all of a sudden, if you use a different query string identifier...  ?CustomerID=450 for example it will work fine - very odd.

    For sharepoint own views that will pass an ID to your form, you can have two parameters to catch this ID as well.

    not sure why it happens but there doesn't seem to be many other peeps having this trouble when i googled.

    Pete
    2008年2月29日 11:42
  • It doesn't work !

     

    2008年3月31日 16:01
  • I have exactly same error here.

    When i try to use url addres in new IE tab, it is working fine.

     

    Has anybody found some solution ?

     

    2008年4月8日 7:55
  •  

    I've had similar problems. That error appear when we have more than a dataview on a page
    2008年4月23日 8:46
  • Thanks dude.

    You are right. Never put the same name to your parameters what sharepoint is using as internal or display name.
    Give your own name then you never get this problem.

    like:- Instead of  http://server/Pages/Publish.aspx?publishFileName=folderName/subfolderName/filename&ID=12

    use this  http://server/Pages/Publish.aspx?publishFileName=folderName/subfolderName/filename&PublishItemID=12

    Hope it will help you.

    Kuldeep kadyan
    2008年8月19日 9:00
  • I had the same problem as well, I was able to Edit a WebPartDataView with a parent ID of less than 10.  Otherwise I would get a "No item exists ..." error for those with a parent ID of greater than 10.

    I was able to narrow the scope down, to the "dvt_1.rowedit" template.  (Search for xsl:template name="dvt_1.rowedit"). 

    Turns out, after I removed the <SharePoint:FieldDescription tags, the edit worked perfectly!  Only 1 of my fields had a description, but still, it worked for some but not all.  After removing the FieldDescriptions, it worked perfectly. 
    2009年2月3日 18:22
  • Data View Web Part questions go to Design/Customization not Programming.

    Moving this.
    WSS FAQ sites: WSS 2.0: http://wssv2faq.mindsharp.com WSS 3.0 and MOSS 2007: http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 and MOSS 2007 Books (including foreign language titles) http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/V%20Books.aspx
    2009年2月4日 5:59
  • Something else to try if you are still having this problem: I had 2 XSLT DataView WebParts on a WebPart page in SharePoint. Each was looking at a different document library. Links for each document would work fine, but when I would hover over a document and click "View Properties" in one of the webparts, it tried to redirect me to a list item in the other list! What gives?!?! After hours of painstakingly comparing the two webparts and trying to find out the common thread, I stumbled on this nondescript call: ctx.ctxId = In both webparts, this value was the same. When you look at the javascript and ID nomenclature of the HTML contained within, this value is used to differentiate Javascript objects from one webpart to another. So for example: One of the objects is an IFrame. Its name is not "FilterIframe". It is "FilterIframe". When SharePoint's javascript calls are made, this number is used to find the IFrame of the webpart for which the call was intended. So, when I found out 2 of these webparts had the same ctxId, I just took the XSLT of one, pasted it into Notepad, and replaced with a . Pasted the webpart back in and all is well! Cheers, Jeremy http://www.budnack.net/Lists/Posts/Post.aspx?ID=22
    2009年10月16日 0:48
  • I have a custom aspx page that is using the query string parameter "ID" to pass the ID of an item in a SharePoint list to display on the custom page.  Randomly (and perhaps only in FF on OSX) I'm experiencing the following error.

    No item exists at http://www.site.com/Page/customviewpage.aspx?ID=52.  It may have been deleted or renamed by another user.

    I've found KB article KB972225 that discusses the perils of using the query string paramter "ID" with the dataview web part and was wondering if others thought the problem might also apply to a custom aspx page.  Perhaps others have experienced a similar problem?

    Thanks...Russ
    2009年12月1日 17:56
  • Guys, as strange as it sounds, but sharepoint does not like you to use internal columns like the ID in the querystring for your custom needs, change the querystring parameters;s name to something else like a BuildingId and give it a try again and it will work it everything else is fine. Muzammil Mohammed http://muzms.blogspot.com
    2009年12月31日 17:57
  • Hi,

    In my case i have my custom page which is set through Designer when clicked on Edit Item, in short i have set my own edit page through Desginer. Page has user control on that page which shows listitem data

     

    Now Initially things were working well when clicked in Edit, it was redirecting it properly. but for certain account when the user click on the edit icon of default sharepoint view. For certain items it throwing the same error "No Item exists". I have check the permission also for the particular user on the same item, it is showing proper. Even  i am not using any ID column.

    I don know things were baehaving properly to certain count of items after which for certain set of items  it starts failing. We have WSS 3.0 Service Pack1 installed on the staging server. However I am not able to reproduce the same on Local Envioronment and my local environment has WSS 3.0 Service Pack 2.

    2010年3月30日 11:17
  • Hai Thanks for ur comments...
    2010年6月8日 6:42
  • I had the same problem as well, I was able to Edit a WebPartDataView with a parent ID of less than 10.  Otherwise I would get a "No item exists ..." error for those with a parent ID of greater than 10.

    I was able to narrow the scope down, to the "dvt_1.rowedit" template.  (Search for xsl:template name="dvt_1.rowedit"). 

    Turns out, after I removed the <SharePoint:FieldDescription tags, the edit worked perfectly!  Only 1 of my fields had a description, but still, it worked for some but not all.  After removing the FieldDescriptions, it worked perfectly. 

    I know this an old thread and the error has been associated with the ID query string, however this solution worked for me.

    I use custom web part pages for my display forms and they contain several data view web parts that display child lists filtered by a lookup column.

    When I started getting this error upon editing these child list items from the custom display form, removing the <SharePoint:FieldDescription> tags worked for me as well.  Thanks!

    2010年8月22日 17:33
  • I cant believe that deleting the Descriptions just worked.

     

    Thanks Brent

     

    J

    2011年2月2日 3:06