Access SharePoint List from Subsite without code (FINALLY)
Facts:
- CQWP browse for source data always allows selecting input data from root site collection (even in subtites), and throughout the site collection (data from any of the sites and subsites)
- Creating a data view web part in a site that is connected to a list from that site, it is possible to export that web part, sharing that list and xslt by importing it to another site
- Disabling UAC sucessfully removes a lot of persmissions issues when using CA and using REST connections (if enabled, running IE as admin is required for admin options to not appear greyed out)
- Customized external content (old "Connect to another library...") would be best done with external data sources with REST (also available in Foundation)
Check Jasper's Blog
http://sp2010a/teamsite/_vti_bin/listdata.svc
To retrieve information for a single list
http://sp2010a/teamsite/_vti_bin/listdata.svc/Contacts
Or perhaps just a single contact (in this case, the one with ID = 1)
http://sp2010a/teamsite/_vti_bin/listdata.svc/Contacts(1)
•QueryString parameters for REST
•$filter
•$expand
•$orderby
•$skip
•$top
•$metadata (will bring back all the XML metadata about the object. Think of it like WSDL for your REST call)
Solve rest error:
Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
http://blog.hompus.nl/2010/03/26/could-not-load-type-idataserviceupdateprovider-when-using-rest-with-sharepoint-2010/
- CQWP browse for source data always allows selecting input data from root site collection (even in subtites), and throughout the site collection (data from any of the sites and subsites)
- Creating a data view web part in a site that is connected to a list from that site, it is possible to export that web part, sharing that list and xslt by importing it to another site
- Disabling UAC sucessfully removes a lot of persmissions issues when using CA and using REST connections (if enabled, running IE as admin is required for admin options to not appear greyed out)
- Customized external content (old "Connect to another library...") would be best done with external data sources with REST (also available in Foundation)
Check Jasper's Blog
http://sp2010a/teamsite/_vti_bin/listdata.svc
To retrieve information for a single list
http://sp2010a/teamsite/_vti_bin/listdata.svc/Contacts
Or perhaps just a single contact (in this case, the one with ID = 1)
http://sp2010a/teamsite/_vti_bin/listdata.svc/Contacts(1)
•QueryString parameters for REST
•$filter
•$expand
•$orderby
•$skip
•$top
•$metadata (will bring back all the XML metadata about the object. Think of it like WSDL for your REST call)
Solve rest error:
Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
http://blog.hompus.nl/2010/03/26/could-not-load-type-idataserviceupdateprovider-when-using-rest-with-sharepoint-2010/
Comments
Post a Comment