Click SharePoint

Microsoft SharePoint Online Code Analysis Framework (MSOCAF)

2011-10-05T13:48:00.000-07:00

SharePoint Online

SharePoint Online is a combination of SharePoint + cloud. Microsoft manages the SharePoint Online for your organization and helps you the leverage the power of SharePoint for your organization globally.

MSOCAF

The MSOCAF tool is used for streamlining the custom solution review Process for SharePoint Online (SPO). MSOCAF solution is used by customers, ISVs and vendors to validate and submit custom solutions.

Before submitting the custom solutions to Microsoft, customers has to validate the custom solutions using MSOCAF tool, this tool detect the code issue and also provides resolution for fixing the issues.

MSOCAF tool has four wizards:

· Analyze

Using Analyze wizard custom solution is analyzed against the set of rules. The custom solution is passed for Folder structure and its content. The code base analyze is a kind of mix of SPDisposeCheck and FxCop utitliy . It checks the custom solution and all the required parameter. If custom solution does not pass MSOCAF analysis than custom solution cannot be submitted to Microsoft for SPO deployment.

· Test deployment

The test deployment wizard helps in deploying the custom solution. The Test deployment wizard uses the “DeploymentManifest.xml” file for deploying the custom solution. This file will reside in the solution package.

· Roll back

After deploying the custom solution using MSOCAF tool. If you feel there is some issues with deployment you can use Roll back wizard to roll back the deployment.

· Submit

The submit wizard is used to submit the custom solution to Microsoft. User can reach to the deployment wizard only if Analysis of the package is successfully passed. While submitted user has to fill the configuration request (CR) Number and submitter’s email ID. User has to agree the agreement and then click on submit button.

How to leverage MSOCAF for other SharePoint custom development?

As the MSOCAF tool provide very strong analyze power for validation the custom solution against various set rules. This helps in writing the custom solution which is of very high standards in terms of design, Security, performance, usage, Naming and Memory management.

How to get MSOCAF?

MSOCAF is free tool available at Microsoft site. Tool can be downloaded from below link https://caf.sharepoint.microsoftonline.com/

How to fill person or group field of form lib using InfoPath?

2011-10-03T16:32:00.000-07:00

Steps:
1. Create Person or group field name TestUser and one more field name HidTestUserName
2. Add the people picker control in InfoPath field
3. Promote the AccountId field value to HidTestUserName field. Refer the below Screenshot.

4. Create workflow for FormDocLib and create step with action of Set Field in Current Item . In this action set the value of TestUser Field.

5. Make sure Start Workflow automatically when an item is created and change options are enabled. Refer the below SS.

How to upload the document using SharePoint client Object Model and set the Properties

2011-10-02T13:53:00.000-07:00

The below code example shows how to upload document from file system to SharePoint using Client Object Model. Also show how to set the properties for Text, Person or group, Checkbox, Managed Metadata columns. Below code refer the excel file to get the file path and column values.

using System;
using Microsoft.SharePoint.Client;
using System.IO;
using System.Data.OleDb;
using System.Data;

class DisplayWebTitle
{
static void Main()
{

string siteUrl = "http://siteurl";
string libraryName = "LibraryName";
string subFolderPath = "";
string metaDataSheetLocation = @"c:\FilePath\FileName.xlsx";

UploadFileInLibrary(siteUrl, libraryName, subFolderPath, metaDataSheetLocation);
}

public static void UploadFileInLibrary(string siteUrl, string libraryName, string subfolderPath, string MetaDataSheetLocation)
{
using (ClientContext clientContext = new ClientContext(siteUrl))
{
DataTable excelData = GetExcelData(MetaDataSheetLocation);

foreach (DataRow dr in excelData.Rows)
{
string fileName = dr["FilePath"].ToString();
string uploadLocation = Path.GetFileName(fileName);
string fileNameStr = Path.GetFileName(fileName);
if (!string.IsNullOrEmpty(subfolderPath))
{
uploadLocation = string.Format("{0}/{1}", subfolderPath, uploadLocation);
}
uploadLocation = string.Format("{0}/{1}", libraryName, uploadLocation);
var list = clientContext.Web.Lists.GetByTitle(libraryName);
var fileCreationInformation = new FileCreationInformation();
fileCreationInformation.Content = System.IO.File.ReadAllBytes(fileName);
fileCreationInformation.Overwrite = true;
fileCreationInformation.Url = siteUrl+ uploadLocation;
Microsoft.SharePoint.Client.File uploadFile = list.RootFolder.Files.Add(fileCreationInformation);
Microsoft.SharePoint.Client.ListItem item = uploadFile.ListItemAllFields;
clientContext.ExecuteQuery();
/*--start taxonomy--- */
List taxonomyList = clientContext.Web.Lists.GetByTitle("TaxonomyHiddenList");

CamlQuery camlQueryForTerm = new CamlQuery();
camlQueryForTerm.ViewXml = @"

"+ dr["Col1"].ToString()+"";

ListItemCollection termItems = taxonomyList.GetItems(camlQueryForTerm);

clientContext.Load(termItems);
clientContext.ExecuteQuery();
ListItem termItem = termItems[0];
string termValue = termItem["ID"] + ";#" + termItem["Term"] + "|" + termItem["IdForTerm"];

/*--End taxanomy --- */

item["TextField"] = dr["TextField"].ToString();

item["PersonGroupField"] = clientContext.Web.EnsureUser(dr["PersonGroupField "].ToString());

item["checkbox"] = dr["checkbox"].ToString();
item.Update()
item["ManagedMetaDataField"] = termValue;
item["ManagedMetaDataFieldTaxHTField0"] = termValue;
item.Update();
clientContext.ExecuteQuery();
Console.WriteLine(fileNameStr + " Uploaded File Successfully");
}

}
}

public static DataTable GetExcelData(string ExcelFilePath)
{
string OledbConnectionString = string.Empty;
OleDbConnection objConn = null;
OledbConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" + ExcelFilePath + ";Extended Properties=Excel 8.0;";
objConn = new OleDbConnection(OledbConnectionString);
if (objConn.State == ConnectionState.Closed)
{
objConn.Open();
}
OleDbCommand objCmdSelect = new OleDbCommand("Select * from [Sheet1$]", objConn);
OleDbDataAdapter objAdapter = new OleDbDataAdapter();
objAdapter.SelectCommand = objCmdSelect;
DataSet objDataset = new DataSet();
objAdapter.Fill(objDataset, "ExcelDataTable");
objConn.Close();
return objDataset.Tables[0];
}

}

How to Setup Retention Workflow using Content hub

2011-10-01T23:03:00.000-07:00

Step 1: Go to Sharepoint Designer save and publish that workflow from the sharepoint designer and save the workflow as a template.

Step 2: Deploy the workflow wsp globally.

Step 3: Activate the Workflow Feature in all old team and my site (Site collection and their sub sites) through Power shell and in all New Sites it will be automatically activated through feature stapling (staple the workflow feature with your site template/defination).

Step 4: Go to the Content Hub site and activate the workflow feature in Site Features

Step 5: After publishing come back to Content hub site and attach this workflow to the content type.

Step 6:Update all content types that inherit from this type with these workflow settings. Here is a snapshot to update all content types that inherit from this type with these workflow settings.

Step 7: Add/Edit retention policy to this content type which will trigger the new deployed workflow under Information management policy settings.

Step 8: After adding/editing retention policy publish/republish this content type so that all the changes we have made will reflect to Old sites (Document Libraries and Documents) and their sub sites(Document Libraries and Documents). For republishing Go to manage publishing for this content type.

Step 9: When Content Type Subscriber Timer job from the Central Administration under Monitoring -> Review Job Definitions category will run then the changes will reflect to this content type. (That will run automatically)

Step 10: Go to your site/subsite where you want this workflow to attach with a Document Library inheriting content type.

Step11: Check the compliance details of existing or newly uploaded document to previously created Document Library. The compliance details will show the retention policy details the workflow details which will be started when retention event will trigger. Refer the Screenshot of compliance details:

When the document is about to expire and retention event is triggered. The workflow will be started.