June 19, 2017

Accessing Checkbox in SharePoint using JQuery

I couldn't find anything obvious for accessing SharePoint Check Box so chucked this together, hopefully useful for someone else 😉😎
Note: The below code/solution is applicable to accessing check box in a custom SharePoint List forms using SharePoint Designer. To know how to create a custom form in SharePoint Online, read this article Get Current Logged in User & Manager using REST API in SharePoint OnlineAccessing Check Box control in SharePoint is little tricky than accessing the check box in HTML. The reason being, Check Box control is rendered as a table instead of a single control as shown below (Check Box and its preview in developer tools - Chrome):
So, each check box is rendered inside SPAN tag in a table. To access the normal SharePoint controls, we will use either ID or title property but for Check Box it is little complicated.
The actual check box control is in "input" tag 2. The values (Example here: A, B) are inside "label" tag 3. But each control (Yes & No) are represented by ID which is generated by SharePoint 4. If you look at the ID, there is "ff5" which is the ID of the control generated randomly by SharePoint
Now, open the designer, add an ID to the TD of the Check Box so that we can query it easily using JSOM as shown below:
//Get the checked values of Check Box
$("input[id ^= 'tdLanguage']").is(function(){
    var checked = $(this).is(":checked"); //is checkbox checked (true/false)?
    var theVal = $(this).next().text();  //get the label for this checkbox
    alert(checked + " : " + theVal);
//Check if checkbox is selected or not
//Check box checked or not - single check box type in SharePoint
$("td[id='tdLanguage'] input:checkbox[name*='ff5']").is(":checked")
//Check all the values of checkbox
$("td[id='tdLanguage'] input:checkbox[name*='ff5']").attr('checked',true )
//Uncheck /Clear all checkbox values
$("td[id='tdLanguage'] input:checkbox[name*='ff5']").attr('checked',false )
*** "'tdLanguage'" is the ID of the SharePoint Radio Button Control, "ff5" is the unique ID of the SharePoint Control in your List form. Change this ID according to your form to get the exact result.
Please share your valuable comments which will make me write more and also share this post using the below social buttons to others.
Happy Share(ing)Point! 👍

June 1, 2017

SharePoint Online Software Boundaries and Limits

Size limit and Number of items that can be synced
1.     You can sync up to 20,000 items in your One Drive for Business library. This includes folders and files.
2.   You can sync up to 5,000 items in a SharePoint library. This includes folders and files. These are the libraries that you find on various SharePoint sites, such as team sites and community sites. This also includes syncing other people's One Drive personal sites that you may have access to. You can sync multiple SharePoint libraries.
3.     In any SharePoint library, you can sync files of up to 2 GB
Character limit for files and folders
  1. In SharePoint Online, file names can have up to 256 characters
  2. Folder names can have up to 250 characters
  3. When you sync One Drive for Business with SharePoint Online, a folder named "forms" isn't supported at the root level for a list or library. This occurs because "forms" is a hidden default folder that's used to store templates and forms for the library.
  4. Any file that’s currently open by an application (for example, an Excel .xlsx file) can't be synced by One Drive for Business.
  5. To sync the file, close any application where the file is currently being used, and then sync the file.
  6. The following characters in file names aren't supported when you sync One Drive for Business with SharePoint Online: (\, /, :, *, ?, “, <, >, |, #, %, ~)
SharePoint Online Site Collection
1. SharePoint Online Site collection package details below:
  • Small Business: a single Team Site Collection
  • Midsize Business plans: limits 20 Team Site Collections
  • Enterprise, Education, and Government: limits to 10,000 Team Site Collections
2. In all options, just single Public Web Site Collection can be created, 1TB for My sites, 2000 site/sub site per site collection
Developer Limits
Only Sandbox Solutions are designed to allow SharePoint developer to customize/develop on Office365/SharePoint Online
  • No access to file/folder. It means you cannot use IO API commands
  • Only be deployed at a site collection level scope (not farm scope)
  • No access to web.config
  • PDF Documents cannot be opened in the browser
  • Restrictions to access security
  • Cannot overuse system resources
The following table describes the limits for SharePoint Online in Office 365 Business Essentials and Office 365 Business Premium:
Storage per user (contributes to total storage base of tenant)
500 megabytes (MB) per subscribed user
Storage base per tenant
10 GB + 500 MB per subscribed user + additional storage purchased
For example, if you have 10,000 users, the base storage allocation is approximately 5 TB (10 GB + 500 MB * 10,000 users)
You can purchase an unlimited amount of additional storage
Site collection storage limit
Up to 1 TB per site collection. (25 GB for trial).
SharePoint admins can set storage limits for site collections and sites. The minimum storage allocation per site collection is 100 MB
List view threshold limit in site libraries, including files and folders
You can sync up to 5,000 items in site libraries, including folders and files
Site collections (#) per tenant
500,000 site collections (other than personal sites)
Sub sites
Up to 2,000 sub sites per site collection
File upload limit
2 GB per file
Number of external user’s invitees
There is no limit to number of external users you can invite to your SharePoint Online Site Collections

May 18, 2017

Site Mailbox is removed from SharePoint Online

I tried to create a Site Mailbox this morning, in SharePoint Online and came to know this feature is no longer supported in SharePoint Online.

Tried to understand it in detail and following are the updates:
  1. Microsoft is notifying Office 365 customers that access to Site Mailboxes is being removed from SharePoint Online, and no more Site Mailboxes can be created from March 2017 onward.
  2. Site Mailboxes originally appeared as a feature of Exchange Server 2013. Site Mailboxes appended together an Exchange mailbox with a SharePoint site to allow users to collect email conversations in a single location, as well as access shared documents from both Outlook and SharePoint.
  3. If you are using Site Mailboxes, then you have got some migration work to look forward to. Otherwise, if you are looking for “email-centric collaboration”, Office 365 Groups are the way to go (Reference: Microsoft Community Groups).

May 5, 2017

Slide Library in SharePoint Online

When you try to migrate from SharePoint 2010 to SharePoint Online (Office 365), Slide Library template is not listed as app in the Create App section.
You can still get it with a direct URL. I would not depend on it being there forever as the Slide Library is officially not in SharePoint 2013, but for now you can create one.
The direct URL to create the old Slide Library:

Update 22/05/2017:
Even though above solution works as expected in SharePoint 2013 & SP Online it is advisable not to use since Microsoft may remove this feature in future.

February 27, 2017

Challenges to be considered before migrating from SharePoint 2010 to 2016

  1. Identifying the business owners for each site / site collection
  2. Data Cleansing - identifying the old contents/obsolete data for archiving
  3. Identifying the intranet links embedded inside the documents (while migrating to SharePoint Online) 
  4. Optimize and define databases - Perform re-organization of content. For example, as you determine what will be brought over to the new environment, you may end up archiving some ‘less-used’ content to a ‘read-only’ or ‘slower’ server.Consider moving read only data to a separate SQL instance or even separate SQL farm where the data is read-only. You may also want to consider moving less frequently used content to SQL servers that have less resources and keep the higher performing SQL servers for the frequently used/collaborative content, perhaps your ‘old’ SQL server.
  5. Size of data to be migrated – this will affect the migration time
  6. Any good migration should involve a content audit. Data security (legal & audit implications should be considered) –confidential documents which are restricted for internal use cannot be migrated to SharePoint Online. Key ‘things’ like ‘Highly Visible or Critical Areas’, ‘Executive Users Permissions’, ‘Large AD Group Users’ assignments, ‘Highly Used’ Features, ‘Heavy Customizations’, Integration with other systems, etc. must be identified, and documented in order to identify where the critical data and functionality exists. Depending on the access to the content, an appropriate ‘services’ and ‘security’ model can be included in the SharePoint migration planning (and later validation).
  7. SharePoint 2010 cannot be directly migrated to 2016 and it needs to be migrated to 2013 and then to 2016 version (when Database upgrade approach is opted as an option for migration)
  8. If tool based migration (like Sharegate, Metalogix) approach is used, then direct migration from 2010 to 2016 is possible
  9. 10 GB is the new soft limit for file sizes in SharePoint 2016
  10. If custom master page is used, then the existing master page needs to be upgraded /recreated from 2010 -2013 –then 2016 version for using it in SharePoint 2016
  11. While using database upgrade (2010 to 2013 and then to 2016) approach, SharePoint 2010 sites will be made read only during migration process
  12. Any custom farm solutions should be upgraded to SharePoint 2016 before use
  13. The same connectivity/integrations to external systems in SharePoint on-premises environment may not be achieved in SharePoint Online
  14. New user ID’s needs to be created in SharePoint Online. New/ existing permission levels needs to be created in SharePoint Online
  15. End users needs to be trained for new UI/navigation, etc.

January 18, 2017

Enable "Open with Explorer" Option In SharePoint Online Document Libraries In Microsoft Edge Browser

Happy New Year 2017 to all readers and wish you all success in this year 😃😃😃

I was asked by my colleague who is from different Technology stream about “Open with Explorer” option disabled in SharePoint Online document libraries in Microsoft Edge browser.
Microsoft Edge browser has a new look and feel than other IE versions and obviously it is going to take a while for all end users to get used to / to know the various options in it.I tried checking the permissions of the user and he has admin permissions but still the user couldn’t open the library with explorer option as shown below:
As usual searched for various articles and understood about the features of Microsoft Edge browser.Read this KB article about Microsoft Edge and SharePoint behavior:

Navigate to the edge browser -> click on Open with Internet Explorer as shown below:

Now, the SharePoint site should open in the IE 11 (latest version before Microsoft Edge is released).As expected, in IE 11, Open with Explorer option is enabled and everything works perfectly as shown below:
If you want to sync, click on Sync and it will open the One Drive -> Sign in -> Sync the data.

Hope this helps you!
Please share your valuable comments which will help me write more and share this post using the social buttons below.