Is it possible to find what new pages / lists / listitems have been added to the intranet site and generate a report on daily basis ?
We have to implement this on sharepoint 2010 and also on sharepoint 2013 websites.
We are using C#.NET.
I am aware that we can find newly created listitems by creating a listview and then sorting it by DATE as TODAY-2 where 2 is no. of days prior.
But, how can I implement same for all lists in the site?
I am doing research on the web analytics in sharepoint 2010, but this doesnot seem to serve my purpose.
Have you come across similar requirement?
I wrote you a small manual on how to create a separate ASPX-page in the _layouts folder. If something is unclear feel free to ask me in the comments of this answer.
I am assuming that you have already a solution set up for both versions SP2010 and SP2013.
Add a new ASPX-page (application-page) to the layouts mapped folder in your solution, lets name it "ViewNewContent.aspx".
In the codebehind in the page_load function, code something that loads all items that have creation date > some defined date and display them on the aspx page. Load the list using the GUID that you will pass as a Get-Parameter to the aspx-page (ViewNewContent.aspx?List={Some-GUID})
Now create a custom action that displays on all lists and redirects the user to the your page with the ListId added: ViewNewContent.aspx?List={ListId}
I hope this gives you a basic idea on how to do this.
Related
I am having problems figuring out a calendar workflow and am beginning to think what I need cannot be done w/out using .NET. I want to copy calendar items up and down between sites.
The site collection structure is Office-->Division-->Branch. There are 5 divisions under the office and multiple branches under each division. Each is a separate site with its own own calendar.
I want to populate a calendar on one site and have the item pushed up or down the site chain to another site calendar. So I need to be able to promote calendar events up AND down between calendars on different sites within the same site collection. Also, I don’t need the whole item copied. I need all fields except one because each site has its own set of check box values for one of the fields.
All my research has indicated this can’t be done without programming and I do not have Visual Studio. I have heard BCS may be a solution but am not sure that we have it. We are using SharePoint 2010 Enterprise Server but many things are not available to me such as Data Sources. One recommendation I got was to have one site (office) and put everything below it as site pages. So divisions and branches would just be pages, not separate sites. However, this seems like it would get out of hand quickly. Any help would be greatly appreciated.
So it looks like my site structure is not optimal as SharePoint lists and libraries do not easily flow between sites. I will need to change the structure so all the divisions and branches are site pages, not sites. This way everything will live in the same site and it will be much easier to move data around via workflow.
In this case, I won't need to move any data between calendars because now I can use one calendar for the office, divisions and branches and create different views to show the required data.
I am working on a sharepoint site and i have a number of lists which i would like to add web pages to,
my problem is that when i go to the edit page mode there is only one web part, the main zone so i can only add the pages one on top of the other
but i want to add two pages side by side' i need to add more zones (right,left etc).
is there a way to this without using the sharepoint designer? (i have problems with it since the sharepoint site is 2007 and the office i have is 2013 so i can only use the webpage for it)
Thank you very much for the help.
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 trying to show events from a calendar in the main site to a calendar in a sub-site of the main site (or vice-versa)...I can't alter any server files or use custom-built web parts...is there anyway to do this w/ OOTB moss 2007?
Altering Server files is a big no-no anyway, so that's good :-D. YOu could try using SharePoint designer to create a so-called aggregation webpart, pulling data from all sites in the site collection (which of course get security trimmed by sharepoint, so people see only what they are allowed to see).
YOu can create use a DataFormWebPart in SharePoint designer to build an aggregation webpart. This is still ootb, but allows you to configure the datasource: i.e. have the datasource query the entire site collection for calendar items, then display them in a list. Disdplay them in a "new" calendar will be a lot of work though.
There is no way to "copy" or deisgnate specific calendar items to be visible in specific other calendars, this will take custom code.
Not strictly OOTB MOSS 2007, but I recenlty wrote an article about syncing any list using a simple workflow. As a Calendar is just a list it works for that as well and it maintains the Calendar look and feel.
Check it out here, it works great and deals with attachments as well. As it is part of a workflow you can add your own logic easily, e.g. Only sync calendar events that have field 'x' set to 'y'.
I wanted to point out that RSSBus Web Part can handle a task like this with minimal code. This, although not ootb is quite simple and does not require use of SharePoint Designer.
<rsb:import lib="RSSBus.SpsOps"/>
<rsb:set attr="url" value="http://mysharepointsite/subSite/"/>
<rsb:set attr="list" value="Calendar"/>
<rsb:set attr="user" value="someuser"/>
<rsb:set attr="password" value="theirpassword"/>
<rsb:call op="spsListItems">
[[sp:name]]</br>
</rsb:call>
The code above can be placed within the RSSBus Web Part on the main site and through the use of "SpsOps" have access to all lists/items on all sites/subsites.
-S
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.