Working With SharePoint Document Library Using Napa Office 365 Development Tools

Introduction

In this article, we will learn how to create a folder in the Sharepoint document library using SharePoint-hosted SharePoint Add-in with 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 select the "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.
  
  
• 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.

Important things we need to know 

Sp.ClientContext

• Represents the SharePoint Objects and Operations context.
• This is used to access SiteCollection, SubSite, List,Library etc.
• This is used to perform async calls to the SharePoint to accessing 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 the JSOM, you must reference the following libraries, in exact order.

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 similar to the 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 Tools can be used to perform Create, Read, Update and Delete (CRUD) operations from their apps for SharePoint.

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 press 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 Tools.

Click "Create" button.

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

You can add more .js files 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. This action will be followed by a login popup window which will come and ask for your credentials.

Enter your credentials and then click "OK".

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

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 above code, 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 createFolder() {
    var clientContext;
    var _Web;
    var _List;
    var _itemCreateInfo;

    clientContext = new SP.ClientContext.get_current();
    _Web= clientContext.get_web();
    _List= oWebsite.get_lists().getByTitle("Tutotrialdocuments");

    _itemCreateInfo= new SP.ListItemCreationInformation();
    _itemCreateInfo.set_underlyingObjectType(SP.FileSystemObjectType.folder);
    _itemCreateInfo.set_leafName("Customfolder");
    this._ListItem = oList.addItem(itemCreateInfo);
    this._ListItem.set_item("Title", "Customfolder!");
    this._ListItem.update();

    clientContext.load(this._ListItem);
    clientContext.executeQueryAsync(
        Function.createDelegate(this, success),
        Function.createDelegate(this, error)
    );

    function success() {
        alert(“New folder Created 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 is executed, go back to SharePoint site and check if the list operations executed successfully or not.

That's it. Thanks for reading the article.