| 
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 |
| 
Following a successful migration we recently performed for a client, the ask was “How do we know if all of our users have changed their passwords following the migration?” The answer need not be as complicated as it sounds. No need for a monstrous VBscript to query LDAP records. There’s an advanced command line tool for just these sorts of things on every AD DS DC.
It’s called ‘dsquery’
In our example this simple command in an elevated cmd prompt gives us all we are looking for. A complete list of users who have NOT changed their passwords since a given day.
>dsquery user -stalepwd 7 -o upn -limit 10000 >> 7daysout.txt
In this example we’re calling dsquery to query the users directory for all user passwords that have not been changed within the last 7 days. It’s then formatted for output as User Principal Names by the –o switch, for readability. The –limit parameter sets the ceiling for the number of records to return. As the default is 100 records, any more returns than that are not returned and lost unless –limit is defined with a higher value. It then pipes the output to a text file we can then forward along to the client. Question answered!
The result is, a readable <return> delimited list of all users who haven’t changed their password since the day of the migration. Generated on demand in mere seconds. The client could use this list to ‘persuade’ the specific users in follow up emails, for example.
Dsquery is much more powerful than this, as you might be able to intuit from this sample of the help menu context in the cmd;
dsquery computer /? - help for finding computers in the directory.
dsquery contact /? - help for finding contacts in the directory.
dsquery subnet /? - help for finding subnets in the directory.
dsquery group /? - help for finding groups in the directory.
dsquery ou /? - help for finding organizational units in the directory.
dsquery site /? - help for finding sites in the directory.
dsquery server /? - help for finding AD DCs/LDS instances in the directory.
dsquery user /? - help for finding users in the directory.
dsquery quota /? - help for finding quotas in the directory.
dsquery partition /? - help for finding partitions in the directory.
dsquery * /? - help for finding any object in the directory by using a
generic LDAP query.
| |  Ian Banks - Systems Engineer |
| 
This blog relates specifically to the best practices for custom SharePoint Workflow lookups in SharePoint Foundation 2010 using InfoPath 2010 to SharePoint lists created in SharePoint Designer connected to an InfoPath Form Library, but could be generalized for any Workflow that connects to a SharePoint Foundation list. The overall best practice being that for workflow lookups, a login ID should always be used for comparison instead of a user name.
We had a client that used many InfoPath forms for various HR purposes, travel requests, and administrative functions within their company. Originally it was created in a SharePoint Foundation shared hosting environment and then eventually was migrated to the clients own on-site servers. For each of these forms, the workflow needed to know who the Supervisor was for particular employees for the approval process. This relationship of employees to their respective supervisor was created in a SharePoint list and the workflow would do a look-up to this list to assign individual permissions to each form and to assign approval tasks to the employee’s supervisor.
The process began originally with the person who creates the new form selecting the name of the employee from a drop-down that was populated from this Supervisors list with a Data Connection. Then InfoPath would use Property Promotion functionality to write the name of the Employee back to the Form Library when the form was submitted. Then the workflow would use this Employee Name field to do the look-up to the Supervisors list to determine who the supervisor was for this particular employee. This worked well in the shared environment and problems did not arise until the site was moved to the client’s servers in their local environment.
When the forms, users and workflows were first migrated everything still worked well and it was not until new users began to be added using a different format and process in the local environment than was previously used in the shared environment that the client noticed that permissions were not being set correctly and approval tasks were not being assigned. After much troubleshooting to determine when this was occurring, because it worked in some cases and not in others, it was discovered that it was related to this different format for the user names when created in the local environment versus the existing users that were migrated from the previous environment.
In order to correct this issue, we had to take the following steps.
1. Add a hidden login ID field to every form and populate using a formula that looked at the employee name selected in the drop-down list by the person filling out the form.
2. Then promote this login ID field to the form library.
3. Then when assigning permissions and tasks in the workflow, compare this login ID to the Employee (pulled as a login ID) people or groups field in the Supervisor list instead of comparing employee name to employee name.
Again this solved the issues at first, but again ran into issues when the client made significant changes to their Active Directory where users were created. This again somehow changed the format of even the user login IDs and again in some cases, the permissions and tasks were not being assigned correctly. Troubleshooting revealed that this was somehow related to the workflow lookup pulling the supervisor name formatted as a login ID, even though it seemed to make perfect sense to compare login ID to login ID. What finally corrected this was to pull the supervisor formatted as a string and compare that string to the login ID field promoted from the form to the form library field.
This was all a learning experience for us and hopefully will help anyone out there trying to do something similar in SharePoint Foundation 2010.
| | Peter Hill - Solutions Architect |
| 
SharePoint is all we do, and we can build upon its platform to create diverse solutions to meet any client’s needs. Personally, I enjoy architecting intranet systems and have spent the majority of my time at dataBridge working with SharePoint Enterprise level intranets. I enjoy the challenge of turning a company’s wants and needs, and in many cases pain points, into automated processes with dashboards to bring people together with the information they need to make their company more efficient.
Many companies have multiple applications in use to accomplish their daily tasks. Having disparate systems to manage information is a challenge as users must be trained on each individual system. The Enterprise edition of SharePoint 2010 has a plethora of features that we can leverage to produce a single user interface that will allow users to interact with numerous business applications without ever having to leave their SharePoint intranet. This means most users only have to learn a single system. This is just one of the beauties of the Business Connectivity Services. Add in dynamic graphs and web based Visio diagrams (that update instantly when business data changes) and you’ve got an application that not only consolidates data into a single location, but also provides robust visuals to express just about any type of information. But wait! There’s more! By creating workflows that are tied to lists, libraries, sites, or InfoPath forms we can model any process that your business has, and odds are, we can help to make that process run faster and smoother, while adding a new level of reporting to the process. | |  Brandt Fuchs - Vice President of Operations |
| Out of the box SharePoint Foundation has a manageable Top and Side Navigation. You can add URLs/Links to the top and side navigation that can go to internal or external sites, pages, documents or anything using an URL (Uniform Resource Locator). In this tutorial we will be reviewing the SharePoint Foundation top navigation in detail.
Top Navigation
- New Navigation Link
- Change Order
- Use Links from Parent
- Edit or Delete Top Navigation Link Item
- Bonus Treat: How to add an email link
- Top Navigation
We can edit the top navigation by going to Site Actions > Site Settings
Under the "Look and Feel" column click "Top Link Bar"
From the Top Link Bar page we can add New Navigation Links, Change Order and Use Links from the Parent.
- New Navigation Link: will let you add a new URL/Link to internal or external sites, pages, documents or anything using an URL (Uniform Resource Locator).
- Change Order: will let you change the numeric order of the top link items horizontally.
- Use Links from Parent: will let you inherit the same navigation as the site above unless you are at the root site / parent site already. In this example we are in a sub site under the root site.
- Edit or Delete Top Navigation Link Item: this will let you edit or delete top link items. If a link was automatically created by SharePoint then you will not be able to edit it but you can delete it and recreate it manually using step 1.
 
Add an email link: using mailto: and an email address we can insert an email link that will open Outlook or another default email platform. Example: mailto:matthew@getsharepoint.com
- Click "New Navigation Link"
- Type mailto:matthew@getsharepoint.com
- Add a description
- Hit Ok
Now in the top navigation you have an email link that can open the end user's default email client
| |  Matthew Skinner - Design & Development |
| I am a developer and I would have to say that PowerShell has become one of my favorite platforms to work with. I have always been involved with IT Pros and automating processes that are difficult for them to do.
One of my regular jobs here at dataBridge is migrating sites from previous versions of SharePoint to 2010.
When we do migrations we normally see what some of the pain points were, for the client, in the previous version. One issue we see often is when the client names the site the server name. You know, you have seen it!
Have you ever had one of those days where you migrate a site to a new server, and you find that none of the links work anymore? This is normally because the links are entered manually and are absolute paths to the server.
I created a simple script to go through the site and all children sites to clean up the URLs. Below is my script and how it makes my life easier.
I have attached the complete script at the end of this post, please feel free to comment.
This is the site collection URL, this script will only run within a site collection.
$siteURL = "http://intranet.contoso.com"
I have put two optional values here to search for, I just have found over time there is normally more than one way people hit a site. You can see by my example, some times you see the server name and sometimes you see a URL. You can add additional variables here if you need. All you need to do then is append them to the if statement and the replace statement.
$fromURL = "http://portal.contoso.com"
$fromURL2 = "http://SERVER-NAME"
In the $replaceURL this can be left empty if you want to enter an absolute path, which I don't recommend, if you want to force the site to only go to one particular URL. If you make it relative you will be able to extend your site later and none of your links will break.
$replaceURL = ""
The rest of the script will loop through the site and all sub-sites and modify the URL only if it matches one of your patterns you want changed.
$site = Get-SPSite $siteURL
$webs = $site | Get-SPWeb -Limit ALL
foreach ($web in $webs)
{
# scan the web quick launch urls
Write-Host "Scanning " $web.Url
$topLinks = $web.Navigation.TopNavigationBar
if($topLinks -ne $null)
{
# Get all the links in the Top Link bar
$topLinks = $web.Navigation.TopNavigationBar
foreach ($node in $topLinks)
{
$nodeUrl = $node.Url
if ($nodeUrl.ToString().ToLower().Contains($fromURL) -or $nodeUrl.ToString().ToLower().Contains($fromURL2))
{
Write-Host " found link to: " -foreground gray -nonewline; Write-Host $nodeUrl -nonewline
# update the link
$nodeUrl = $nodeUrl.ToString().ToLower().Replace($fromUrl,$replaceURL).Replace($fromUrl2,$replaceURL)
$node.Url = $nodeUrl
$node.Update()
Write-Host " - done." -foreground green
}
}
}
}
$site.Dispose()
As you can see this has become a very useful script whenever working with a migration. This script could also be run on a scheduled basis, if you want to clean up URLs that users enter incorrectly.
If you would like to download this script click on this link UpdateTopNavLinks.ps1
Happy scripting! | |  Rick Toner - Lead Developer |
| 
If you have visited a website within the past 15 years, chances are you have run into gradients in some form or another. Deploying gradients in a website's design allows designers to give a certain amount of depth and polish to a site that would otherwise come off a little flat. They are effective when used in a subtle and respectful manner that does not go overboard. It is easy to become lost in trying to make your site "stand out" and end up abusing something like gradients; the results of which are less than desirable more often than not. The beauty of gradients that are done right is that you barely ever notice them, but without them your design can be left lacking.
Many SharePoint sites are intranets and as a result need to look professional but at the same time not flat or boring. When used tastefully and sparingly, gradients can give your SharePoint site just the right kind of creative but professional feel.
In this article we will cover the basics of the gradient tools at our disposal in Photoshop and how best we can put those to work for us rather than against. For those of you, who are already familiar with the gradient tools, feel free to skip the first part.
I. The Gradient Tool
 In order to access the gradient tool in Photoshop, you need to select it in the same selection area as the "paint bucket tool". By default the paint bucket tool is auto-selected as the top selection here. So simply locate it underneath the eraser tool and click + hold on the menu item. A selection box will appear with two options, select the gradient tool. Once you have selected it your curser will change to a cross shaped target and you will be able to apply a gradient to your selected layer.
Now that the gradient tool has been selected, you will see that you have a number of new options to select from on the "options" menu bar below the main menu.
As you can see there are a healthy number of options and ways you can modify/customize your gradient to give it the appearance you are looking for. Above you will notice I labeled three of the options which may seem a little more ambiguous as to what they do.
- Gradient editor: lets you modify and adjust the overall look and feel of the gradient you hope to create. You can adjust the colors, ratio, opacity, etc., all within this tool just by double clicking on the gradient preview.
- Gradient style: selection allows you to determine in what manner your gradient will be rendered. The two most commonly used styles in web design are linear and radial. The other three: angle, reflected, and diamond have their place but should be used sparingly as a good rule of thumb.
- Blending Modes: These options are not unique to gradients and can be used to affect how layers blend into others below it. Similarly selecting a different blend mode when creating a gradient will change its appearance in relation to the objects below it.
It is worth taking an in-depth look at what the gradient editor enables you to do. It is here that the foundation of your gradient is created.
Breaking down the Gradient Editor:
- Name Field: This one is pretty self-explanatory and allows you to set a custom name for each gradient that you create. This is helpful when you save the gradients out to use in later projects.
- Gradient Type Selector: This drop down has two options consisting of "Solid" and "Noise". It is defaulted to Solid and that is almost exclusively the type you want to use when incorporating gradients into your web designs.
- Smoothness: Determines how soft the transition from one color to the next is in your gradient.
- Opacity Slider: This is the first of the two main sliders on the gradient bar that control the appearance of the gradient. This slider controls the opacity of the color on this side of the gradient and can be used to fade a gradient out and meld it into its background.
- Color Slider: This slider controls the color of the gradient at its current position and functions exactly the same as the above slider. Its position directly influences how much of the gradient is taken up by this color.
II. Putting Gradients to Work.
Now that we have had a rundown of the gradient tool and how it operates let's take a look at an example of how to properly put it to use. Here are a few key points to hammer home when creating gradient elements for your SharePoint web design.
One of the best places to utilize gradients when branding a SharePoint site is with the web part headers. Web Parts are going to be used across your site on nearly every page you have on your site. Since they are so common place their look and feel can make the difference in having a boring SharePoint site or an exciting and appealing one.
Web Part with Rounded Gradient Header Web Part with Out of the Box Header
 
As you can see here in the above example, with no other style changed to the web part or its structure, adjusting the header makes a huge improvement in its overall aesthetic appeal. Let's take a closer look at the stylized header and compare one with and without the gradient.
Solid Color Web Part Header
Gradient Web Part Header
Gradient Web Part Header Gone Mad
While there can be no doubt that even the solid color web part header is an improvement compared to the out of the box look and feel. The subtle gradient on the second header gives a sense of depth and complexity that can be very appealing given the right design. An important property of the gradient in this header is that it is not extremely bold or overwhelming. Using colors that are only slightly different in shade allows for a gradual and natural progression from one color to the next.
The last web part header is an example of how easy it is for gradients to quickly become an ugly mess if not used properly. Using more than two colors with drastically different shades can produce an effect that is more akin to 80s fashion than a professional looking web design.
| |  Matt Metcalf - Design & Development |
| 
Does your branding ever slip and slide? When creating a custom footer in SharePoint, you may find your footer looking like something shown below. For some reason it won’t stay underneath of your content, even though it’s underneath your content wrapper. Well here is a little CSS snippet that can fix that. Thank you to Dylan Skinner for sharing a simple solution to a pesky problem.
Now the footer stays underneath of the content area. Also for those who want to know; the footer in this example is a div right underneath of the #s4-mainarea.
 | | Dylan Skinner - Design & Development |
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 |
|
|