| You can sync Outlook to any list or library within SharePoint Foundation 2010 and MSS (Microsoft SharePoint Server 2010).
So the title really should be: How to integrate any SharePoint 2010 list or library with Outlook 2010.
By connecting to a Tasks List in Outlook 2010, you can aggregate all of your tasks in one place and work between applications smoothly.
1. Log into SharePoint.
2. In the Quick Launch menu, click on Tasks, located under Lists.
3. Under the List tab, click on Connect to Outlook.
4. An Internet Explorer dialog box will appear stating that you should only connect lists from sources you know and trust. Click on Allow.
 5. A Microsoft Office Outlook dialog box will appear stating that you should only connect lists from sources you know and trust. Click on Yes. 
6. When Outlook 2010 opens, you might be asked to supply your user name and password. If so, enter these in the Microsoft Office Outlook dialog box that will appear.* Remember to select “Remember my credentials”
7. In Outlook, the tasks list will appear under Other Tasks in the Tasks section of the Navigation Pane.
Note: Only the tasks assigned to you are displayed in the To-Do Tasks list and the Daily Tasks list.
| | ![]() - |
| Matthew Skinner recently spoke at the Western Carolinas SharePoint Users group last week which meets each month in Asheville. Here is the blog he wrote following that presentation on SEO.
1. How to create custom page titles.
2. How to create a custom “Description” Meta tag.This can be accomplished in SharePoint 2010 Foundation or Server.
Recommended SEO Reading: Search Engine Optimization Starter Guide - Google PDF
Google Search Example: getsharepoint.com
· Meta Title (Custom Page Title)
· Meta Description (Custom Page Description)
 Page TitleThe Title tag lets you indicate the current pages title. Out of the box SharePoint sets the site title and appends the page navigation name to the end of the site title.
<title></title>
Example: Site Title – Page Name (Western Carolinas SharePoint User Group - Home)
http://www.wcspug.org/SitePages/Home.aspx
Description Meta Tag
Out of the box SharePoint does not have a way for you to populate the page description.
If we do a search for wcspug.org we can see that there isn’t an accurate description of the site. This will lower your page ranking dramatically.
Just do a search for "To navigate through the Ribbon, use standard browser navigation keys. To skip between groups, use Ctrl+LEFT or Ctrl+RIGHT. To jump to the first Ribbon tab”
You can see there is a real need for the Description Meta Tag for SharePoint Public Facing Sites.
How to add the custom columns and code for your custom Title and Description.
*Disclaimer: Please use caution and follow these steps at your own risk – especially working with SharePoint Designer.
1. Create Site Columns: Site Settings > Galleries: Site Columns > Create
a. MetaTitle (Single line of text)
b. MetaDescription (Single line of text)
2. Add these new columns to the Pages Library
a. View All Site Content > Site Pages > Library Settings > Add from existing columns
3. Edit page meta data View All Site Content > Site Pages > Edit Properties
a. Populate MetaTitle with a unique and descriptive page title (max of 65 Characters)
b. Populate MetaDescription with an accurate description and summary of your page (max of 150 Characters)
4. Open the site with SharePoint Designer and edit the master page
a. We have to first hide the existing <asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server"/> that is in the SharePoint Title Tag in a hidden ASP Panel at the bottom of the page.
b. We will add ASP ContentPlaceHolder with a unique id
c. Add our Title and Description tags
d. Inside of our Title and Description tags we will add SharePoint:ListItemProperty tags with the columns we created earlier as the “Property”.
SEO Code Snippet:
<asp:ContentPlaceHolder id="PlaceHolderMetaTags" runat="server">
<title runat="server"><SharePoint:ListItemProperty Property='MetaTitle' runat='server'/></title>
<meta name="description" content="<SharePoint:ListItemProperty Property='MetaDescription' runat='server' />" />
</asp:ContentPlaceHolder>
 ASP Hidden Panel Code Snippet and Example:
<asp:Panel visible="false" runat="server"> Old Title tag and PlaceHolderPageTitle goes here.
</asp:Panel>
Please note! The only drawback is the next time you go to edit the master page you will need to replace Meta Description tag again before saving a new version of the master page. For some reason when you open the master page the SharePoint:ListItemProperty adds additional code that breaks the tag. So replace it with the clean code before saving the master page again.
<meta name="description" content="<SharePoint:ListItemProperty Property='MetaDescription' runat='server' />" />
| | ![]() - |
| 
On a recent project while I was building out a custom dashboard page for a client, complete with a tabbed interface with web part zones in each of the tabs. I ran across an interesting issue with the page upon its completion. Whenever the page was put into edit mode, the web part zones and all of the content in them would be stripped completely from the page.
After searching my pages code for non-terminating div tags, missing placeholders, malformed tables, and the standard "usual suspects" I was left scratching my head.
After a while I decided to try and rebuild the page using a web part page rather than a wiki as the starting point. This solved the problem immediately. It seems that in SharePoint 2010 when a wiki page is put into edit mode it automatically strips out any web part zones and its contents, it just does not like them being on the page.
While you are perfectly able to add and edit the web parts in SharePoint Designer, once you are in the browser it crosses a line that SharePoint does not like. You are not completely out of luck however. If you absolutely need to add web part zones to a wiki page, you can still edit the web part in the browser on an individual basis by clicking on "edit web part" or editing it in designer. What you cannot do, however is put the entire page into edit mode, lest your web parts vanish into thin air.
| |  Matt Metcalf - Design & Development |
| SharePoint 15 'Sneak Peek' to be presented at SHARE Conference by Microsoft Product Manager Kristina Kerr
Video Announcement: http://vimeo.com/37195263
Microsoft is aiming for a 2012 release of SharePoint 15 (codenamed SharePoint Server 15). The following new features have been rumored but not completely confirmed yet.
1. SharePoint 15 will include a new SharePoint Apps Marketplace
2. SharePoint Apps will support multi-tenant installations so that hosting providers can make available the same set of applications to multiple customers
6. Touch screen enabled: ZDnet.comSharePoint 15 Technical Preview Interoperability API Documentation:
This download provides documentation of APIs related to Interoperability with SharePoint 15.
SharePoint 15 Technical Preview Interoperability API Documentation: This compiled help (.chm) file contains reference topics focusing only on types and members that are called by other Microsoft applications. This reference does not document the full SharePoint 15 managed object model. That documentation will accompany a later release of SharePoint 15.
"Office 15” Begins Technical Preview:
Office 15 Technical Preview screenshots:
| | ![]() - |
| 
Hi Readers,
This code can be used in the Enterprise version of SharePoint. Thanks to Brandt for sharing this convenient and valuable solution.
"When creating custom Data Form Web Parts it can be a challenge to link to a browser based form. It took a while to dynamically construct but I’m offering to share it with the community."
Below is an link tag that will open a browser based InfoPath form.
<a href="{concat( ̴SITEURL ̴/_layouts/FormServer.aspx?XmlLocation=',@FileRef.urlencodeasurl)}" onclick="return DispEx(this,event,'TRUE','FALSE','{@File_x0020_Type.url}','{@File_x0020_Type.progid}','{@DefaultItemOpen}','{@HTML_x0020_File_x0020_Type.File_x0020_Type.mapcon}','
{@HTML_x0020_File_x0020_Type}','{@serverurl.progid}','{@CheckoutUser.id}','{$UserID}','{@ForceCheckout}','{@IsCheckedoutToLocal}','{@PermMask}')"><xsl:value-of select="@Distributor_x0020_Code"/>LINK TO FORM</a>
Simply replace the bold and italicized values and voila! You can link directly to a browser based InfoPath form bypassing the need to open the InfoPath application.
| |  Brandt Fuchs - Vice President of Operations |
| Here's a great blog about how sometimes it is OK to skip a step!
The reason for this post is to share my findings while testing the operation and the provided directions, on a VM mockup of the host server, where I discovered some issues that lead me to omit a certain step in the documented procedure, for reasons I will elaborate on herein. From the directions, the first step is the actual upgrade of the installed webparts and binaries. See my comments and findings explained below these instructions.
Installation Warning
Bamboo recommends performing the install during off hours or lock down the sites. Doing so prevents the software DLLs from being locked by a process. Run IIS reset and restart the timer service on all the web front end servers to release all holding processes on files and assemblies.
Attention: You must have PM Central R2.0 or higher to upgrade to PM Central R3.0 from a previous version. If you have an older version of PM Central (R1.x), contact Bamboo Support or your Bamboo Account Manager to obtain the correct prerequisite version. Upgrading PM Central directly from R1.8 is possible, but is not recommended.
These instructions are specific to upgrading to PM Central R3.0. If you upgrading to an older version of PM Central, click here to search the Bamboo Knowledge Base for documentation for the version you are upgrading to.
Required Installation Permissions:
Before you install PM Central, make sure that you have the appropriate rights. The account running the installation must have the following permissions:
- Must be a member of the local server Administrators group.
- Must have the db_owner role for the SharePoint configuration database.
- Must be a site collection administrator for each site collection where PM Central will be available. This is required to automatically activate the site collection features.
To upgrade PM Central:
1. Stop the World Wide Web Publishing Service (W3SVC).
· Select Start > Administrative Tools > Services.
· Scroll down and select World Wide Web Publishing Service.
· Click Stop.
2. From the Setup program, select the SharePoint Project Management Central core component and click Install.
3. Click Next. Wait while the wizard performs the system check, and then click Next.
 4. Select the Upgrade/Repair Existing and Install New option and then follow the installation wizard to complete the upgrade installation.
NOTE: PM Central contains approximately 33 Web Parts that need to be installed. During the repair and upgrade process, if one of the DLLs is locked by a process, the installation of that particular Web Part will fail.
My findings were that step 1. is problematic. The purpose of this step is to prevent users from browsing the site(s) potentially holding one or more PM Central .dll’s in process, locking out the installer from being able to overwrite the component during installation.
The problem I encountered during testing is that I found that if the WWW service is in a stopped state during the upgrade process, certain webparts will fail to deploy, unable to reach required sites by URL, thus invalidating the install.
I tried achieving a similar desired state by stopping the application pools as an alternative to step 1. in the Bamboo directions. This also caused the installation to fail for the same reasons.
I then attempted the upgrade installation with both the WWW Service and application pools left in a running state. This does produce a warning during the ‘System Check’ stage of the installer procedure where it tests whether or not the WWW service is in a running state. Although, I found that this warning can safely be ignored and this indeed allows the upgrade installation to successfully retract and redeploy each webpart and component during the upgrade process. During the upgrade process all sites enter a state of unavailability, anyway. This prevents users from accessing the site(s)and locking any .dll’s. You should run an iisreset before initiating the upgrade process to free up any .dll’s that may be in use. So, take note of this alternative method in case you encounter similar issues during your upgrade.
| |  Ian Banks - Systems Engineer |
| I recently worked on a site that had been upgraded from 2007 to 2010. The client said they learned so much about what they did wrong on their site. We all learn from our mistakes and experiences. The issue the client had experienced was that they spent so much time adding users to hundreds of groups that they didn’t want to have to recreate the security structure. I offered them some options; one of them was to purchase one of the migration tools on the market to do that for them. The problem is that the price is so expensive for just copying the security over to a new collection site.
I have worked with the export site in a past version and even in 2010 at a site level, but you only could backup a site and restore everything, this is not really the best way, I know you could rip out all of the lists and libraries, but really?
Along comes 2010 with PowerShell allowing a list to be exported at a granular level. Export-SPWeb -ItemUrl ( http://technet.microsoft.com/en-us/library/ff607895.aspx) This looks like a great solution for all of those times you just want the security, but wait! After trying this out I found out that users and groups were copied over to the root level, but nothing was mapped. It was half way imported. The groups and permissions were missing. So once again, back to the drawing board, do it yourself! Below is a script I created to remap, essentially re-plumb the new site to what the security structure of the original site was.
First, all of the variables are at the bottom of the script.
This is configured to run on the same server currently.
The export path can live anywhere on the machine; I recommend putting this somewhere non important.
$sourceURL = "http://intranet"
$destinationURL = "http://intranet/sites/NewSite"
$listName = "Tasks Test"
$exportPath = "C:\Users\<username>\Desktop\Temp\"
This function accepts five parameters:
SourceURL is the current site you want to duplicate the security from.
DestinationURL is the new website you want to push the security to.
ListName is the Title or display name of the list, this is not the URL name, I get the URL in the script.
ExportPath this is the path where the export file will be saved to, it is not important to keep the list file.
DeleteList I added this so you can have the script delete the list from the destination site after the sync has completed; it has a default value of true.
Copy-SiteSecurity -SourceURL $sourceURL -DestinationURL $destinationURL -ListName $listName -ExportPath $exportPath -DeleteList:$true
Here is the complete script:
Clear-Host
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
# I call this "The missing cmdlet"
function Get-SPList([string]$webUrl, [string]$listName)
{
$spWeb = Get-SPWeb -Identity $webUrl
$spList = $spWeb.Lists[$listName]
return $spList
}
#This adds the group to the current web
function Add-GroupToWeb ($spWeb, $groupName, $permLevel)
{
$newGroupAccount = $spWeb.SiteGroups[$groupName]
$newGroupAssignment = New-Object Microsoft.SharePoint.SPRoleAssignment($newGroupAccount)
$newGroupRole = $spWeb.RoleDefinitions[$permLevel]
$newGroupAssignment.RoleDefinitionBindings.Add($newGroupRole);
$spWeb.RoleAssignments.Add($newGroupAssignment)
}
#This adds the group to the site collection
function Add-GroupToSite ($spWeb, [string]$groupName, [string]$groupDescription)
{
$sourceGroups = $sourceWeb.SiteGroups
foreach($sourceGroup in $sourceGroups)
{
if($sourceGroup.Name -eq $groupName)
{
$group = $sourceGroup
break
}
}
if ($group -eq $null)
{
$newGroup = $spWeb.SiteGroups.Add($groupName, $spWeb.CurrentUser, $spWeb.CurrentUser, $groupDescription)
$spWeb.AssociatedGroups.Add($spWeb.SiteGroups[$groupName])
$spWeb.Update()
}
else
{
$spWeb.AssociatedGroups.Add($spWeb.SiteGroups[$groupName])
$spWeb.Update()
}
}
function Update-SecurityGroups([string]$sourceURL, [string]$destinationURL)
{
Write-Host "Remapping users and groups."
$sourceWeb = Get-SPWeb $sourceURL
$destinationWeb = Get-SPWeb $destinationURL
#First we need to loop though the source site and grab all of the groups
$sourceGroups = $sourceWeb.SiteGroups
foreach($sourceGroup in $sourceGroups)
{
Add-GroupToSite -spWeb $destinationWeb -groupName $sourceGroup.Name -groupDescription $sourceGroup.Description
foreach($permLevel in $sourceGroup.Roles)
{
if($permLevel.Name -ne "Limited Access")
{
Add-GroupToWeb -spWeb $destinationWeb -groupName $sourceGroup.Name -permLevel $permLevel.Name
}
}
}
$destinationWeb.Dispose()
$sourceWeb.Dispose()
}
function Copy-SiteSecurity([string]$SourceURL, [string]$DestinationURL, [string]$ListName, [string]$ExportPath, [bool]$DeleteList=$true )
{
#Get real URL for list
$listURL = "/" + $(Get-SPList -webUrl $SourceURL -listName $ListName).RootFolder
#Remove invalid characters
$listFile = $ListName -replace "[^\w\.@-]" ,"_"
$listURL = [System.Web.HttpUtility]::UrlPathEncode($listURL)
$filePath = $ExportPath + $listFile + ".cmp"
Write-Host "Exporting" $SourceURL$listURL
Write-Host "Path" $filePath
if(Test-Path -Path ($filePath))
{
Remove-Item -Path $filePath -Confirm:$false
}
Export-SPWeb $SourceURL -ItemUrl $listURL -IncludeUserSecurity:$true -IncludeVersions CurrentVersion -path $filePath -nologfile
Write-Host "Exporting complete."
Write-Host "Importing" $DestinationURL$listURL
Import-SPWeb $DestinationURL -IncludeUserSecurity -path $filePath -nologfile
#This is the line that remaps the users and groups
Update-SecurityGroups -sourceURL $SourceURL -destinationURL $DestinationURL
if($DeleteList)
{
Write-Host "Delteing the temporary list" $DestinationURL$listURL
Get-SPWeb $DestinationURL | Where-Object { $_.Lists.Delete([System.Guid]$_.Lists[$ListName].ID) }
}
Write-Host -ForegroundColor Green "Security Duplication Ccomplete!"
}
$sourceURL = "http://intranet"
$destinationURL = "http://intranet/sites/NewSite"
$listName = "Tasks Test"
$exportPath = "C:\Users\<username>\Desktop\Temp\"
Copy-SiteSecurity -SourceURL $sourceURL -DestinationURL $destinationURL -ListName $listName -ExportPath $exportPath -DeleteList:$true
# Here is a sample call to just add a user group
# Add-GroupToSite -spWeb $destinationWeb -groupName "TestGroup" -groupDescription "This is a test"
If you would like to download this script click on this link DuplicateSiteSecurity.ps1
Happy scripting!
| |  Rick Toner - Lead Developer |
| 
There are a lot of third party RSS viewing and aggregating web parts out there for SharePoint that allow multiple feeds, as well as feed selection by individual users and more, but to my surprise, there was not one that allows for filtering of the articles pulled in by the reader. The out-of-the-box RSS Viewer web part in SharePoint 2010 Server Enterprise is even more limited when it comes to configuration choices through the browser. It basically only lets you choose a single feed URL, how many articles to pull, and whether or not to show the feed titles. Keep in mind as well that there are a few different ways to filter. You could be wanting to filter out certain items, or in this case, wanting to pull in articles that match certain keywords or filter criteria.Further research revealed some external sites that do the filtering for you and then pass you the filtered list, but for an internal client site I was concerned this would not be reliable or would run into security issues or at minimum warning messages from the browser. If you are interested here is a good source of some of the most popular ways (http://www.readwriteweb.com/archives/6_ways_to_filter_your_rss_feeds.php).
Therefore, I did some further testing of how much I could customize the RSS Viewer web part through SharePoint Designer and was quite pleased with the results. By selecting the entire web part in the Design view  , the controls in the Ribbon become available.
From here you can do all the normal things you would do to lists pulled from SharePoint, including set filter criteria on specific fields.
 Remember that these criteria are extremely literal however. To be sure that all articles are pulled in that may match the criteria, you would probably want to have multiple criteria with “Or” joining them with any capitalization or spelling variations you can imagine. Since the feeds come from external sources you can’t really control how they will format certain words or where they will put them.
| |  Peter Hill - Solutions Architect |
| I recently had a project where I had to build an InfoPath form in InfoPath 2010 that had to be compatible with InfoPath 2007. The one issue I ran into was the people picker fields not working. The reason for this is that InfoPath 2007 does not have people picker fields by default. So my solution was simple; all you have to do is create a text file and insert the following code…
<Context siteUrl="http://<servername>"/>
Then save the text file out as Context.xml (and it is case sensitive).
After this you need to create a new data source in InfoPath…
Then select Receive data…
Then select xml document…
Then browse for your file and upload it. Now you should be good to go!
Your InfoPath forms opened up in InfoPath 2007 filler should now have fully functioning people pickers. | |  Dylan Skinner - Design & Development |
| We recently had a client that wanted to automatically assign Calendar Year/Quarter and Fiscal Year/Quarter values to every document they post to SharePoint using the following criteria:
· Calendar Year (1/1-12/31)
· Fiscal Year (10/1-9/30)
· Calendar Quarter (1st: 1/1-3/31, 2nd: 4/1-6/30, 3rd: 7/1-9/30, 4th: 10/1-12/31)
· Fiscal Quarter (1st: 10/1-12/31, 2nd: 1/1-3/31, 3rd: 4/1-6/30, 4th: 7/1-9/30)
This client wanted to be able to select the date used for the assignment, but it could be done with any date field as the starting point like created or modified default SharePoint columns. This was also done to a document library in particular, but could work the same for any list.
There are functions available for calculated columns to extract the YEAR(Date) or MONTH(Date) from any date field, however to keep the final formula with all of the nested IF statements a little easier to manage, we first created additional calculated columns to store this information. So the final formula below assumes you have the following columns:
· Date Field
o Could be named whatever you want, but would suggest not using “Date” though as that site column already exists several other places in SharePoint so it could be confusing which one to pick when building the formula, or could use the default SharePoint Created or Modified date fields.
· Document Month
o Calculated Column with formula =MONTH([Date Field])
· Document Year
o Calculated Column with formula =YEAR([Date Field])
· Calendar Quarter
o Calculated Column with formula below.
· Calendar Year
o Calculated Column with formula below.
· Fiscal Year
o Calculated Column with formula below.
· Fiscal Quarter
o Calculated Column with formula below.
Final Calculated Column Formulas with Nested IF Statements
This logic to determine the values to use for the less-than and greater-than is based on the criteria established above and would need to be adjusted if different fiscal year beginning and end dates.
CALENDAR QUARTER
=IF([Document Month]<4,CONCATENATE("First Quarter ",[Document Year]),IF(AND([Document Month]<7,[Document Month]>3),CONCATENATE("Second Quarter ",[Document Year]),IF(AND([Document Month]<10,[Document Month]>6),CONCATENATE("Third Quarter ",[Document Year]),CONCATENATE("Fourth Quarter ",[Document Year]))))
CALENDAR YEAR (obviously the most simple because it is just the year from the date field)
=YEAR([Date Field])
FISCAL QUARTER
=IF([Document Month]<4,CONCATENATE("Second Quarter ",[Fiscal Year]),IF(AND([Document Month]<7,[Document Month]>3),CONCATENATE("Third Quarter ",[Fiscal Year]),IF(AND([Document Month]<10,[Document Month]>6),CONCATENATE("Fourth Quarter ",[Fiscal Year]),CONCATENATE("First Quarter ",[Fiscal Year]))))
FISCAL YEAR
=IF(([Document Month]>9),([Document Year]+1),[Document Year])
| | Peter Hill - Solutions Architect |
Manage Subscriptions /_layouts/images/ReportServer/Manage_Subscription.gif /blog/_layouts/ReportServer/ManageSubscriptions.aspx?list={ListId}&ID={ItemId} 0x80 0x0 FileType rdl 350 Manage Data Sources /blog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 351 Manage Shared Datasets /blog/_layouts/ReportServer/DatasetList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 352 Manage Parameters /blog/_layouts/ReportServer/ParameterList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 353 Manage Processing Options /blog/_layouts/ReportServer/ReportExecution.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 354 Manage Cache Refresh Plans /blog/_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 355 View Report History /blog/_layouts/ReportServer/ReportHistory.aspx?list={ListId}&ID={ItemId} 0x0 0x40 FileType rdl 356 View Dependent Items /blog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 350 Edit Data Source Definition /blog/_layouts/ReportServer/SharedDataSource.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 351 View Dependent Items /blog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 350 Manage Clickthrough Reports /blog/_layouts/ReportServer/ModelClickThrough.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 352 Manage Model Item Security /blog/_layouts/ReportServer/ModelItemSecurity.aspx?list={ListId}&ID={ItemId} 0x0 0x2000000 FileType smdl 353 Regenerate Model /blog/_layouts/ReportServer/GenerateModel.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 354 Manage Data Sources /blog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType smdl 351 Load in Report Builder /blog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderModelContext&list={ListId}&ID={ItemId} 0x0 0x2 FileType smdl 250 Edit in Report Builder /_layouts/images/ReportServer/EditReport.gif /blog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderReportContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 250 Edit in Report Builder /blog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderDatasetContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 250 Manage Caching Options /blog/_layouts/ReportServer/DatasetCachingOptions.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 350 Manage Cache Refresh Plans /blog/_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId}&IsDataset=true 0x0 0x4 FileType rsd 351 Manage Data Sources /blog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rsd 352 View Dependent Items /blog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 353 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 |
|
|
|
 |
| Welcome to
SharePoint Blogs. Use this space to provide a brief message about this blog
or blog authors. To edit this content, select "Edit Page" from the "Site
Actions" menu. |
|
|
Manage Subscriptions /_layouts/images/ReportServer/Manage_Subscription.gif /blog/_layouts/ReportServer/ManageSubscriptions.aspx?list={ListId}&ID={ItemId} 0x80 0x0 FileType rdl 350 Manage Data Sources /blog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 351 Manage Shared Datasets /blog/_layouts/ReportServer/DatasetList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 352 Manage Parameters /blog/_layouts/ReportServer/ParameterList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 353 Manage Processing Options /blog/_layouts/ReportServer/ReportExecution.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 354 Manage Cache Refresh Plans /blog/_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 355 View Report History /blog/_layouts/ReportServer/ReportHistory.aspx?list={ListId}&ID={ItemId} 0x0 0x40 FileType rdl 356 View Dependent Items /blog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 350 Edit Data Source Definition /blog/_layouts/ReportServer/SharedDataSource.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 351 View Dependent Items /blog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 350 Manage Clickthrough Reports /blog/_layouts/ReportServer/ModelClickThrough.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 352 Manage Model Item Security /blog/_layouts/ReportServer/ModelItemSecurity.aspx?list={ListId}&ID={ItemId} 0x0 0x2000000 FileType smdl 353 Regenerate Model /blog/_layouts/ReportServer/GenerateModel.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 354 Manage Data Sources /blog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType smdl 351 Load in Report Builder /blog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderModelContext&list={ListId}&ID={ItemId} 0x0 0x2 FileType smdl 250 Edit in Report Builder /_layouts/images/ReportServer/EditReport.gif /blog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderReportContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 250 Edit in Report Builder /blog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderDatasetContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 250 Manage Caching Options /blog/_layouts/ReportServer/DatasetCachingOptions.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 350 Manage Cache Refresh Plans /blog/_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId}&IsDataset=true 0x0 0x4 FileType rsd 351 Manage Data Sources /blog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rsd 352 View Dependent Items /blog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 353 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 |
|
|