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
Related
I am beginning sharepoint development and have some quick questions concerning basic terms.
How do i find out whether a particular site is a site collection, or a site JUST BY THE URL? Is their a powershell command to do this?
I was creating some sites in sharepoint. Some sites were appended with /sites/sitename whereas others were just under the base url of sharepoint. What is the difference between the 2? AND, how do i recreate the ones under the sites node? For some reason, I cant find the option to create under the sites node again. Please explain this concept as all msdn tutorial are very confusion for beginners like me. Those are good once you get the hang of basics.
Please provide an analogy how to understand web app, site collection, site, web site, etc.
Is there a way to use NEWFORM.aspx for a document library instead of UPLOAD.aspx?
The Site collection is at the root level of your Web application.
So http://abc.com/ => Site collection
Using Powershell, open the Sharepoint Powershell prompt and run Get-SPSite to get all Site-Collections
the /sites/ is called as a managed path
It can be defined in the Central Administration for every web application.
The option to select the /sites will be available only when you create the second site collection under the Web Application (The first one take the / by default.)
Have a look at Technet Article
document library is for uploading file, not for storing user submitted data, for that you need to create a list
1) Document Set is used in cases where multiple documents have the same properties, its like putting all these documents in a folder and then providing attributes to that folder which are in turn applied for each document in that folder.
In your case, if all the files have the same values for the 8 fields then the document set is the correct way to go.
2)If there is additional metadata associated with the files then these can be added either to the content type (eg. document or document set content type) or to the columns in the library itself, you dont need to create a separate list for holding that data. Adding data to the content type ensures consistency across all the document libraries within that site collection, adding columns to the library affects only that library.
I have a website in Sharepoint 2007 (it is a publishing portal).
I want to create a site with more specific info than what it comes with Sharepoint.
You know, when you create a new site, the only info you can enter is title and URL.
I would need an image and a description.
The solution is not a custom list, because i need to have pages inside and other lists.
How can i extend this site list?
Write an application page or web part that creates the new site. Programmatically update it with what users enter in your custom form.
Creating the site
The SPWebCollection.Add() method creates the site from a site definition. Create a custom definition that includes the site columns, content types and lists required. These will then be created as part of the site.
Further customisations
This won't perform all customisations however - for the rest develop a feature receiver. On activation it will run any arbitrary code on your new site.
For example as you are using a publishing site, retrieve its default page with the DefaultPage property. This is an SPFile object which has an Item property that can be edited like any other SPListItem. Update the image field and description field for the item based on its content type. The page will then render these properties.
All of the above can be wrapped in an SPLongOperation for a nicer user experience.
There are other options as well, for example the SPWebProvisioningProvider. The two separate steps above of creating a site definition and activating a feature receiver could be tied into one with this.
There is more information on the above techniques (plus others) and their pros and cons in part 3 and part 4 of this series by Raymond Mitchell.
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..
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.