While visiting with one of my customers this week I was asked for a tutorial on creating a date range filter for a Data View web part using SharePoint 2010 and SharePoint Designer 2010. I decided the easiest way to demonstrate this task was to create a short web cast video. Check out the video below:
A few days ago one of my customer’s reached out to me with a rather perplexing issue. They have a custom list in SharePoint 2010 with a multiline textbox configured to append changes to existing text. Whenever a user of the site tried to create or edit an entry in this list they would receive an access denied error.
Since the user has access to other lists and content in the site it left me with a few possible options:
- The list has unique permissions which is causing the access denied error.
- A workflow task associated with the list is requiring a higher level of permission.
- An event handler associated with the list is requiring a higher level of permission.
The customer responded that none of the above possibilities were true. The permissions were being inherited, no workflows were associated, and they were not using event handlers.
I was still very confident that this was a simple permissions issue somewhere. To enable the append changes to existing text option on an textbox you must first enable versioning on the list. Is it possible that the default permission levels in the site collection were changed, or maybe they are using their own custom permission level? A quick email and I receive my response. Yes! They had created a custom permission level and removed the view versions ability. Once they added that ability back into their custom permission level the users were able to add and edit items in the list.
There is an article available on TechNet that can be valuable when dealing with issues related to permission levels. The article lists out all of the default permission levels and their settings. A quick review of this document can assist an administrator in determining if a site collection owner has made modifications to the out of the box permission levels.
One of the first questions IT organizations usually say after installing SharePoint is “now what?”. The organization understands the business value of SharePoint and are excited to use it. The problem is that they do not know where to begin with building out sites for their users.
To help kick start that process Microsoft has created a complete portfolio of free SharePoint templates that can be used with SharePoint 2010 and SharePoint Online. This portfolio includes 30 templates covering all sorts of topics including project tracking, operations, management and finance, information management, human resource management, and healthcare.
To view or download these templates, hop on over to the Microsoft in Government web site.
While building out a SharePoint demo farm with SQL 2012 I ran into the following error when trying to view a PowerPivot spreadsheet:
Unable to refresh data for a data connection in the workbook
After a lot of digging around I realized that it was a pretty simple issue. My farm includes a web front end (WFE), an applications server, and the SQL 2012 database server. One step in configuring PowerPivot on the application server is to ensure that both version 4 and 5 of the MSOLAP provider is installed. The one piece of information that isn’t mentioned is that you need to also install the MSOLAP providers on the web front ends if they also have Excel Services enabled. Once the MSOLAP providers were installed on the WFE the error went away and the workbook functioned as expected.
Check out this TechNet article for information on installing the Analysis Services OLE DB Provider (MSOLAP) on SharePoint.
Like most administrative offices in most county governments throughout the United States, the Juvenile Justice agencies in San Diego County all run on paper—a million pieces of paper, all of which have to be created, copied, distributed, filed, and retrieved by hand. To help their employees work more efficiently and effectively, these agencies are replacing that paper with a digital library and workflow management solution based on Microsoft technologies. The result: attorneys glean better insights from their cases while spending less time reviewing them. Within the District Attorney’s Office, greater flexibility to assign cases boosts attorney productivity by 14 percent. Support staff productivity is up 50 percent. And the tangible return on investment, across the Juvenile Justice agencies, is expected to be more than 100 percent.
A new project recently posted on CodePlex provides a way to theme your SharePoint 2010 sites with a Metro style UI. This project includes 4 files: master page, CSS, page layout and image pack. You can read more about the project, view a demo screenshot or download the files at the CodePle SharePoint 2010 Metro UI site.
Ever wonder how Microsoft deployed and manages SharePoint 2010 internally? The TechNet session titled “36 Terabytes: How Microsoft IT Manages SharePoint in the Enterprise” will answer some of your questions. Microsoft’s internal SharePoint services currently provides 180,000 global users a comprehensive collaboration experience hosting 36 terabytes of content across three regional data centers. Learn how Microsoft IT architected, deployed, and manages its SharePoint enterprise services as well as how the Cloud is changing the way we do business.
Check out the video here.
Disclaimer: The information found in this blog post is not endorsed, recommended, or supported by Microsoft. If you run into any issues with this configuration you are on your own! You have been warned.
This blog post outlines how you can get SharePoint 2010 running on Windows 8 RP for development purposes. I put this together as a way to test out Visual Studio 2012 RC with SharePoint 2010 on Windows 8 RP.
To get started, please review the MSDN document called Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008. These are the basic steps required for getting SharePoint 2010 running on Windows 7. To get SharePoint running on Windows 8 RP there are a few additional steps which I have outlined below. Some of the steps will reference information in the MSDN article linked above.
- Download and Copy the SharePoint installation file to a folder (such as c:\SharePointFiles) on the computer where you are installing SharePoint and doing your development. The SharePoint installation file should be a single .EXE file such as OfficeServer.exe.
- Extract the installation files by opening a command prompt window and then typing the following command at the directory location of the folder where you copied the installation files in the previous step. OfficeServer.exe /extract:c:\SharePointFiles
- Using a text editor such as Notepad, open the installation configuration file, config.xml, located in the path c:\SharePointFiles\files\Setup\config.xml and add the following line inside the <configuration> tag:
<Setting Id=”AllowWindowsClientInstall” Value=”True”/>
- Save the configuration file.
- Review the configuration file. It should look similar to the XML block shown in Step 2 sub-step 5 in this document.
- Install the following prerequisites:
- Microsoft Sync Framework
- Chart Controls
- Filter Pack – Located in the c:\SharePointFiles\PrerequisiteInstallerFiles\FilterPack folder
- SQL Server Analysis Services ADOMD.NET
- Enable Windows features by running the command shown in Step 2 sub-step 8 in this document.
- Manually enable the Windows Identity Foundation feature by:
- Go to the start menu (press the Windows key on the keyboard)
- Type: “Windows Features”
- Click on the Settings shown below the search box
- Click on the Turn Windows Features On or Off option on the start menu
- Check the Windows Identity Foundation 3.5 option and then click OK.
- Wait for the feature to be enabled.
- Open Internet Information Services Manager and expand the server node in the left tree menu to expose the Application Pools grouping.
- Select Application Pools in the left menu and then click on the Set Application Pool Defaults… action in the right menu.
- Set the .NET Framework version to V2.0 and then click OK
- Select the DefaultAppPool from the list of application pools and then click on the Basic Settings… action in the right menu.
- Set the .NET Framework version to .NET Framework v2.0.50727 and then click OK.
- Run the SharePoint 2010 installer by typing the following at the command prompt: c:\SharePointFiles\Setup.exe
- Accept the Microsoft Software License Terms
- On the Choose the installation you want page, click Standalone to install everything on the developer workstation.
- After the SharePoint files are installed you will be presented with the option to run the SharePoint Products and Technologies Configuration Wizard. You should allow this to run. If you do not run the Wizard now you can run it at a later time. The SharePoint installation is not completed until the Wizard is run.
- One the configuration Wizard completes you will see your new SharePoint 2010 Site.
- SharePoint 2010 Only works with application pools that are set to version 2 of the .NET framework. If any of the application pools used by SharePoint are set to anything else you will receive an error during the SharePoint 2010 Products and Configuration Wizard. You can return to IIS manager and review the application pool settings at any time. If the wizard fails due to the wrong .NET version you can modify the application pool and then restart the wizard.
I would like to hear feedback If you try running SharePoint 2010 on Windows 8 RP for development evaluation purposes.
Yesterday I posted a video showing how to automatically populate fields in an InfoPath form with values from the SharePoint user profile store for the currently logged in user. In this video I demonstrate an alternate method that works with SharePoint web applications that are using claims based authentication.
This video is about 28 minutes long.
In this video I demonstrate how to automatically populate fields in an InfoPath form with values from the SharePoint user profile store for the current logged in user.
It is important to note that this method will only work for SharePoint 2010 sites that are hosted under a web application configured for classic mode authentication. If you are using claims based authentication this method will return an error message. In the future I plan to create a video to demonstrate how to accomplish this task for a claims based SharePoint web application.
The video is about 16 minutes long.