Removing Folder In A SharePoint Document Library Using JavaScript Object Model (JSOM)

Introduction

In this article, we will learn how to remove a folder in Sharepoint document library, using SharePoint-hosted SharePoint add-ins, using Napa Office 365 development tools. Sharepoint's basic operations are used by JavaScript Object Model here. If there are any changes, post your comments here.

Develop the project, using the method given below in Napa tool

• On your developer site, open Napa Office 365 development tools and then choose Add New Project.
• Choose the app for SharePoint template, name the project, create site and then choose Create button.
• Replace APP.js with the source code given below.
• Publish your app.

Prerequisite

• The important steps are given below, which are to be followed before creating the app.
• Specify the permissions that your app needs, as shown below.
• Choose the Properties button at the bottom of the page.
• In the Properties Window, choose Permissions.
• In the Content category, set the Write permissions for the Tenant scope.
• In the Social category, set the Read permissions for the User Profiles scope.
• Close the Properties Window.

Basic and important things that we want to know are given below.

Sp.ClientContext

• Represents SharePoint Objects and Operations context.
• This is used to access SiteCollection, SubSite, List,Library etc.
• This is used to perform async calls to SharePoint to access the data.
• Load method: Retrieves the properties of a client object from the Server.
• executeQueryAsync method: Executes the current pending request asynchronously on the Server.

Reference the required libraries

Before using JSOM, you must reference the libraries in the order given below.

1. ASP.NET AJAX library
2. sp.runtime.js file
3. sp.js file

Creating, updating and deleting the lists through Client Object Model works similarly to Server Object Model, using .NET Framework (CSOM, SSOM). .

The operations do not complete until and unless, you call the executeQueryAsync(succeededCallback, failedCallback) function.

SharePoint 2013 introduces a Napa tool Service, which is comparable to the existing SharePoint Client Object Model.

Napa tool can be used to perform Create, Read, Update and Delete (CRUD) operations from their apps for SharePoint.

By following this article, you can learn how to create a simple SharePoint-hosted SharePoint add-in by using Napa. The add-in that you’ll create includes the controls and the code to manage the lists and list items.

Choose the kind of add-in; you want to create, name the project and then choose the Create button.

Common steps for all Napa tool deployment

Napa is a tool, which you can use to create SharePoint-hosted SharePoint add-ins.

We can't create a PHA (Provider Hosted APP), using Napa tool.

Click Create button.

Default .aspx display is like the pic, shown above and App.Js file looks, as shown.

You can add more .js file and add the code to it instead of it to the existing file.

Now, publish your app.

Choose the Click here to launch your add-in in a new Window link.

Click Trust it option to deploy your app here, followed by your login popup Window, which will come and ask your credentials.

Enter your credentials and then click OK.

In the App.js, the variables are declared to store the Host Web and App Web.

var hostWebUrl;
var appWebUrl;

Get the Host Web and App Web URL in document.ready.

hostWebUrl= decodeURIComponent(manageQueryStringParameter('SPHostUrl'));
appWebUrl = decodeURIComponent(manageQueryStringParameter('SPAppWebUrl'));

In the code given above, SPHostUrl represents the full URL of the host site and SPAppWebUrl represents the full URL of the app Web.

<script type="text/javascript">
    var hostweburl;

    // Load the required SharePoint libraries.
    $(document).ready(function () {

        // Get the URI decoded URLs.
        hostweburl =decodeURIComponent( getQueryStringParameter("SPHostUrl") );

        // The js files are in a URL in the form:
        // web_url/_layouts/15/resource_file
        var scriptbase = hostweburl + "/_layouts/15/";

        // Load the js files and continue to
             $.getScript(scriptbase + "SP.Runtime.js",
            function () {
                $.getScript(scriptbase + "SP.js", createFolder);
            }
        );
    });

function deleteFolder(resultpanel) {
    var clientContext;
    var oweb;
    var _folderUrl;

    clientContext = new SP.ClientContext.get_current();
    oweb= clientContext.get_web();

    clientContext.load(oweb);
    clientContext.executeQueryAsync(function () {
        _folderUrl = oweb.get_serverRelativeUrl() + "/Lists/TutorialLibrarury/Folder1";
        this.folder = oWebsite.getFolderByServerRelativeUrl(_folderUrl);
        this.folder.deleteObject();

        clientContext.executeQueryAsync(
            Function.createDelegate(this, successHandler),
            Function.createDelegate(this, errorHandler)
        );
    }, errorHandler);
    function success() {
        alert(“New folder Deleted successfully”);
    }

    function error(sender,args) {
    alert( "Request failed: " + arguments[1].get_message();
    }
}

    // Function to retrieve a query string value.
    // For production purposes you may want to use
    // a library to handle the query string.
    function getQueryStringParameter(paramToRetrieve) {
        var params =
            document.URL.split("?")[1].split("&");
        var strParams = "";
        for (var i = 0; i < params.length; i = i + 1) {
            var singleParam = params[i].split("=");
            if (singleParam[0] == paramToRetrieve)
                return singleParam[1];
        }
    }
<script>

Once the code has been executed, go back to SharePoint site and check if the list operations have executed successfully or not.

Thanks for reading the article.