Wednesday, November 16, 2016

Checking selected value in all dropdowns using jquery

Below code works if you have multiple drop downs where you want to check the selected value in all drop downs  in the form and see if this value is selected already, if selected then will show an alert message and change the selected value of that particular drop down

Add the "OnChange" in dropdown events as this onchange="ChkCurrent(this);
where 'id' is current value dropdown
 function ChkCurrent(id) {   
            var ddlValues = new Array();
            $("[id*='ddlstsCurrM']").each(function (i) {
                if ($(this).val()== 1) {

            if (ddlValues.length > 1)
                alert("This value has been already selected");
                var ddlid ="#";


Thursday, August 11, 2016

Minimizing/hiding sub tasks on a tasks list in office 365

By default sharepoint will show all the subtask on a tasks list to minimize them use the below script by adding script editor webpart on tasks pages

<script src="https://sharepointsiteurl/SiteAssets/JS%20file/jquery-1.9.1.js" type="text/javascript"></script>
    <script type="text/javascript">
        $(document).ready(function () {


Saturday, July 23, 2016

Workflows getting suspended when sending emails outside company domain using SharePoint designer in O365

SharePoint 2013 designer workflows does not allow users to send emails out side their company domain the alternative is to start 2010 workflow from 2013 with email functionality or degrade the workflow version to 2010

Wednesday, July 13, 2016

Retrieving all list items from a list which has crossed threshold limit in O365/sharepoint online using REST

To retrieve list item from a list which has already crossed the threshold limit i.e. 5000 items in 0365
this can only be done if we have indexed the list previously, i mean we can only query a list which has indexed column which has been created while list creation, in office 365 we cannot increase the threshold limit more than 5000 but we have an option to do that in on perm for up to 20000 items

increasing a threshold limit is not suggested by Microsoft, this will effect the performance, the only option to do this is to pull up data from a large list(more than 5000) in batches, you can batch data up to 4999 in once rest call and need to run untill the total count of the list completes

in the below code "ArchivedList" object will store all the items from a list in batch basis
use the script editor webpart to check this code.

<script src="https://yoursharepointsite/SiteAssets/Java%20Script%20Files/jquery-1.10.2.js"></script>  
<script type="text/javascript">
var ArchivedList = [];
var ListTest=[];
var i=0;
       function () {

           var spHostUrl = "https://yoursharepointsite";
           //Build absolute path to the layouts root with the spHostUrl
           var layoutsRoot = spHostUrl + '/_layouts/15/';
           $.getScript(layoutsRoot + "SP.Runtime.js", function () {
               $.getScript(layoutsRoot + "SP.js", getListData);
function getDataFromUrl(endpoint) {
     return jQuery.ajax({
         url: endpoint,
         method: "GET",
         headers: {
             "Accept": "application/json; odata=verbose",
             "Content-Type": "application/json; odata=verbose"
function getLargeList(nextUrl) {
     var dfd = new $.Deferred();
     if (nextUrl == undefined) {
     getDataFromUrl(nextUrl).done(function (listItems) {
         var items = listItems.d.results;
         var next = listItems.d.__next;
         $.when(getLargeList(next)).done(function (){
     return dfd.promise();
function getListData() {
     var documentLibName = 'Archived';
     https://yoursharepointsite/_api/web/lists/getbytitle(documentLibName)/items?$select=Title,No_Days,Current_x0020_State,Form_x0020_Type,Modified,ContentType/Name,ContentType/Id&$expand=ContentType&$filter=(Modified ge '"+strtDate +"' and Modified le '"+endDate+"') and startswith(ContentTypeId,'0x0120') &$top=200
     var listServiceUrl1= _spPageContextInfo.webAbsoluteUrl + "/_api/web/lists/GetByTitle('Archived')/Items?$Select=Title,No_Days,Current_x0020_State,Form_x0020_Type,Modified,ContentType/Name,ContentType/Id&$expand=ContentType&$filter=startswith(ContentTypeId,'0x0120')&$top=200";
     var listServiceUrl = _spPageContextInfo.webAbsoluteUrl + "/_api/web/lists/GetByTitle('" + documentLibName + "')/Items?$Select=Title,No_Days,Current_x0020_State,Form_x0020_Type,Modified,ContentType/Name,ContentType/Id&$expand=ContentType&$top=200";
     $.when(getLargeList(listServiceUrl)).done(function () {


Deleting data from workflow history list using JSON 

copy past the below code in script editor webpart.

<script src="https://sharepoint_yoursite/subsitename/SiteAssets/Java%20Script%20Files/jquery-1.10.2.js"></script>
    <script type="text/javascript">
var clientContext;
var website;
var oList;
var cnt = 0;
var collListItem;
// Make sure the SharePoint script file 'sp.js' is loaded before your code runs.
SP.SOD.executeFunc('sp.js', 'SP.ClientContext', sharePointReady);

// Create an instance of the current context.
function sharePointReady() {
    clientContext = SP.ClientContext.get_current();
    website = clientContext.get_web();
    oList = website.get_lists().getByTitle('Workflow History');

    var camlQuery = new SP.CamlQuery();
    this.collListItem = oList.getItems(camlQuery);

    clientContext.load(collListItem, 'Include(Id)');
    clientContext.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed));

function onQuerySucceeded(sender, args) {

    var listItemInfo = '';
    var listItemEnumerator = collListItem.getEnumerator();

    while (listItemEnumerator.moveNext()) {
        var oListItem = listItemEnumerator.get_current();
        var ID = oListItem.get_id();
        var oListItemDel = oList.getItemById(ID);
        clientContext.executeQueryAsync(Function.createDelegate(this, this.onDeleteSucceeded), Function.createDelegate(this, this.onDeleteFailed));
        console.log(ID + " : Deleted");

function onQueryFailed(sender, args) {
    console.log('Request failed. ' + args.get_message() + '\n' + args.get_stackTrace());

function onDeleteFailed(sender, args) {
    console.log('Delete failed. ' + args.get_message() + '\n' + args.get_stackTrace());

function onDeleteSucceeded(sender, args) {
    cnt = cnt + 1;
    console.log('Delete success : ' + cnt);

Saturday, June 18, 2016

SharePoint 2016: New site contents experience

I though of you showing all new site content which is going to come up in SharePoint 2016, below is the new look :)

New features in SharePoint 2016

I am listing down some of the import new features for SharePoint 2016, i believe you find this interesting, all the references are from MSDN

·        Fast site collection creation using PowerShell command "SPSiteMaster"
·        SharePoint Server 2016 Central Administration is now provisioned on the first server in a farm by default when using the SharePoint Products Configuration Wizard. Central Administration is not provisioned on additional servers in a farm by default.
You can provision or un-provision Central Administration on individual servers in a farm, no matter what the server role is by using the following methods:
·        The Services on Server page on Central Administration > System Settings
·        Windows PowerShell cmdlets:
·        The psconfig.exe -cmd adminvs operation
The SharePoint Products Configuration Wizard
Hybrid sites features
This feature allows your users to have an integrated experience while using SharePoint Server and SharePoint Online sites:
·        Users can follow SharePoint Server and SharePoint Online sites, and see them consolidated in a single list.
·        Users have a single profile in Office 365, where all of their profile information is stored.
Large file support
·        Previous versions of SharePoint did not support uploading or downloading files larger than 2,047 MB. SharePoint 2016 now allows you to upload or download larger files. You can configure the desired maximum file-size limit on a per-web application basis in your SharePoint farm.
SharePoint Foundation is no longer available in the SharePoint Server 2016 release.

SharePoint Server 2016 doesn't support the standalone install option, so it is no longer available in the setup program. Use the MinRole during installation and choose one of the available install options. The Single Server Farm option where everything is installed on the same computer is supported for dev/test/demo purposes. When you use this option, you must install SQL Server yourself and then run the SharePoint Server 2016 farm configuration wizard

ForeFront Identity Manager client (FIM)

Earlier versions of SharePoint used ForeFront Identity Manager client (FIM) to synchronize between Active Directory and SharePoint. SharePoint Server 2016 no longer uses FIM as the synchronization client. The default process is Active Directory Import. You can also use any synchronization tool such as Microsoft Identity Manager 2016, or any third-party tool.

Excel Services in SharePoint
Excel Services and its associated business intelligence capabilities are no longer hosted on SharePoint Server. Excel Services functionality is now part of Excel Online in Office Online Server (this is the next version of Office Web Apps Server), and SharePoint users can use the services from there
If you currently use Excel Services in SharePoint 2013 and upgrade to SharePoint Server 2016 you must also deploy Office Online Server with Excel Online to ensure Excel Services functionality remains available.
Mini Roles
By using the new MinRole feature in SharePoint Server 2016, SharePoint farm administrators can define each server’s role in a farm topology. The role of a server is specified when you create a new farm or join a server to an existing farm. SharePoint automatically configures the services on each server based on the server's role, and the performance of the farm is optimized based on that topology.
Server role
Service applications, services, and components that serve user requests belong on Front-end web servers. These servers are optimized for low latency.
Service applications, services, and components that serve backend requests (such as background jobs or search crawl requests) belong on Application servers. These servers are optimized for high throughput.
Distributed cache
Service applications, services, and components that are required for a distributed cache belong on Distributed Cache servers.
Service applications, services, and components that are required for searching belong on Search servers.
Custom service applications, services, and components that do not integrate with MinRole belong on Custom servers. The farm administrator has full control over which service instances can run on servers assigned to the Custom role. MinRole does not control which service instances are provisioned on this role.
Single-server farm
Service applications, services, and components required for a single machine farm belong on a Single-Server Farm. A Single-Server Farm is meant for development, testing, and very limited production use. A SharePoint farm with the Single-Server Farm role cannot have more than one SharePoint server in the farm.


SharePoint 2016: New document library experience in O365/SharePoint online

Today morning i have seen a popup asking to experience the new document library changes in our company website, check the new changes for document libraries, hope you love this.

Now we can see folders in a list or in a tiles view and change the metadata fields and save it as a view

Wednesday, June 15, 2016

Error: Sorry something went wrong...the file … has been modified by … on in document library or document set

Issue: i am seeing the above error while updating an item inside document library with document set content type, it is happening while updating the item using JQuery code in office 365 with REST calls, and i am do that update for checking out(updating a custom column called checkout) document set and then updating the field columns, so i am seeing this error for the second update of item properties for a document set.


I have resolved this issue by removing the versioning from that particular document library
and the also unchecked the "Automatically update the workflow status to the stage name" and the other JQuery code change which may help resolving the issue is to reload the list before doing a second update using CSOM

Wednesday, February 17, 2016

K2 Vs Nintex workflows for SharePoint

·         Good tool for representing processes visually
·         Support for delivery of data to process approvers and other stakeholders that includes the information they need to perform their role in the process in a friendly format. Ability to show them the data they need to make a decision on a variety of devices, and to record their decisions.
·         Good tools for monitoring and reporting process performance and identify delays.
·         Nintex Workflow is GUI base and easy to use. It is suited for workflows that are not too complex. It would be great to have more in depth training and the user guide has room for improvement as well
·         Nintex is a great tool for a logical, tech-minded individual without official development skills.

·         K2 as has best support and great community base
·         Nintex lags in support
·         User friendly
·         Reporting capability
·         Auditing capability
·         Workflow and business process management
·         Line of Business Data integration
·         Good for large data pulling
·         Easy upgrade to new versions
·         Non-technical users can implement somewhat complex solutions.
·         Email notifications easy.
·         Can see workflow task history visually.
·         Administration for Nintex is easy
·         We found SharePoint's built-in process tools clumsy, hard to re-use, and not very powerful or flexible.
·         Getting setup to where you're actually start using the product can be quiet complex and the instructions are not quite clear
·         Error messages are completely vague, making it extremely difficult to debug.
·         Failures occur for random reasons.
·         Error notifications get sent out too frequently which confuse users.
·         Have performance issue when pulling larger lists
·         Support nightmare for failed workflows.
·         K2 blackpearl (enterprise) has a fixed cost for unlimited users and servers
·         Nintex has a price per web front-end.  This is key consideration when farming out multiple SharePoint front-ends.
·         K2 blackpearl provides exclusive activity/event library addressing common systems and scenarios ( AD integration for user management, Exchange integration, SAP, Salesforce,SharePoint integration for actions such as document management, user management, CRM). It also provides excellent framework to connect to LOB systems using Smart Objects. This helps developer’s focus on core process logic than interface details.
·         Nintex also is very tightly integrated with SharePoint and lacks integration ability to external LOB in the enterprise.
·         It also connects to databases and CRM systems, or integrating your SharePoint content with social media platforms
·         K2 is for medium to large budget, scaling to enterprise in IT pro-environment
·         Nintex is best suited for small business solutions which deals with lesser data and business can easily create workflows without any developer