Timeline for ows_EncodedAbsUrl results in 404 Not Found
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 31, 2015 at 17:19 | vote | accept | FrobberOfBits | ||
| Mar 31, 2015 at 17:14 | comment | added | Eric Alexander | either method would work, ows_FileRef or ows_EncodedAbsUrl, the each require their own manipulation. It does give you the URL of the item, it just isn't usable in any fashion and it needs manipulated depending on what you need to do, view or edit an item. I always had to do the same thing in dataview web parts too, so it the same across all platforms, client side and server side. | |
| Mar 31, 2015 at 17:09 | comment | added | FrobberOfBits | This is sounding like a realistic solution, and yet this is CRAZY that SharePoint won't in any form just give you the URL of an item. | |
| Mar 31, 2015 at 17:09 | comment | added | FrobberOfBits |
So @PirateEric are you suggesting my best option might be to pull ows_FileRef, parse the URL to extract the proper path, then add the `DispForm.aspx?ID=" + ows_ID at the end?
|
|
| Mar 31, 2015 at 17:02 | comment | added | Eric Alexander | ows_FileRef has most of the components you'd want, which is similar to the encodedabsurl. It has the item ID and with some manipulation, you can extract the relative url out of it. Example of returned data: 4;#sites/mysite/Lists/Videos/4_.000 | |
| Mar 31, 2015 at 16:52 | comment | added | FrobberOfBits | Building the URL to DispForm is also problematic, because the list name in the URL doesn't necessarily have to be the same as the list name as returned by SOAP. Is there another parameter that would indicate the proper list URL so these DispForm URLs can be built safely? | |
| Mar 31, 2015 at 16:02 | history | answered | Eric Alexander | CC BY-SA 3.0 |