SharePoint Videos

Top Benefits of SharePoint 2013
SharePoint and Office 2013 Integration
What's New in Business Intelligence in Office and SharePoint 2013
SharePoint, Lync, and, Exchange in the Cloud with Office 365
Advanced Reporting in SharePoint with Microsoft Power View
SharePoint 2013 and Enterprise Content Management
SharePoint 2013 Migration and Governance
Why SharePoint 2013
SharePoint 2013 Launch
SharePoint 2013 and Enterprise Content Management
What's New in Search for SharePoint 2013
SharePoint 2013 Solutions for the Legal Industry
Full Lifecycle Content Management with SharePoint 2013
Driving the Business Case and User Adoption for SharePoint
SharePoint 2013 Solutions for the Financial Services Industry
ProjectReady 2013: SharePoint Solutions built for the AEC
Investment Considerations for SharePoint 2010 and SharePoint 2013
Advanced Workflow Made Easy with SharePoint 2013 and Nintex
Advanced Content Lifecycle and Records Management in SharePoint
How to Redline, Markup, Collaborate and Review Content in SharePoint
Application of Content Security and Corporate Risk Protection in SharePoint
Compliant Document Generation and Assembly in SharePoint
Full Lifecycle Content Management with SharePoint 2013
Driving the Business Case and User Adoption for SharePoint
SharePoint and Office 365 Migration Made Easy
Keys to Successful SharePoint Initiatives and User Adoption
Automate Business Processes with SharePoint 2013 and Business Connectivity Services
Out of the Box Business Intelligence and Reporting in SharePoint 2013
Boost Performance and Eliminate Storage Limitations in SharePoint
Digitize Paper Driven Processes with Dynamic Web Forms in SharePoint
Ensure Auditability and Compliance with Advanced Workflows in SharePoint
SharePoint 2013 vs. SharePoint Online and Office 365: Business Intelligence
SharePoint 2013 vs. SharePoint Online and Office 365: Enterprise Content Management
SharePoint 2013 vs. SharePoint Online: Search
Power Business Intelligence for SharePoint Online and Office 365
SharePoint 2013 vs. SharePoint Online: Workflow
Enforce Governance with Ease in SharePoint and SharePoint Online
SharePoint Reporting for Project, Program and Portfolio Management
Expanding the Use, Potential and Value of SharePoint and Office 365 through 3rd Party Applications
SharePoint 2013 vs SharePoint Online and Office 365 Security, Compliance and eDiscovery
Enterprise Workflow in the cloud with SharePoint & Office 365
Easily Move Email, Files and SharePoint to Office 365
Governance Essentials for SharePoint 2013 and SharePoint Online
Manage Email in the Cloud or On-Premise with SharePoint & Office 365
Automating Contract Management with Workflow in the Cloud or On-Premise
What’s Coming in Office 365 & SharePoint 2016
Best New Features of SharePoint 2016
Task, Resource & Utilization Management & Reporting for the AEC with SharePoint and Office 365
Legal Matter Task Management and Reports in SharePoint and Office 365
The Value of the Microsoft Cloud: Understanding the Scalability, Affordable Storage & Security Advantages of Office 365
Enterprise Records Management in SharePoint & Office 365
Security & Sharing in SharePoint 2016, Online & Office 365
AutoCAD & Document Management, Viewing, Markup & Mobility in SharePoint
Legal Document Control & Collaboration in SharePoint
Legal Matter & Email Management with Microsoft Outlook

 Connect

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.


Correlation ID:d0bf1c78-a781-40c0-b26e-31a1b5e05149

 TheSharePointBlog Schedule an Azure webjob for an existing Console Application project

Ranked 5.0  out of 5. Rate This Post!     

By: Shaili Modi

This can be used when we want a Console application to run on a regular interval using Azure Scheduler.

Prerequisites

WebJobs deployment features are available in Visual Studio 2013 when you install Azure SDK version 2.4 or later versions: Azure SDK for Visual Studio 2013.

The WebJobs deployment features are also included in Visual Studio 2013 Update 3 and later updates.

Use this to configure an existing Console Application project to deploy as a WebJob by itself, with no link to a web project. This is very useful when you want to run a WebJob in a web app by itself. You might want to do this in order to be able to scale your WebJob resources independently of your web application resources.

Right-click the Console Application project in Solution Explorer, and then click Publish as Azure WebJob.

schedule-an-azure-webjob-for-Console-Application-project-1

A dialog box appears, with the project selected in the Project name box.

sharepoint-blog-schedule-an-azure-webjob-for-Console-Application-project-2

Once you click OK, the following dialog appears:

sharepoint-blog-schedule-an-azure-webjob-for-Console-Application-project-3

You can select it to create in an existing web app or create a new web app or import a publish profile.

sharepoint-blog-schedule-an-azure-webjob-for-Console-Application-project-4

sharepoint-blog-schedule-an-azure-webjob-for-Console-Application-project-5

On clicking on Publish it creates the web job which can be viewed and managed ...

 TheSharePointBlog Creating a New SharePoint List Item with Content Type ‘Link to Document’ Item Programmatically

Ranked 5.0  out of 5. Rate This Post!     

By: Shaili Modi

A link to a document item would create a link to any document in a sharepoint document library. It can also be used to link to documents outside of sharepoint, but we will concentrate on how to add documents from a sharepoint document library here.

A document can be made available in SharePoint with a few easy steps using the “Link To a Document” content type.

Once the ‘Link To a Document’ content type is added to the list there are two main steps:

Create an aspx file that can be used as a template to create new items

  • The Link is basically an aspx page that redirects to the document. The format of the aspx page should be as below:

sharepoint-blog-creating-a-new-link-to-document

  • Save it as a template.txt and use it to replace the redirect URL when creating the Link to Document item.
  • The IconOverlay Tag creates a Word like Icon instead of an aspx link icon on the item

Use the Files.Add() function to add the aspx page to the library

Once the aspx text file is ready this is how you can create a new item:

 TheSharePointBlog Office 365 - SharePoint Online Content Type Hub

Ranked 5.0  out of 5. Rate This Post!     

By Shaili Modi

With SharePoint 2010 or 2013 on-premises, you could add a new site collection, turn on the features and configure the managed metadata service to publish the content type to a content type publishing hub.

When you try to do that in SharePoint online however, you’ll notice there isn’t a way to configure the managed metadata service with the hub URL.

If you try to create a content type and publish it in the new created hub you would get this error:

the-sharepoint-blog-sharepoint-online

The managed metadata service isn’t wired up to the content type hub you created, so you can’t publish. We kind of knew that since we couldn’t find the settings in the managed metadata service that we see on-premises.

 

Every SharePoint Online tenant has a content type hub pre-built! It exists at https://<tenant>.sharepoint.com/sites/contenttypehub

When you view the list of site collections in your tenant, the hub isn’t there as it is a hidden site collection.

So when publishing content types in SharePoint Online, be sure to use your pre-built content type hub!

 TheSharePointBlog Simple SharePoint Warm-Up with CSOM

Ranked 5.0  out of 5. Rate This Post!     

By: Christian Holslin

Warming up a SharePoint farm can be helpful if your users experience start-up delays in the morning when first accessing the system.  To get around this hiccup, we commonly deploy what many refer to as a warm-up script.  There are many ways to build one, and many out there to choose from.  I will walk you through a simple .NET 4.5 console application built with the client-side object model which works for SharePoint 2010 and SharePoint 2013 and is easy to deploy almost anywhere on the network.

Skipping Ahead

If you’re just here for the code, feel free to skip down to the Source Code section at the bottom.  There are some dependencies, but if you know what you’re doing already you might be able to guess what they are.  If not, read the Dependencies and Assembly References sections.

Benefits of CSOM over Server-Side

The traditional server-side warm-up script designed for a MOSS 2007 environment requires direct access to the SharePoint farm.  While these work great for SharePoint 2010 and SharePoint 2013 as well, you can only run the warm-up script on one of the SharePoint servers.

The client-side object model, or CSOM, frees us from this restriction allowing us to deploy our warm-up script onto any server or workstation on the network, so long as it can access SharePoint via the HTTP protocol.

Removing CSOM as a Dependency

You could take my code and remove CSOM as a dependency a...

 TheSharePointBlog Create a Calculated Column to Calculate Business Days

Ranked 5.0  out of 5. Rate This Post!     
By: Shaili Modi
 
SharePoint Calculated Columns are powerful tools when creating out-of-the-box solutions. With these columns, we can manipulate other columns in the list item.
 
If we need to get a Reply Due or a Due Date field as a date being 5 working days from the received date/added date/modified date?
 
We can use the SharePoint calculated column using the formula Weekday which returns 1 for Sunday, 2 for Monday and through to 7 for Saturday.
 
So from here we can work out if the day is 5 working days before current day…
 
the-sharepoint-blog-create-a-calculated-column-to-calculate-business-days
 
Or writing this another way we can use this to create a SharePoint calculated column formula:
 
Weekday > 3 then +5
Weekday = 2 or 3 then +3

 TheSharePointBlog InfoPath Cannot Save the Form Error

Ranked 5.0  out of 5. Rate This Post!     
By: Shaili Modi
 
Symptom:
Assume that you are running Microsoft InfoPath on a Windows Server 2008 R2 server, and the Desktop Experience feature is not enabled on the server. In this situation, you cannot use InfoPath to publish an InfoPath form on a Microsoft SharePoint Server 2013 server. Additionally, when you try to publish and save the form, you receive the following error message:
 
InfoPath cannot save the following form: Form Name. This Document Library was either renamed or deleted, or network problems are preventing the file from being saved. Contact your network administrator.
 
Cause:
This issue occurs because the Desktop Experience feature is not enabled on the Windows Server 2008 R2 server. Therefore, connections cannot be made from the Windows Server 2008 R2 server to the SharePoint server.
 
The same problem occurs running InfoPath 2013 against SharePoint 2013 running on Windows 2012.
 
Solution:
  • If you must develop InfoPath forms on the Sharepoint Server.

 TheSharePointBlog Excel Services View Only Permissions Demystified

Ranked 5.0  out of 5. Rate This Post!     

By: Neil Barkhina

One of the really cool features of Excel Services is the ability to use it for reporting and dashboards, without divulging its underlying formulas and data connections to the end users. However to get this working, you need to understand a little about what permission levels and configuration settings to use. Luckily SharePoint gives you a nice little head start with a Group called “Excel Services Viewers”

  • Intro
  • Show permission level screen and different options
  • Show Document library ribbon options when you have view only
  • Show the report after it loaded
    • Show the backstage in excel services
    • Show downloading the document, doesn’t have any formulas
  • What happens if the report has data already embedded?
    • In that case show the reload workbook on open option in excel

Excel-Services-View-Only-Permissions-Demystified-Picture1

The key to this group is that it is set to “View Only” which is a special permission level which only allows users to “View Items”.

TheSharePointBlog DiggTheSharePointBlog DeliciousTheSharePointBlog StumbeUpon

 TheSharePointBlog LINQ to XML

Ranked 5.0  out of 5. Rate This Post!     
By: Shaili Modi

XML is one of the most popular formats for files and data streams that need to represent complex data. The InfoPath forms use XML data as well as many task forms and the RSS data feed.
 

Once you've got your hands on XML data, you can use LINQ to query anything from the data. LINQ to XML is a great way to manipulate the XML data out of the XML file.

  • The first thing we need to do is get the XML of the InfoPath form, before we can work with it. Open the file and get the XML. You can then use the File object along with OpenBinary() to get the raw bytes of the XML.

byte[] xmlBytes = workflowProperties.Item.File.OpenBinary();

  • You can then takes those bytes and read them into a regular string.

string xmlString = System.Text.Encoding.UTF8.GetString(xmlBytes);

if (xmlString[0] == (char)0xfeff)

xmlString = xmlString.Substring(1);

 TheSharePointBlog Defining Extended DRM Permissions for Documents

Ranked 5.0  out of 5. Rate This Post!     

By: Peter Nuffer, Guest Blog Writer, Accusoft

 

Out of the box, SharePoint provides only basic document security options that protect the integrity of the repository but don’t effectively address misuse of content through unauthorized printing, saving and copying text from documents to which restricted users have read-only access configured through SharePoint’s DRM.

 

What’s needed is an integrated way to augment SharePoint’s native document security easily and effectively, and for a low cost in terms of licensing, infrastructure, implementation, maintenance and user training. You can achieve that by selectively redirecting SharePoint document viewing to a secure browser-based environment with customizable DRM controls.

 

Prizm Content Connect for SharePoint includes a redirector that a SharePoint administrator can configure to intercept direct requests from selected users for selected documents and redirect document display away from the native application into a multiformat viewer running in the user’s default browser.

 

After Prizm Content Connect for SharePoint has been installed, the administrator has access to new end user permissions and global settings within SharePoint. End user permissions include DRM and annotations permissions, while global settings control the interaction between SharePoint and the behind-the-scenes components that implement document viewing.

 

TheSharePointBlog DiggTheSharePointBlog DeliciousTheSharePointBlog StumbeUpon

 TheSharePointBlog Connecting the WCF Web Service to Infopath

Ranked 5.0  out of 5. Rate This Post!     

By: Shaili Modi

Windows Communication Foundation (WCF) is an SDK for developing and deploying services on Windows. WCF provides a runtime environment for your services, enabling you to expose CLR types as services, and to consume other services as CLR types.

Adding the IRestService.cs and RestService.cs classes

Once we add the service(.svc) we need the IRestService.cs type class, which returns the result in XML or JSON as we need it.

Here is an example that prints a string.

This is the IService.cs class code that has the function definition.

[ServiceContract]

    public interface IDataService

    {

        [OperationContract]

        string Warmup(string TEST);

    }

      
TheSPBlog Latest Tweets
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.


Correlation ID:d0bf1c78-a781-40c0-b26e-31a1b5e05149
   Follow TheSPBlog on Twitter
SPBlogTwitter

 Subscribe

  The SharePoint RSS  Gig Werks Mailing List 

 Contact Us






©2009 Gig Werks. All rights reserved. Privacy Policy