Archive for the ‘MS Office SharePoint Server’ Category

Microsoft Demo Builder 2013

August 17, 2014

Demo builder helps you build demos with data which can be used in your corporate demo.

It also comes with OOB SharePoint integration, Azure Integration as well as customer portal. Very handy for setting up quick demo environment.


Check this link for details:

Microsoft Office SharePoint 2013 FBA Pack Released

July 1, 2014

The SharePoint 2013 FBA Pack has been released. It was ported from the SharePoint 2010 FBA Pack (which was originally ported from the SharePoint 2007 CKS Forms Based Authentication Solution), and includes all of the features from the SharePoint 2010 FBA Pack:

  • User Management
  • Role Management
  • Membership Request Web Part
  • Password Recovery Web Part
  • Change Password Web Part
  • Change Password Menu Item

Forms 7 – A lightweight InfoPath alternative for SharePoint

June 16, 2014

Forms7 is a lightweight InfoPath alternative that uses a jQuery plugin that allows users to easily create forms for SharePoint 2007/2010/2013 using basic HTML.


Forms7 comes with many features that can add robustness and usability to your forms including:

- Create forms using ANY HTML editor and store form in ANY SharePoint List

- Store multiple forms on the same SharePoint list without adding additional fields

- Helper functions for loading Cascading Drop Down lists from other SharePoint Lists

- Custom validation that checks for required fields, validity of entered data, and the ability to create your own validation functions

- Forms7 can use jQuery UI for date fields and other functionality

- “Required” fields are ignored if the fields are not visible on the page

- NEW in version 0.05 Reporting using the DataTables Library. Create List Views for your Forms7 forms!

Videos for more information and getting started

Introduction to Forms 7

Installation and Minimal Form

Select Boxes and Loading Select boxes with SharePoint List data for options

Converting Word Document to Forms7 Form 

Reporting/List Views of form data stored in Forms7


The Forms7 plugin will iterate over the fields in your HTML form and store the fields as a JSON object in one field in your SharePoint list. Using Forms7 you can promote fields to SharePoint list fields as well as add custom validation of fields.

Forms7 puts the power of the forms in the hands of your business again by allowing non-technical users to create attractive forms using any HTML editor and passing that HTML off to your JavaScript developers should additional functionality want to be added like conditionally hiding/showing fields.

Forms7 is a great InfoPath alternative for users wanting to move away from that technology for their basic forms needs.

An earlier version of Forms7 is currently in use by a fortune 100 company storing 9 different forms in one list with great success.

Forms7 is free, and for free, it does have it’s limitations including:

1) People Pickers are not currently supported
2) It’s in ALPHA!! I’ve not tested every possible iteration and possibility.
3) Documentation is currently light (non-existent) but this will be added as interest grows.

Forms7 uses SPServices to read and write SharePoint list data ( Future plans include a supported version that uses the Client Object Model.

How can you help?? Let me know you are interested so that I’ve got some motivation to document and improve this promising technology.

The included Sample Form will help you get started until I can get some actual documentation in place. To use the sample form without modifications:

1) copy the form and script to a “SiteAssets” document library on your site.

2) Create a list called “Contacts” and add a multiline plain text field called “Forms7Data”.

3) Create a Web Part Page called “SampleForm” under Site Pages

4) Drop a Content Editor Web Part on the page and link it to ../SiteAssets/sampleForm.html

You can see a live sample here:

A more styled example of form for same list can be found here (best viewed in Chrome because of CSS used):

More Examples and Documentation Coming Soon! 

SPIEFolder version 2.0

June 10, 2014

SPIEFolder is a tool you can use to import/export files to/from SharePoint document libraries and the local file system.
Allows you to either Import a file system folder (And all files and subfolders) into a SharePoint Document Library, and also export a SharePoint Document Library or a complete site’s content to the file system for Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 and SharePoint Foundation 2010/SharePoint Server 2010. This tool completely replicates the document libraries folder hierarchy to the file system when exporting, and replicates the folder hierarchy from the file system to the document library when importing.

Note: This tool ONLY exports the physical files and folders, it does NOT export metadata.

Lastest Version: 2.0 – Click to Download

Source: Keith Richie Blog

SharePoint Server 2013 Service Pack 1 now available

May 7, 2014

SP1 is our latest release to SharePoint Server 2013 on-premises. This service pack includes performance, reliability, and security fixes. It also helps IT address some of the most common scenarios faced when moving to the cloud, helping them deploy cloud-based workloads in their organization faster and with less complexity, while providing them with the control they demand.

These improvements to SharePoint 2013 on-premises include:

  • Seamless hybrid connection to OneDrive for Business in Office 365.
  • Support for Yammer as the chosen social network, making it easier to replace the default Newsfeed.
  • Support for JSON Light in OData v3 requests.

Seamless connection to OneDrive for Business in Office 365

We’re making it easier for SharePoint 2013 on-premises customers to use OneDrive for Business in the cloud alongside their existing SharePoint deployment. In SP1, new functionality allows an IT administrator to selectively configure redirection of OneDrive for Business, sites, and pages to the cloud while providing familiar IT controls. By combining OneDrive for Business and existing hybrid solutions, such as Search, IT can deploy rich cloud-based experiences for users and maintain control and visibility of the content users create.


Organizations of all sizes are using Yammer. SP1 makes it easy for IT to replace the out-of-the-box SharePoint 2013 social experience (Newsfeed) with Yammer. Using simple controls in SharePoint 2013 Central Administration, IT can choose to activate (or deactivate) Yammer, redirecting users to their established Yammer network.

JSON Light

SP1 includes notable improvements that support developers. SP1 introduces support for JSON Light, allowing developers to choose which level of metadata they would like in a response: no metadata, minimal metadata, or full metadata (previously the only option in SharePoint 2013).


In addition to the new functionality SP1 provides, this service pack includes a number of fixes designed to improve your experience with SharePoint 2013. It also includes all cumulative updates through December 2013 and public updates through February 2014.

The list below identifies all the 2013 fixes that have already shipped, including cumulative updates and public updates. All of the fixes on this list are included in the SharePoint 2013 SP1 release. In addition to the fixes listed below, Service Pack 1 contains additional fixes for each product.

Try it out today

Service Pack 1 is just one step we’re taking to support our customers who have deployed SharePoint 2013. As we move forward in 2014, we’ll continue to keep you up to date with the latest performance, security, and reliability fixes through ongoing releases of both public and cumulative updates. And while we’re doing that, we’ll continue to drive toward the next SharePoint release, scheduled sometime during 2015.

No matter how you take advantage of SharePoint—on-premises, online, or somewhere in between— we’ll continue to ensure that you have the latest innovations, easy on-ramps to the cloud, and great experiences.

SharePoint Current Visitors Web Part

March 5, 2014

The Current Visitors Web Part is intended to display a list of users that are currently visiting a SharePoint site collection.

All you need to do is just to place the Web Part on your SharePoint page (Web Part or Master).

The Web Part is using OOB SharePoint auditing so please note when you activate the Current Visitors Web Part feature on your site collection, this in turn enables the site collection audit logging.

By default the ‘currently visiting’ user is a person who viewed any content in the site collection in the last five minutes. This period can be configured in the Web Part’s properties.


SharePoint 2010/2013 Tabbed Web Part Zone

March 3, 2014

Tabs in SharePoint Project Description

This project shows a working example of how to implement a tabbed web part zone in both SharePoint 2010 and 2013 using only a custom page layout and JQuery.
This project contains a sample SharePoint Publishing Page Layout (For both 2010 and 2013) with a “Tabbed Web Part Zone”.  See for more information.
Please see the Downloads section for pre-packaged WSPs for both SharePoint 2010 and 2013 if you’d like to directly deploy it to an on-premise SharePoint farm.
Please contact if you have any questions, comments or issues.

New! Tabbed Web Parts for SharePoint Online (365)

I have now created a manually deployable publishing page layout that is fully compatible with SharePoint Online 2013 with publishing (as well as backwards compatible with SharePoint 2013 Enterprise On-Premise if you do not want to deploy the entire WSP). Please check it out here:


SharePoint Admin Dashboard

March 1, 2014

Project Description Easily compare server configuration.   “Grid” layout shows configuration of the full farm in one table.  Export to Excel for filter, sort, and pivot chart.


  • Do admin tasks faster
  • Scale up beyond RDP
  • Add new servers without fear
  • Verify consistent configuration


  • New WSP format
  • Central Admin > Monitoring > SPDash easy navigation
  • View server config data in table format
  • Export to Excel
  • Timer job refreshes data cache of XML files
  • Wide screen layout for SharePoint 2013
  • Automatic hive (14/15) detection for SP2010/2013 support

Data Sources

  • WMI query
  • Global Assembly Cache
  • IIS web.config
  • Logical disk size and space
  • File versions (to confirm patching)
  • Display Local Administrator members
  • Kerberos SPN for all managed accounts and farm machines

Background SharePoint farms have many servers with various services, applications, traffic patterns, and purposes.  Having “grid” scripts like the below sample screen-shots can save lots of time.  What’s a “grid”?   Simple.   I wanted to build a real-time Excel spreadsheet to display ALL configuration without RDP.  RDP won’t scale.  While great for 1-2 servers, it’s awful for 10+ servers.  Having confidence in your configs and knowing everything is 100% consistent are BIG steps forward for most admins.


The SharePoint Diagnostic Studio 2010 (SPDiag 3.0)

February 5, 2014

Microsoft seems to have snuck in a new tool to help diagnose/troubleshoot issues in SharePoint.  It is part of the Microsoft SharePoint 2010 Administration Toolkit v2.0 and provides SharePoint administrators with a unified interface that can be used to gather relevant information from a farm, display the results in a meaningful way, identify performance issues, and share or export the collected data and reports for analysis by Microsoft support personnel.


In the example above I installed it on a WFE server in the SharePoint farm


Selecting “New Project” and accepting the server will give you a dashboard.similar to above and access to reports in the following categories: Base, Capacity, Performance, Availability and Usage.  NOTE: Make sure you launch SPDiag 3.0 as “Administrator” if you are running it on one of the SharePoint Servers, you can also run it from a client workstation provided some additional configuration has been performed.

SharePoint Diagnostic Studio 2010: Can be installed on any computer running 64-bit Windows 7, or on any server running a 64-bit Windows operating system. Requires Windows PowerShell 2.0.

To find out more about SPDiag 3.0 including: What’s new, Installing and Configuring, and Using it please check out the link here on TechNet.

The Microsoft SharePoint Team Blog has a great article detailing the features of SharePoint Diagnostic Studio.

SharePoint Diagnostic Studio in combination with SharePoint Health Analyzer and System Center Operations Manager gives an unprecedented view into your SharePoint Farm.

Important Links:

SharePoint 2010 and BCS – Unable to display this Web Part

January 24, 2014

Using SharePoint Designer 2010 to create a external content type and external list is a good choice and spent a lot of time. But when you open the external list in your browser you can get the following error.

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.

The reason is very easy. If your source return more than 2000 elements this error occurred. So here are the solutions.

  1. Filter your data by using stored procedure, view etc. and make sure that you didn’t get more than 2000 elements.
  2. Change the Throttling settings

The default value of the throttling is 2000 elements. So you can edit this throttling by run the SharePoint 2010 Management Shell as Administrator.

The console will be open and you have to enter the following command:


You get a list of all Proxy Services. The Service “Business Data Connectivity Service” is important for us. The rest is in this case Trash ;-)  .

Copy the GUID of the Business Data Connectivity Service and run the following comand, for showing the current throttling settings:

Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottlyType Items -ServiceApplicationProxy <GUID>

For editing the current settings you have to save them into a global variable.

$db = Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottleType Items -ServiceApplicationProxy <GUID>

Set-SPBusinessDataCatalogThrottleConfig -Identity $db -maximum 10000 -default 8000

Now the Throttling is set to a maximum of 10000 elements and a default value of 8000 elements. If you have a source with more then 1000 elements, then you have to set a higher value.



Get every new post delivered to your Inbox.

Join 31 other followers