Google+ API going to be Shutdown

AS you all may know from the March 7,2019 google is going to shutdown the support for the Google+ API. This is going to be the progressive shutdown for the Google+ APIs.

So all the calls with the endpoint to the Google+ APIs will start to fail from the January 28,2019.

Google has already started the process of sending an email to their developers/users who are using the Google+ APIs. Even if you didn’t receive that email you must remove the use of that API or switch to some other api calls.

The most commonly used APIs that are being shut down include:

Google+ integration with mobile and web is also going to shutdown.

As a part of the feature Google Sign in feature is available and they are trying to provide a new visual change for the enterprise organizations.

You can find more details on their blog:

Import Info Path form to the SharePoint Online

How to Export and then Import Info Path form in SharePoint Online?

While I was working with the project for one of my client. I got a requirement to make Info Path form work with the SharePoint Online. As you all may know that Info Path forms are bit tricky unless you have good understanding about that and how they work.

I was working on a provider hosted app. The main usage of this app is to convert the Info Path form in MVC based form and mimic the actual flow of data from Initialization of process to the Finalized/Completed the process.

To achieve this, I have a console application which will read the infopath as xml from sharepoint 2013 on premise site and convert them to the appropriate record for my new SharePoint Online module.

My Console application also export the attachments from the Info Path forms and save them in a document library with the main list column as lookup.

I know this whole conversation can make you confuse.


Let me know if you like to have a look in the console application and a code. I will be happy to assist you on that..


For more info: Visit my SharePoint site :




Comparison between SharePoint Hosted and Provider Hosted App

During my sessions related to the share point I asked the students to define the difference between SharePoint Hosted App and Provider Hosted app. They provide some fundamental differences but no one is able to give proper answer.

So here I am providing a list of differences from the user/client perspective so that you can decide which app approach needs to be chosen for your project work.


SharePoint Hosted Provider Hosted
No server side code, 100% client side code Managed code and high trust
Can be developed using HTML5, CSS, JavaScript, jQuery, ASP.NET Ajax, CSOM, REST API, Silverlight, KnockOut JS, Angular JS Any programming language can be used
Data Storage Locations: SharePoint Online, Content Database Data Storage Locations: ISV Storage, Azure Storage, Content Database.

(ISV – Independent Software Vendors)

Start Page Location: On-Premises, SharePoint Online Start Page Locations: ISV Hosted web site, SharePoint Online, On-Premises SharePoint Online, On-Premises
Can be hosted on either SharePoint on-premises or office 365 Deployed outside  the SharePoint.
Business logic is JavaScript on custom SharePoint pages Business logic is mainly remote server-side code.

SharePoint add-in model does not allow managed code to be installed directly on SharePoint, however it can be hosted in application server and a separate website (eg. on IIS) on in azure.

App usage scenario: An add-in that includes a people picker control and that stores information about SharePoint users in a SharePoint list App usage Scenario: Can be used in situations where SharePoint being consumed as service and/or hosted by a provider. App model is the option if you do not have a on premises installation. Go with this option when you require server-side managed code.
App Components are SharePoint components like SP Features, Custom Actions, Lists, Site Columns, Content Types, BCS models(web scoped), Web and list templates Can connect to any internal or public web service
SharePoint-hosted SharePoint Add-ins do not support event handling, To handle list and list item events, you need to create remote event receivers (RERs), which are web services that run externally to the SharePoint farm or SharePoint Online.
This add-in components are hosted in the isolated add-in domain of your SharePoint farm Can be hosted in any web server or hosting service
Authentication: This uses the privileges of the signed in user Authentication: Uses OAuth or the JavaScript cross-domain library
CRUD Operations: You can use either the REST/OData web service or one of the client object models in SharePoint 2013.

SP.js is available to perform create, read, update, and delete (CRUD) operations on SharePoint data.

CRUD Operations: You can use the REST/OData endpoints in SharePoint 2013 to perform create/read/update/delete (CRUD) operations on data in the add-in web. You can write server side code any technology you like to perform this CRUD operations.
These apps don’t work with SAML Claims authentication provider with ADFS 2.0 Any SharePoint component that can be in a SharePoint-hosted add-in can also be in a provider-hosted add-in.

Microsoft Azure – Automate Creating, Developing and Deploying Azure Websites

Microsoft Azure is a quick and easy way to create and deploy Web sites or APIs for your cloud consumers. Much has been written on different aspects of Azure Websites, including security, deployment and so on. It’s always a challenge to bring this information into a real-life implementation. In this article, I’ve pulled together these various facets to help you quickly create a production-ready Azure Website. I’ll walk you through the end-to-end lifecycle of creating, deploying, configuring and monitoring an Azure Website.

Refer this MSDN link for more details :

Courtesy : Gyan Jadal

Is it necessary to check out a document in SharePoint ?

Is it necessary to check out a document in SharePoint ?

As you man know, there is a concept of Co-authoring in SharePoint. It allows multiple users to work on the same document simultaneously. The concept of check-in/check-out is a total opposite of co-authoring. In this post, I would like to explain what it is all about and whether you need it at all.

Co-authoring is all about collaboration between multiple users. Check-in/Check-out, on another hand, is a total opposite of co-authoring. Check-in/Check-out is for control freaks like me, who want to control the document they are working on without anyone else messing it up. Essentially, check-out prevents other users from making any changes to the document until you check the document back in.

How to check out a Document?
There are 3 ways for you to check out a document:

  1. Manual check-out
  2. Automatic check-out
  3. Missing required column check-out
  4. Manual Check-out

Manual check-out
To manually check out a document, right-click on the file you want to check out, and choose More > Check-out
check out a document in SharePoint.

Automatic Check-out
Automatic check out means that users will be forced to check out a document from a document library before they can make any edits. To enable automatic check out, go to Library Settings > Versioning Settings and switch Require documents to be checked out before they can be edited? to Yes. Click OK
Next time anyone tries to edit any document in the library – they will be forced to check out a document.

check out a document in SharePoint Message users get when they try to edit (Word) document in the browser.

check out a document in SharePoint Message users get when they try to edit (Word) document using Word desktop application.

Missing Required Column Check-out

This is not really an official name or anything. I call it “a very annoying type of check-out”. It happens when you make your metadata columns required and users upload the file, but exit metadata screen before metadata is filled. SharePoint, in this case, makes the document checked-out. The user then manually needs to fill in required metadata and manually check the file back in. In the meantime, the file will not be visible to anyone else, until the user who is uploading the file fills in the required metadata and checks it in. It is important to note that this type of behavior only occurs in the classic document library. The issue has been addressed with the modern document library. Modern document libraries do not require “required” metadata, so you can upload documents and leave metadata fields blank, and documents will not be checked out by default! Instead, users are able to fill in “required” metadata via a new feature called “attention view”.

check out a document in SharePoint

What Happens when the document is checked out?
Once the document is checked out, there is a little green arrow that appears over the file type icon. If you hover over it with your mouse, it will tell you who the document is checked out to.

What will other users experience?
When you check out a document, users will still be able to access the latest version of the document in SharePoint document library, bit only in Read mode. They will not be able to make any edits or save the document back to the library until the original document is checked back in.

How to check the document back in?
Once you are done with all the changes and are ready to make the document available for others to modify, you can check it back in by choosing Check-in

If you are making changes from within Office Apps, usually it is smart enough to remind you to check in when you exit the application.

Check in on behalf of others
As an Administrator, you can also take over the checked out documents and check them in on other’s behalf. Go to Library Settings, then Manage files which have no checked in version

Then, choose the files you want to take over and choose Take Ownership of Selection

This will allow you to check the file in as if this is your own file (using instructions above).

How to discard check out?
If you wish, you can also discard the check-out altogether. Just choose Discard Check Out from the menu.

Do you need check-in/check out?
Back to the original subject of this post. Do you really need to check out a document before making any changes? Here is my advice:

Try to stay away from the check-out feature unless it is absolutely necessary

For most usual types of document libraries, you do not need to check-out a document or enable automatic check-out. It adds a lot of unnecessary overhead and complexity for end users (i.e. hidden documents). If you have a highly collaborative environment, you do not need to slow the users down by making them check out the file every time they click “Edit”. Moreover, any changes that are made to the document are controlled via version history, so you can always go back and restore a previous version if need be. So to summarize, stay away from check-out, you don’t need.