Is there a way to inherit list items down to a sub-site from a sub-collection in Windows SharePoint Services 3.0 SP1?
We'd like to have a list of contacts available at a site collection level and have those inherit down to a list at a site level. The sub-site level would then be able to have contacts specific to itself along with any contacts created in the parent site. Is that possible?
Lately I've been handling requirements like this using jQuery. Two web service calls to get data from the current and parent sites, then merge and display the data client side. It won't be a standard SharePoint list view, but you can get pretty close if that's what you're looking for.
I have an example of something similar on my blog:
http://tqcblog.com/2009/05/04/sharepoint-discussion-with-jquery/
The simplest idea I can think of is to use a dataview webpart to show the list items in the parent site and another for the child site.
Having the inheritance relationship between list as you imagine, would be really quite cool, but it is definitely not out of the box functionality.
Related
i'm using Sharepoint 2010 and i want to create a List in a new Site, which contains Lists from the other sites.
Like a Global Overview.
Our problem is that we're using several sites with Ticketsystems. So i want to create a global list which contains all tickets from all other sites. (For sure just if they got rights to the Ticketsystem).
Is there a way to do this?
Regards
Alex
You can easily create a ticketingsystem in SP2010 with the following steps:
1. create a content type for the ticketsystem
2. add an itemreceiver to the content type
3. create a list for the ticket system
4. add contenttype binding to bind the content type to the list
5. deploy the list to the rootweb as well as all the subsites by adding the list through a webtemplate for instance
The itemreceiver you add should be an itemadding which would place a newly created ticket in the subsite also on the rootweb level. This would allow you to have all the tickets on the subsites and one allcontaining list on the rootsite level.
As far as I know there is no generic way of mixing references from another list in a new list.
You can either integrate and copy list items from your ticket systems into a "central ticket system" or create a custom control that reads from all ticket systems and displays them in the blend you like.
There is custom development in either way.
Begin by having a look at the Data View Web Part
http://office.microsoft.com/en-us/sharepoint-designer-help/display-data-from-multiple-sources-in-a-single-data-view-HA010099144.aspx
http://www.learningsharepoint.com/2010/10/16/create-dataview-webpart-in-sharepoint-2010-tutorial/
There is also the Content Query Web Part
http://msdn.microsoft.com/en-us/library/ff650512.aspx
The SPSiteDataQuery class lets you run a CAML query for all lists/libraries in a single site collection. It's pretty trivial to tie that to an SPGridView control to get a ListView-like user interface.
Internally this is what the Content Query Web Part users, so it has many of the same limitations.
Here's a reasonable example
i'm new to SharePoint, and i'm working with sharepoint 2010.
I'm trying to create a webpart on SPdesigner that holds a XsltListViewWebPart
which is linked to a custom library i created in the Site Collection.
I want to list all the documents related to current user from the all sites
under the site collection.
to do so i set the DataSourceMode from "List" to "CrossList"
but then the webpart doesn't show any document as seen in the image below
(its like there is a line but the data is not showing..)
Does any one know what the reason for this?
How can I fix it to work so the webpart will list all docs from all sites in collection?
First, is there any reason why you don't use the out of the box Relevant Documents Web Part?
I don't think the xslt List View Web Part works in crosslist mode. What you'll need to do is use a Data View Web Part.
I am developing a sharepoint 2010 project.
I want to restrict users view on lists based on their identity. (e.g. the branch of organization they work in, but in fact the ristrictions can be more complicated).
What solutions do you recommend?
With out of the box features this is not possible. You can go to great lengths to remove the list's view selectors and other navigational elements that let people cruise around a the schema and metadata for a list but it is not a security mechanism.
If a user has read permissions to an item, they'll have read access to all the fields of that item.
There is an outside chance that it you disabled all RPC mechanisms, SOAP, RESTful web services, Client Object Model and the office clients that you might be able to claim this as a security mechanism. If you don't there will always be a way around your "security" scheme.
This feature can't be implemented by SharePoint by now and I think neither for the next version
You can use a third part tool to achieve it, such as BoostSolutions' Column/View Permission or LightningTools' DeliverPoint
BTW, I work for BoostSolutions and I mentioned our own product because it works for your issue. Hope it helps :)
create sharepoint groups based upon your requirement or diffrent type of user base and accordingly give them rights may be item level or on complete list
and while doing these things just go through the following posts
http://blogs.gartner.com/neil_macdonald/2009/02/25/sharepoint-security-best-practices/
http://weblogs.asp.net/erobillard/archive/2008/09/11/sharepoint-security-hard-limits-and-recommended-practices.aspx
Not 100% sure on SharePoint 2010, but definitley for SharePoint 2007, there is not a way to do this, especially if the views are corresponding to security requirements on the columns users are able to see.
One way to work around this is have the list be not accessible by users, and then have code logic allow for access to the data creating the different "views" on the data in something like a Web Part. The downsides to this is search becomes an issue (since the data is hidden) and having multiple "views" of the data (if necessary) is also another item to work through.
I know its a very old question but posting it as it might help someone.
There is an work around to do it as described here
I find it easier, if possible, to create the view and lock it with the filters on the list settings page.
For example, I have a list of employees that includes their employee IDs. I use that list on other pages to gather data in other webparts. So I filter the employee list to [ME]. So the data is available to the page needing it to filter others and they cannot see anything else.
Now, what about the person who needs to manage that page? I create a view, call it HR. That view can see everything. Then I export that webpart with that list view on it through the designer. I then delete the HR view from the employee list.
This leaves no way for anyone to switch views and see everything again. I create a webpart page for the person who manages it, and I upload that webpart and set the view of the webpart to HR. In the end, I have a page that I lock down instead of trying to lock down views or list permissions separately.
Would you be able to have two lists that are joined. One that all users have access to and another that only certain people have access to, and then join them? Then maybe the people that don't have access to the other table it doesn't pull the information? Not sure, but I'll try that out later today.
I'm very new to SharePoint, so apologies if this sounds a little basic.
I want to create a List in SharePoint that is just purely URL links, but then make it available to every site collection that we will create.
Once this list is created, I need it to display in a webpart (like that standard 'links' webpart). I guess I will need to create a Feature, so that it can be activated at Site Collection level.
Any ideas how this can be achieved please?
Thank you all kindly in advance, Ash ;-)
I did something similar - but I created it as a Web Part with it's own security trimming. I covered some of the basics here:
http://www.codersbarn.com/?tag=/webpart
What you would need is a view on your list of links (that view will display the content of your list). Have a look here for more details on List View Web Parts. Once you figure out how to create it and what you want in your view, coding it shouldn't be too hard (You can either use SharePoint Designer on your site to create the view you want and then reverse engineer it into code using SPSource or you can create it from the schema.xml of you list).
You should note however, that with WSS you will not be able to view the content of a list on another site collection (i.e. you can only views of your list on the site collection where the list was created). Cross-site list views are a lot more complex to implement (you can buy components that do it though). I'm not sure how MOSS deals with cross-site list views but if you use MOSS, you should make sure that you can do it before you start developing your view.
EDIT : I would definitely go with what IrishChieftain suggested if your list isn't too complicated and has a structure that won't change much. Dealing with cross-site list views is a pain.
Is it possible in a SharePoint 2007 list (MOSS, though I don't think that this is Enterprise Edition) to allow users in one SharePoint group to edit values in some fields and users in another group to edit values in the other fields?
From all the searching I've done, this does not appear to be possible, so as a fallback I'll accept answers that suggest the best way to accomplish something like this (e.g. maintain the items in separate lists, linking them by ID).
I do not have access to Central Admin, but I do have Full Control of the site. Also, this site was not configured for custom code, so besides changing list settings (and site settings) I can make changes via SharePoint Developer (but not Visual Studio).
A big THANKS in advance!
Steve
You are correct that it's not possible to set field-level permissions without custom code. Furthermore, you're on the right track thinking separate lists, though you should be aware that SharePoint list lookups are a rather weak correlation. Usable, but not exceedingly robust.
For presenting the combined data you'll want to look at SharePoint Designer's joined subviews.
Have a look at Displaying SharePoint Fields by Permission Level by Laura Rogers. This is an approach that uses SharePoint Designer.
Also see the SPListDisplaySetting CodePlex project. This is a site collection feature that needs to be installed so may not be an option.
You can customize Edit Forms for SharePoint 2007 Lists (EditForm.aspx).
With custom list definition and custom edit form you can write code to check the user and show different fields depended on the users permissions.
'a' workaround to get this functionality is to change the content type associated with a list item using workflows.
Like so:
User creates list item in content type A (limited fields).
Workflow starts, changes to content type B (all fields).
Admin gets notified, opens listitem, fills out additional form fields.
And so on..