Collab365 Summit - May 10th-12th 2016 - Live from Microsoft HQ

Collab365 Summit - May 10th-12th 2016 - Live from Microsoft HQ

Register yourself @ Collab365 Summit 2016

In the Collab365 team on the 10th, 11th and 12th of May 2016 for an incredible amount of SharePoint, Azure and Office365 content. Delivered direct to your device, when you want it and for no cost at all. Catch premium keynotes across all 3 days. Sessions designed and delivered for IT Pro, IT Dev and Business delegates.

Introducing brand new Summit Experience for 2016

Watch Live

Watch the LIVE SHOW streamed direct from Redmond or catch the recorded sessions from top speakers around the world. If you are a seasoned pro or just starting out on your career with SharePoint and Office 365 we have plenty to help you begin your skills journey 

Learn Lost

100 sessions of amazing content brought to you by Microsoft - Direct from MS HQ and beyond, community experts and evangelists from right around the globe. Watch Dev sessions, IT Pro and Business sessions. It's all free to attend and is guaranteed to educate.

Have Fun

As well as live sessions, live chat and real time twitter feeds, we have been adding more spice to the mix in the form of 2 real-time, tech based, fun as heck quizzes. Compete against your peers, win prizes and unlock new learning opportunities!

Microsoft Product team speakers

Bill Baer and Raman Sharma	SharePoint
Jeremy Thake	Office 365 – Product Manager
Sonya Koptyev	Office 365 – Product Manager
Mark Kashman	Office 365 – Product Manager
Chris McNulty	Office 365 – Product Manager
Reuben Krippner	Office 365 - Director
Christophe Fiessinger	Enterprise Social Group

Feature Dependency SharePoint 2013

Feature Dependencies in SharePoint 2013 - Base Site Features

The feature that depend another feature to work correctly on the site called feature dependent.

In SharePoint 2013, all most all site template has its own dependency on other features.

Example,

In team site navigation hierarchies with managed meta data, requires publishing feature dependency.

Team site with default list and list template requires few feature dependencies.

Or, if you want to provision the list with event receiver, you may prefer to split the even receiver logic, site column and content type in to different feature. Finally, your list will group all the features to work as expected. In that case, no features will be activated with dependent features are activated first.

First site column features must be activated, the content type that relies on the column must be activate and finally the list definition and event receiver.

Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES

Open the “BaseSite” folder and “Feature example, it will be shown like this image,

So the base site feature id: B21B090C-C796-4b0f-AC0F-7EF1659C20AE has its dependencies on rounded blue bordered box.

Feature Name	Feature GUID
Local Directory Site Control	14AAFD3A-FCB9-4bb7-9AD7-D8E36B663BBD
Portal Layouts	5F3B0127-2F1D-4cfd-8DD2-85AD1FB00BFC
WebPart Adder groups.	2ED1C45E-A73B-4779-AE81-1524E4DE467A
Document routing resources	0C8A9A47-22A9-4798-82F1-00E62A96006E
Record Resources	5BCCB9A4-B903-4fd1-8620-B795FA33C9BA
Social Site	4326E7FC-F35A-4b0f-927C-36264B0A4CF0
Search WebParts	EAF6A128-0482-4F71-9A2F-B1C650680E77
Search templates and resources	8B2C6BCB-C47F-4F17-8127-F8EAE47A44DD
Item Form recommendations	39D18BBF-6E0F-4321-8F16-4E3B51212393

Types of Features:

1. cross site scoped : The feature can have it dependency of the another feature that is scoped its  high level hierarchies. Example , Publishing feature in the web (sub site) scope requires the site collection scoped Publishing Infrastructure should have been activated prior to be activated on the site level.
2. Same site scoped : Feature can have its dependency of the other feature that is scoped on the same site scope level.
   
   Example, A feature that provisioning the site columns should be activated before the feature that creates the content type that relies on the already available site columns in the site and its associated form template on the site.

Rules of the Feature:

1. Feature can be set to visible or hidden through its feature definition file (Feature.xml)
2. Hidden feature cannot have any feature dependency.
3. Hidden feature can activated ,deactivated,installed and uninstalled through only Power shell command,So farm admin have full control on it.
4. Feature dependencies cannot be chained.

jQuery ajax method and SharePoint list

Using jQuery ajax method we can initiate the RESTful request to retrieve the SharePoint List Items that has been designated as resources through end point.

Once the end point has been identified, the query will be used to make CRUD operation using OData protocol.

Here is the simple code snippet and bit explanation behind the jQuery ajax call and the call back method.

All you need to is to pass the SharePoint's REST endpoint URI as url parameter to ajax method.
And request what data format has to be returned by the request by specifying the header format.

 $(document).ready(function () {
            $.ajax(
                {

                   url: "http://win-0nvq2rjqgo2/_api/web/lists/getbytitle('trac')/items",
                    mehtod: "Get",
                    headers: { "Accept": "application/json; odata=verbose" },
                   dataType:"json",
                  success: function (data) {
                        SuccessMessage(data)
                    },

                     error: function (data) {
                     //var parsedJson = $.parseJSON(data.responseText);
                       console.log(data.responseText);
                        //Logging the error details
                  }
                });
        });


        function SuccessMessage(w) {
         $.each(w.data.results, function (index, item) {
         //logic to show the output in html page
                $('#itemsInDiv').append(item.Title + "---->" + item.FName);
            });

When the request has been processed and the data will be passed to success handler by SharePoint.


To get the clear exception, log the error details using data.responseText. Here I just renamed the list track to trac and logged the exception details.

Microsoft Mechanics

Microsoft Mechanics

Microsoft's new initiatives to bring all the engineers those are continuously working for improving the Microsoft Products such as Azure,Office 365,Office Desktop version,Exchange Server 2016,SharePoint,OneDrive and Skype for business together and imparting the knowledge to IT workers through Video platform.
Checkout the blogs / Video
Microsoft Mechanics

A true collaboration feature in Outlook 2016

The new feature in Outlook 2016 allows you to aggregate all your files irrespective of the location either OneDrive, local file system, shared location and of course SharePoint.

While you trying to attach the document while email compose, you will find all these history on "Recent Items" in the "Attach File"'s spinner.
It will be organized and categorized by the Outlook date wise.

People Picker Field Value through jQuery

To retrieve the SharePoint people picker values through jQuery use this one line code

var User = $("textarea[title='People Picker']").val().split("\\");

CSOM LookUp Field value retrieval

Here is a simple code snippet to retrieve the LookUp value from the List Item.
You need to casting the retrieved item as FieldLookupValue to process further.

 ClientContext ctx = new ClientContext("http://win-gc3f02d6lkq/sites/apps");
            var list = ctx.Web.Lists.GetByTitle("Cities");
            CamlQuery query = new CamlQuery();
            query.ViewXml ="";
            ListItemCollection items = list.GetItems(query);
            ctx.Load(items);
            ctx.ExecuteQuery();
            foreach(var item in items)
            {
                var lookUpId = item ["Country"] as FieldLookupValue;
                Console.WriteLine(item["Title"].ToString() + "--" + lookUpId.LookupValue);
            }
            Console.ReadLine();

This will lists the city name along with country field that has been used as lookup column from the Countries Master List in the "Cities" list.

LookUp Column Caml Query

If you want to query the Lookup column in the SharePoint, you need to specify the value type "Lookup" in CAML query.

Example Code

Allow unsafe updates and Form digest

When you SharePoint application throws this error
Microsoft.SharePoint.SPException: The security validation for this page is invalid.

You need to ensure to use the "AllowUnsafeUpdates" property of SPWeb class has been set to true where ever you are trying to update the SharePoint items.
After you update revert back to true in your code.

Because SharePoint restricts the cross-site script injection when you are trying to update or change over the HTTP Requests.

FormDigest  is the counterpart to AllowUnsafeUpdates in Server object model in Client side object model.
All SharePoint Forms uses the "FormDigest" value by default.Just open any of the edit form in SharePoint in the browser and see the "View Source code" of the page.
You can see the "FormDigest" value.

Attempted to perform an unauthorized operation

Attempted to perform an unauthorized operation Visual studio,SharePoint Deployment

Error occurred in deployment step 'Activate Features': Attempted to perform unauthorized operation.
If you happen to see this error in your visual studio,then reason is your account has permission to access the Farm but not on your site collection where you trying to deploy the solution.

To resolve this issue Go to your Central Administration-->Application Management header-->Change Site collection administrators under "Site Collection" header.
Add your account try again the deployment.

subsites in sharepoint

this code snippet retrieving all sub sites from the root site in Share point Server 2007

SPSite site = new SPSite("http://win-j40e6cmrcl9/personal/administrator/");
        string[] subsites = site.AllWebs.Names;
        for (int i = 0; i < subsites.Length; i++)
        {
           SPWeb web = site.AllWebs[i];
           Response.Write(web.Name.ToString());
         
        }