Jean Paul's Blog

There are 2 types of People in the World, One who Likes SharePoint and..

    Advertisements
  • Microsoft MVP

  • MindCracker MVP

  • CodeProject MVP

  • eBook on SharePoint 2010

  • eBook on Design Patterns

  • eBook on Windows Azure

  • NLayers Framework @ CodePlex

  • MSDN Forums

  • .Net vs. Java

    Due to Public Demand
  • Advertisements

Archive for January, 2016

Item Level Permissions and Code Access

Posted by Paul on January 29, 2016

Item Level Permissions and Code Access

In this article we can explore how Item Level Permissions behave in Code Access scenario.

Item Level Permissions

We can enable Item-level Permission on a list so that only the Creator will be able to Read the item.  For other users the item won’t be displayed.

As an Administrator, you can go to the List > List Settings > Advanced Settings to enable Item-level Permissions.

i1

Testing from Browser Access

Create a new item as Administrator User.

i2

Now login as a different User who is just a Contributor.  You won’t’ be able to see the Admin item now.

i3

Now create a new item.

i4

Now login back as the Administrator or Site Owner & You can see both the items.

image.png

Site Collection Administrator or Site Owner can view all the Use Items.

Testing from Code Access

Now let us see the Item-level Permission applies to Code Access as well.  For this I am using CSOM Code with/without Network Credential class.

By default the code runs under Login User which is Administrator.

static void Main(string[] args)

{

ClientContext context = new ClientContext(“http://sharepoint“);

List list = context.Web.Lists.GetByTitle(“Restricted Contacts”);

ListItemCollection items = list.GetItems(CamlQuery.CreateAllItemsQuery());

context.Load(items);

context.ExecuteQuery();

foreach (var item in items)

{

Console.WriteLine(item[“Title”]);

}

 

Console.ReadKey(false);

}

Executing the Code you can see both the items are displayed.  Since we are Administrator user now.

i5

Now apply the Contributor User Credential to test the User Context.

ClientContext context = new ClientContext(“http://sharepoint“);

context.Credentials = new NetworkCredential(“tim”, “Welcome123”);

i6

This concludes that Item-level Permission applies to Code Access as well & Site Collection Administrators or Site Owner can view all items in both browser & code access scenario.

image.png

Item-level Permissions is a great feature.  Without this we would have required custom code to break the permission & assign permission to the created user.

References

http://bit.ly/1PYkb8o

Summary

In this article we have explored Item Level Permissions & CSOM Code with different User Contexts.

 

Advertisements

Posted in SharePoint, SharePoint 2013, Uncategorized | Leave a Comment »

BCS Error – Access denied by Business Data Connectivity

Posted by Paul on January 23, 2016

You will get the following error while first time configuring BCS.

· Access denied by business data connectivity.

image

Solution

Following would be the solution.

Open Central Administration > Manage Service applications > Click Business Data Connectivity Service.

image

In the appearing page click on the Set Metadata Store Permissions ribbon item.

image

You will get the following page. Here do the following:

· Enter Everyone and click Add button

· Check all the permissions listed below

· Check the Propagate Permissions too

Click OK button.
image

Now retry your BCS List in SharePoint.

Summary

In this post we have explored a common error while configuring BCS & steps to resolve it.

Posted in SharePoint, SharePoint 2013 | Tagged: , , | Leave a Comment »

Insert using REST API

Posted by Paul on January 23, 2016

In this article we can explore a simple code to Insert an Item using REST API.

Contacts List

Create a Contacts List for our purpose.

image

Script Inclusion

Following are the script files you need to include:

1. JQuery https://jquery.com/download/

2. JSON2 https://www.drupal.org/project/json2

You can copy the following script code with Microsoft & Yandex CDN links.

http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.12.0.min.js

http://yandex.st/json2/2011-10-19/json2.min.js

Insert Code

Following is the Insert Code to Insert an item.

function test()

{

CreateListItemWithDetails(“Contacts”, _spPageContextInfo.webAbsoluteUrl, “New Contact”, success, failure);

}

function success()

{

alert(“success”);

}

function failure()

{

alert(“failed”);

}

function CreateListItemWithDetails(listName, webUrl, newItemTitle, success, failure) {

var itemType = “SP.Data.” + listName + “ListItem”;

var item = {

“__metadata”: { “type”: itemType },

“Title”: newItemTitle

};

$.ajax({

url: _spPageContextInfo.siteAbsoluteUrl + “/_api/web/lists/getbytitle(‘” + listName + “‘)/items”,

type: “POST”,

contentType: “application/json;odata=verbose”,

data: JSON.stringify(item),

headers: {

“Accept”: “application/json;odata=verbose”,

“X-RequestDigest”: $(“#__REQUESTDIGEST”).val()

},

success: function (data) {

success(data);

},

error: function (data) {

failure(data);

}

});

}

Invoke Code

Following would be the Invoke Code.

<input type=”button” value=”Click Me..” onclick=”javascript:test();”

Testing Code

You can use a new page & Content Editor web part to test the above code. On successful insert you should be getting the message below.

image

You can also verify the new item in the Contacts list.

image

This concludes Insertion using REST API code.

References

http://bit.ly/1R7kB11

Summary

In this post we have explored how to Insert an Item using REST API.

Posted in SharePoint, SharePoint 2013 | Tagged: , , | Leave a Comment »

When to use BCS in SharePoint?

Posted by Paul on January 17, 2016

I have found that Non-SharePoint Guys are recommending BCS (Business Connectivity Services) without Rationale.  BCS is a good feature, but we have to understand the Costs & Implications before blindly using it!

Advantages

Following are the scenarios where BCS can turn to be an advantage:

  • Leverage You have an existing Database Table which users are currently updating.  In this case BCS provides a leverage of External List to connect to this table.  Thus SharePoint users can also work on the Database Table in a synchronized manner.  No additional coding / synchronizing efforts.
  • Support All editions of SharePoint On-Premise supports BCS.

Disadvantages

Following are the disadvantages of using BCS for new systems:

  1. SharePoint Online Not all Plans of SharePoint Online supports BCS.  So if you are designing a product that should be living in heterogeneous client environments – think before you decide.  Check References for more information.
  2. Item-level Permissions BCS do not support Item-level permissions since the data is residing on a different source like SQL table.
  3. Alerts Alerts are not supported in BCS External Lists.
  4. User Context You will need additional configuration efforts to Impersonate the User.
  5. Secured Store Service You might get into SSS overheads based on the Impersonation Models.
  6. Authentication Method Based on client SharePoint environment you may face difficulty in choosing right Authentication Method.  Check References for more information.
  7. Firewall Issues Since External Systems or SQL Databases live in Firewall Or Behind the scene infrastructures, there will be additional Configuration & Troubleshooting Efforts for a successful BCS Connection
  8. Automation Deployment If you are using Automation Deployment Scripts, you will need additional R&D time for writing the accurate BCS deployment steps.

Note

BCS can turnout to be a Leverage or Liability based on your Current & Future Requirements

References

https://technet.microsoft.com/en-us/library/sharepoint-online-service-description.aspx

http://sharepointpromag.com/sharepoint/6-lessons-developing-business-connectivity-services-solution

https://technet.microsoft.com/en-us/library/jj219580.aspx

Summary

In this post we have examined few good & bad cases of using BCS.

Posted in SharePoint, SharePoint 2013 | Tagged: , , , | Leave a Comment »

SharePoint Page Performance Optimization

Posted by Paul on January 7, 2016

In this article we can explore few options to improve SharePoint Page Performance.

image

Page Performance

The usual NFR (Non-Functional Requirement) value for Page Response time is 3 seconds. This is the standard for a normal Intranet Deployment Scenario. So if your page is taking more than 3 seconds to load, then it is not a good sign.

SharePoint Page Performance Optimization

Following are few page performance optimization ideas which we can employ. Depending on one or more of the application, we can get up to 80% improvement in page performance.

SharePoint Branding

Implementing proper branding is crucial to Page Performance. The Branding Architect should re-visit the page components and ensure only required components are used in the page. Few of the items are listed below:

1. Do not use Web Part Zone, Content Editor etc. if there are not direct requirement

2. Remove unwanted SharePoint link & JS file references

If you are using Full Page Branding, it is better to start with a clean ASPX page and add the Minimal SharePoint components like JS Links, Form Digest etc.

This step should improve performance by 20%.

Offline Application Cache

If your users are using HTML5 Compatible Browsers, then Offline Application Cache is recommended. This will enable files to be cached in the browser side & reducing round trips.

Up to 80% Performance Improvement can be achieve using this step.

JS Bundling

JS Bundling is combining multiple JS files into a bundle file. This will reduce the number of Network calls to the server. The same can be applied to CSS Bundling as well.

This step should give up to 20% Improvement in Page Performance.

Image Spriting

Image Spriting is combining multiple image files into a single file. This will reduce the number of requests to the server.

This step should give up to 20% Improvement in Page Performance.

AJAX Cache Busting

There seems to be a big delay with Internet Explorer on REST API calls. This can be resolved through AJAX Cache Busting.

The idea here is to add a dynamic query parameter with date/timestamp so that each REST API URL will look unique and the browser will bypass Cache checking.

This should improve 20% in page performance.

JSOM Batching

If you are using multiple REST API calls, you may also consider using JSOM Batching. This can improve 20% in page performance.

image

The Browsers are using multi-threaded mode to fetch the files.

References

http://www.jeanpaulva.com/index.php/2015/12/02/cost-of-sharepoint-branding/

Summary

In this article we have explored few options to improve SharePoint Page Performance.

Posted in SharePoint, SharePoint 2013 | Tagged: , | Leave a Comment »