SharePoint Journey

Wednesday, August 31, 2016

SharePoint 2013 working with file: How to upload attachments to SharePoint list item using REST services

You just need to provide item id to which you want to attach file and attachment file name. Rest of the things are similar to how to upload the file.

Following is the complete code to upload the attachments:

<html>
<head>
<script src="/Site%20Assets/js/jquery-1.11.1.min.js"></script>
<script>
function AddAttachments()
{
var digest = "";
$.ajax(
{
url: "/_api/contextinfo",
method: "POST",
headers: {
"ACCEPT": "application/json;odata=verbose",
"content-type": "application/json;odata=verbose"
},
success: function (data) {
digest = data.d.GetContextWebInformation.FormDigestValue;
},
error: function (data) {

}
}).done(function() {
var fileInput = $('#uploadFile');
var fileName = fileInput[0].files[0].name;
var reader = new FileReader();
reader.onload = function (e) {
var fileData = e.target.result;
var res11 = $.ajax(
{
url: "/_api/web/lists/getbytitle('testlist')/items(1)/AttachmentFiles/ add(FileName='" + fileName + "')",
method: "POST",
binaryStringRequestBody: true,
data: fileData,
processData: false,
headers: {
"ACCEPT": "application/json;odata=verbose",
"X-RequestDigest": digest,
"content-length": fileData.byteLength
},
success: function (data) {

},
error: function (data) {
alert("Error occured." + data.responseText);
}
});
};
reader.readAsArrayBuffer(fileInput[0].files[0]);

});
}
</script>
</head>
<body>
<div>
<input id="uploadFile" type="file">
</div>

<div>
<input type="submit" onclick="AddAttachments()" value="Add Attachments"> </input>
</div>
</body>
</html>

Loop through user profiles using console app

Use the following code to loop through all user profiles using a c# console app:

var siteUrl = "http://yoursite";

SPSecurity.RunWithElevatedPrivileges(delegate()
{
  using (SPSite site = new SPSite(siteUrl))
  {
    try{
      SPServiceContext serviceContext = SPServiceContext.GetContext(site);
      UserProfileManager upMananger = new UserProfileManager(serviceContext);

      foreach (UserProfile profile in upMananger)
      {
        //Add your logic here..
        Console.WriteLine("Found: " + profile["AccountName"]);
      }
    }
    //Catch exceptions here, ex. NullReferenceException
    catch (System.Exception ex){
      //Handle exceptions
    }
  }
});

Some useful tips to avoid errors:
- Run the console application as Administrator
- Grant your account full control to User Profile Service Application (Fix NullReferenceException)

SharePoint JS: Upload a file using javascript, jQuery, HTML5

To upload a file using jquery, i used this code:

//Function attached to the html fileupload tag (<input type="file">)
function uploadFile(){
    if (document.getElementById("inputFile").files.length === 0) {
        alert('No file was selected');
        return;
    }
    var parts = document.getElementById("inputFile").value.split("\\");
    var filename = parts[parts.length - 1];
    var file = document.getElementById("inputFile").files[0];
    uploadFileSync("http://ngo.com", "libraryname", filename, file);
}

//Upload file synchronously
function uploadFileSync(spWebUrl , library, filename, file) 
{
    var reader = new FileReader();
    reader.onloadend = function(evt) 
    {
      if (evt.target.readyState == FileReader.DONE) 
      {
         var buffer = evt.target.result;
         var completeUrl = spWebUrl
           + "/_api/web/lists/getByTitle('"+ library + "')"
           + "/RootFolder/Files/add(url='"+ filename +"',overwrite='true')?"
           + "@TargetLibrary='"+library+"'&@TargetFileName='"+ filename +"'";

          $.ajax({
                url: completeUrl,
                type: "POST",
                data: buffer,
                async: false,
                processData: false,
                headers: {
                    "accept": "application/json;odata=verbose",
                    "X-RequestDigest": $("#__REQUESTDIGEST").val(),
                    "content-length": buffer.byteLength
                },
                complete: function (data) {
                    alert('succes');
                },
                error: function (err) {
                     alert('failed');
                }
        });
      }
    };
    reader.readAsArrayBuffer(file);
}

Resources

jQuery
HTML5 - FileReader
Note- If Validation Setting on Library This Code is Not Working
Request failed. List data validation failed.undefined
Error Message:

Request failed. List data validation failed.undefined

Problem Description:

I wrote JavaScript function to add item into SharePoint List but I getting below error shown in following figure.

I got above error because I kept column validation in my one of the Date Column,

I remove column level validation from my List, I wrote validation in JavaScript function only.

That’s all and finally my Item created using JavaScript…

Saturday, August 20, 2016

Using Content Deployment to Copy One Site Collection to Another in SharePoint 2010

In simple terms, Content Deployment in SharePoint 2010 is used to deploy the content from one site to another site. We can set the content deployment jobs (incoming and outgoing) using SharePoint Central Administration 2010.

The two-farm topology is a standard Internet site topology and is typical of topologies that are used to publish an Internet site. It is usually composed of two server farms: one to host the authoring site collection and the other to host the production site collection.

It is important to be aware that content deployment is a one-way process. The content deployment feature does not support round-trip synchronization from source to destination and vice versa. Creating new content or changing existing content on the destination site collection can cause content deployment jobs to fail. Because of this, it is usually recommended to restrict permissions on the destination site collection so that only specific users can make direct changes to content that is stored within that site collection.

We will now go through a typical process that will copy one site collection to another with content deployment.

PROCESS OVERVIEW

Content Deployment in SharePoint 2010 is composed of the following three processes.

Create two Web Applications in separate content databases and create site collections in the web applications.
Configure Content deployment, paths and jobs -> Run jobs.
Check the deployment status and the destination site collection’s content.

I. CREATING THE WEB APPLICATIONS AND SITE COLLECTIONS

1. First, create two web apps and ensure the two are in separate content databases.

http://spy2010
http://spy2010:1111

2. Second, create site collection http://spy2010/sites/authoring and select the “Team Site” template.

3. The initial content deployment destination must be a blank site collection.

4. Create a site collection and ensure that you select “<Select template later>.”

Note: DO NOT create a site collection using “Blank Site” template, as this does not count as an empty site collection and content deployment will fail.

5. The site collection in port 1111 is just http://spy2010:1111/sites/production.

II. Configure Content deployment, paths and jobs in CA

1. Navigate to Central Administration -> General Application Settings -> Content Deployment -> Configure Content Deployment.

2. Configure new deployment path

Note: A content deployment path is required to define a one-to-one relationship between a source and destination site collection for the purposes of content deployment. Once you have created a path, jobs can be scheduled and run on an ad-hoc basis to deploy additional content as required.

3. Select your “authoring” site collection as the source and “production” site collection as the destination.

4. Enter the current central administration address, including the port number.

Note: We will need to test the connection to make sure the destination site collection list populated correctly.

Create a deployment job and run it

5. We will need to create a deployment job. Jobs and deployment paths have a one-to-one relationship, so we will need to create at least one job for each path that we have specified.

6. Select the “One time only” radio button to kick the job off immediately.

7. Create a schedule or run the job now using the “One time only” option to test your new deployment path.

8. You can view current job status on the “Manage Content Deployment Paths and Jobs” page.

9. Once the job status becomes “Completed,” the “Production” site collection’s content has been copied successfully.

III. Check deployment status and destination site collection’s content

1. Navigate to Central Administration -> General Application Settings ->Content Deployment -> Check deployment of specific content.

2. We can check the “production” status on the following page.

3. When we login to “production,” we can see that the content is now same as the content in “authoring.”

Cross site publishing and anonymous access in Share Point 2013

With cross site publishing feature in SharePoint 2013 you may make your content stored in some list or document library in one site collection, available via search index in other site collection (it is the most frequent use case mentioned in the documentation, although cross site publishing works also within single site collection and across different web applications in the same farm). What if you develop public site and you need to enable the content from e.g. authoring site, which is accessible only for content editors, also for anonymous users?

When you enable document library as catalog (Doc lib settings > Catalog settings) there is possibility to specify whether or not anonymous access should be enabled:

When you leave it off like shown on the picture above, list.AnonymousPermMask64 property will contain default flag SPBasePermissions.AnonymousSearchAccessWebLists, which according to documentation means the following:

Content of lists and document libraries in the Web site will be retrieveable for anonymous users through SharePoint search if the list or document library has AnonymousSearchAccessList set.

I.e. if list or doclib contains only this flag, it doesn’t have anonymous access enabled. When you will enable anonymous access from UI:

AnonymousPermMask64 property will contain the following mask: AnonymousSearchAccessList | AnonymousSearchAccessWebLists. AnonymousSearchAccessList flag means the following:

Make content of a list or document library retrieveable for anonymous users through SharePoint search. The list permissions in the site do not change.

I.e. when it is set, content will be available for anonymous users (as our experience shows it will be available even if AnonymousSearchAccessWebLists flag is not explicitly set for the list).

Setting anonymous access for the list when it is published as catalog is done in PublishingCatalogUtility.EnableAnonymousAccess() method:

   1:  internal static bool EnableAnonymousAccess(SPWeb parentWeb, SPList list)

   2:  {

   3:      CommonUtilities.ConfirmNotNull(parentWeb, "parentWeb");

   4:      CommonUtilities.ConfirmNotNull(list, "list");

   5:      if (GetIsAnonAccessEnabled(list))

   6:      {

   7:          return false;

   8:      }

   9:      SPWeb firstUniqueAncestorWeb = parentWeb.FirstUniqueAncestorWeb;

  10:      firstUniqueAncestorWeb.AnonymousPermMask64 |=

  11:  SPBasePermissions.AnonymousSearchAccessWebLists;

  12:      list.BreakRoleInheritance(true);

  13:      list.AnonymousPermMask64 |= SPBasePermissions.EmptyMask |

  14:  SPBasePermissions.AnonymousSearchAccessList;

  15:      return true;

  16:  }

And the last note: if you connect to catalog programmatically using CatalogConnectionManager class (see example here), it will also set anonymous access, i.e. list will have AnonymousPermMask64 = AnonymousSearchAccessList even though there is no explicit option for that in the example above.

Tuesday, August 16, 2016

SharePoint Hosted App Using REST API From Client Side Script

Here are the steps:

Step 1: SHA Project folder structure.

Step 2: App Web List Creation Steps.

Firstly add simple list into SHA project. Here are the steps to create List into SHA project.

In this example I created custom list named “Customers” as in the following,

Elements.xml File code- it adds data into List.

<?xml version="1.0" encoding="utf-8"?>    
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">    
  <ListInstance Title="Customers" OnQuickLaunch="TRUE" TemplateType="105" FeatureId="00bfea71-7e6d-4186-9ba8-c047ac750105" Url="Lists/Customers" Description="My List Instance">    
    <Data>    
      <Rows>    
        <Row>    
          <Field Name="FirstName">Rupali</Field>    
          <Field Name="Title">Shinde</Field>    
          <Field Name="WorkPhone">(123)456-6789</Field>    
        </Row>    
        <Row>    
          <Field Name="FirstName">Vishnu</Field>    
          <Field Name="Title">Jadhav</Field>    
          <Field Name="WorkPhone">(143)867-5309</Field>    
        </Row>    
        <Row>    
          <Field Name="FirstName">DJ</Field>    
          <Field Name="Title">Jadhav</Field>    
          <Field Name="WorkPhone">(800)LUV-AZUR</Field>    
        </Row>    
        <Row>    
          <Field Name="FirstName">Summit</Field>    
          <Field Name="Title">Jadhav</Field>    
          <Field Name="WorkPhone">(888)123-5677</Field>    
        </Row>    
        <Row>    
          <Field Name="FirstName">Kiran</Field>    
          <Field Name="Title">Jadhav</Field>    
          <Field Name="WorkPhone">(888)GOT-OAUTH</Field>    
        </Row>    
        <Row>    
          <Field Name="FirstName">Shrikant</Field>    
          <Field Name="Title">Shinde</Field>    
          <Field Name="WorkPhone">(813)813-8133</Field>    
        </Row>    
        <Row>    
          <Field Name="FirstName">Seema</Field>    
          <Field Name="Title">Jadhav</Field>    
          <Field Name="WorkPhone">(800)BIG-TULS</Field>    
        </Row>    
      </Rows>    
    </Data>    
  </ListInstance>    
</Elements>    

Step 3: User Interface designing steps.

Home page of application is having “Add New Customer “ button, which shows user entry form to fill user details.

User Details Grid – this grid will show user details with Edit, Delete and Display button into it.

<%@ Page Language="C#" MasterPageFile="~masterurl/default.master" Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
    
<%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
<%@ Register TagPrefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
    
<asp:Content ID="Content1" ContentPlaceHolderID="PlaceHolderPageTitle" runat="server">    
    SharePoint-hosted App REST API Demo     
</asp:Content>    
    
<asp:Content ID="Content2" ContentPlaceHolderID="PlaceHolderPageTitleInTitleArea" runat="server">    
    Using the REST API from Client-side JavaScript    
</asp:Content>    
    
<asp:Content ContentPlaceHolderID="PlaceHolderAdditionalPageHead" runat="server">    
    
    <link rel="Stylesheet" type="text/css" href="../Content/App.css" />       
    
    <script type="text/javascript" src="../Scripts/jquery-1.6.2.min.js"></script>    
    <script type="text/javascript" src="../Scripts/jsrender.js"></script>    
    
    <script type="text/javascript" src="../Scripts/App.js"></script>    
    
</asp:Content>    
    
<asp:Content ContentPlaceHolderID="PlaceHolderMain" runat="server">    
    
    <div id="toolbar">    
        <input type="button" id="cmdAddNewCustomer" value="Add New Customer" class="ms-ButtonHeightWidth" />    
    </div>    
    
    <div id="results" />    
    
</asp:Content>    

Output

Step 4: Grid Data filling steps – the following code is used to fill GridView.

var hostweburl;    
var appweburl;    
    
$(function () {    
    
    // register event handlers on page    
    $("#cmdAddNewCustomer").click(onAddCustomer);    
    $("#results").append($("<img>", { src: "_layouts/images/gears_anv4.gif" }));    
    
    // Get the URI decoded URLs.     
    hostweburl = decodeURIComponent(getQueryStringParameter("SPHostUrl"));    
    appweburl = decodeURIComponent(getQueryStringParameter("SPAppWebUrl"));    
    
    var scriptbase = hostweburl + "/_layouts/15/";    
    $.getScript(scriptbase + "SP.RequestExecutor.js", getCustomers);    
});    
    
function getCustomers() {    
     
    $("#results").empty();    
    $("<img>", { "src": "/_layouts/images/GEARS_AN.GIF" }).appendTo("#results");    
        
    var executor = new SP.RequestExecutor(appweburl);    
    var FullURL = appweburl + "/_api/web/lists/getbytitle('Customers')/items";         
       
    executor.executeAsync(    
       {    
           url: FullURL,    
           method: "GET",    
    
           headers: {    
               "accept": "application/json;odata=verbose",    
               "content-type": "application/json;odata=verbose",    
               "X-RequestDigest": $("#__REQUESTDIGEST").val()    
           },    
           success: onDataReturned,    
           error: errorHandler    
       }    
   );    
}    
    
function errorHandler(data, errorCode, errorMessage) {    
    document.getElementById("results").innerText = "Could not complete cross-domain call: " + errorMessage;    
}    
    
function onDataReturned(data) {    
    
    $("#results").empty();    
    
    var jsonObject = JSON.parse(data.body);    
    var odataResults = jsonObject.d.results;    
    
    // set rendering template    
    var tableHeader = "<thead>" +    
                      "<td>Last Name</td>" +    
                      "<td>First Name</td>" +    
                      "<td>Work Phone</td>" +    
                      "<td> </td>" +    
                      "<td> </td>" +    
                      "<td> </td>" +    
                    "</thead>";    
    
    var table = $("<table>", { id: "customersTable" }).append($(tableHeader));    
    
    var renderingTemplate = "<tr>" +    
                              "<td>{{>Title}}</td>" +    
                              "<td>{{>FirstName}}</td>" +    
                              "<td>{{>WorkPhone}}</td>" +    
                              "<td><a href='javascript: onShowCustomerDetail({{>Id}});'><img src='_layouts/images/DETAIL.gif' alt='Show Detail' /></a></td>" +    
                              "<td><a href='javascript: onUpdateCustomer({{>Id}});'><img src='_layouts/images/EDITITEM.gif' alt='Edit' /></a></td>" +    
                              "<td><a href='javascript: onDeleteCustomer({{>Id}});'><img src='_layouts/images/DELITEM.gif' alt='Delete' /></a></td>" +    
                            "</tr>";    
    
    
    $.templates({ "tmplTable": renderingTemplate });    
    table.append($.render.tmplTable(odataResults));    
    
    $("#results").append(table);    
}   

Step 5: Add new customer

EditCustomer.aspx file contains code for New Customer Popup.

<%@ Page Language="C#" MasterPageFile="~masterurl/default.master" Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
    
<%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
<%@ Register TagPrefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>    
    
<asp:Content ContentPlaceHolderID="PlaceHolderAdditionalPageHead" runat="server">    
    <link rel="Stylesheet" type="text/css" href="../Content/App.css" />    
    <SharePoint:ScriptLink name="SP.UI.Dialog.js" runat="server" Defer="false" LoadAfterUI="true" Localizable="false" />    
    <SharePoint:ScriptLink name="sp.js" runat="server" Defer="false" LoadAfterUI="true" Localizable="false" />    
    
    <script type="text/javascript" src="../Scripts/jquery-1.6.2.js"></script>    
    <script type="text/javascript" src="../Scripts/EditCustomer.js"></script>    
</asp:Content>    
    
<asp:Content ContentPlaceHolderID="PlaceHolderMain" runat="server">    
    
    <div class="dialog_input_section">    
    
        <table id="customerEditTable">    
            <tr>    
                <td>First Name:</td>    
                <td>    
                    <input id="txtFirstName" /></td>    
            </tr>    
            <tr>    
                <td>Last Name:</td>    
                <td>    
                    <input id="txtLastName" /></td>    
            </tr>    
            <tr>    
                <td>Work Phone:</td>    
                <td>    
                    <input id="txtWorkPhone" /></td>    
            </tr>    
        </table>    
    
    </div>    
    
    <div class="dialog_button_section">    
        <input type="button" id="cmdOK" value="Save" class="ms-ButtonHeightWidth" />    
        <input type="button" id="cmdCancel" value="Cancel" class="ms-ButtonHeightWidth" />    
    </div>    
    
</asp:Content>     

App.JS file contains the following code to open popup.

$("#cmdAddNewCustomer").click(onAddCustomer);  

Above click internally calls EditCustomer.aspx file and render it on screen.

Step 6: Update Customer

Inside GridView, edit button is provided to update existing customer details.

Code:

function onUpdateCustomer(customer) {        
       
    var executor = new SP.RequestExecutor(appweburl);    
    var FullURL = appweburl + "/_api/web/lists/getbytitle('Customers')/items(" + customer + ")";    
    
    executor.executeAsync(    
       {    
           url: FullURL,    
           method: "GET",    
    
           headers: {    
               "accept": "application/json;odata=verbose",    
               "content-type": "application/json;odata=verbose",    
               "X-RequestDigest": $("#__REQUESTDIGEST").val()    
           },    
           success: onCustomerReturned,    
           error: errorHandler    
       }    
   );    
}   

Output

Step 7: Delete Customer

Inside GridView, delete button is provided to delete existing customer details.

Code

function onDeleteCustomer(customer) {    
    
    var requestUri = _spPageContextInfo.webAbsoluteUrl + "/_api/Web/Lists/getByTitle('Customers')/items(" + customer + ")";    
    
    var requestHeaders = {    
        "accept": "application/json",    
        "X-RequestDigest": $("#__REQUESTDIGEST").val(),    
        "If-Match": "*"    
    }    
    
    $.ajax({    
        url: requestUri,    
        type: "DELETE",    
        contentType: "application/json",    
        headers: requestHeaders,    
        success: onSuccess,    
        error: onError    
    });    
}  

Step 8: View Customer Details.

Inside GridView, view button is provided to view existing customer details.

function onShowCustomerDetail(customer) {    
    
    var customerItemEditUrl = _spPageContextInfo.webAbsoluteUrl +    
                            "/Lists/Customers/DispForm.aspx?ID=" + customer;    
    
    var dialogOptions = {    
        url: customerItemEditUrl,    
        title: "Customer Detail",    
        dialogReturnValueCallback: getCustomers    
    };    
    
    SP.UI.ModalDialog.showModalDialog(dialogOptions);    
}     

Output

When view form is open in browser and if you change user details there itself it gets updated and final result get rendered on screen.

Full Source Code

var hostweburl;    
var appweburl;    
    
$(function () {    
    
    // register event handlers on page    
    $("#cmdAddNewCustomer").click(onAddCustomer);    
    $("#results").append($("<img>", { src: "_layouts/images/gears_anv4.gif" }));    
    
    // Get the URI decoded URLs.     
    hostweburl = decodeURIComponent(getQueryStringParameter("SPHostUrl"));    
    appweburl = decodeURIComponent(getQueryStringParameter("SPAppWebUrl"));    
    
    var scriptbase = hostweburl + "/_layouts/15/";    
    $.getScript(scriptbase + "SP.RequestExecutor.js", getCustomers);    
});    
    
function getCustomers() {    
     
    $("#results").empty();    
    $("<img>", { "src": "/_layouts/images/GEARS_AN.GIF" }).appendTo("#results");    
        
    var executor = new SP.RequestExecutor(appweburl);    
    var FullURL = appweburl + "/_api/web/lists/getbytitle('Customers')/items";         
       
    executor.executeAsync(    
       {    
           url: FullURL,    
           method: "GET",    
    
           headers: {    
               "accept": "application/json;odata=verbose",    
               "content-type": "application/json;odata=verbose",    
               "X-RequestDigest": $("#__REQUESTDIGEST").val()    
           },    
           success: onDataReturned,    
           error: errorHandler    
       }    
   );    
}    
    
function errorHandler(data, errorCode, errorMessage) {    
    document.getElementById("results").innerText = "Could not complete cross-domain call: " + errorMessage;    
}    
    
function onDataReturned(data) {    
    
    $("#results").empty();    
    
    var jsonObject = JSON.parse(data.body);    
    var odataResults = jsonObject.d.results;    
    
    // set rendering template    
    var tableHeader = "<thead>" +    
                      "<td>Last Name</td>" +    
                      "<td>First Name</td>" +    
                      "<td>Work Phone</td>" +    
                      "<td> </td>" +    
                      "<td> </td>" +    
                      "<td> </td>" +    
                    "</thead>";    
    
    var table = $("<table>", { id: "customersTable" }).append($(tableHeader));    
    
    var renderingTemplate = "<tr>" +    
                              "<td>{{>Title}}</td>" +    
                              "<td>{{>FirstName}}</td>" +    
                              "<td>{{>WorkPhone}}</td>" +    
                              "<td><a href='javascript: onShowCustomerDetail({{>Id}});'><img src='_layouts/images/DETAIL.gif' alt='Show Detail' /></a></td>" +    
                              "<td><a href='javascript: onUpdateCustomer({{>Id}});'><img src='_layouts/images/EDITITEM.gif' alt='Edit' /></a></td>" +    
                              "<td><a href='javascript: onDeleteCustomer({{>Id}});'><img src='_layouts/images/DELITEM.gif' alt='Delete' /></a></td>" +    
                            "</tr>";    
    
    
    $.templates({ "tmplTable": renderingTemplate });    
    table.append($.render.tmplTable(odataResults));    
    
    $("#results").append(table);    
}    
    
function onShowCustomerDetail(customer) {    
    
    var customerItemEditUrl = _spPageContextInfo.webAbsoluteUrl +    
                            "/Lists/Customers/DispForm.aspx?ID=" + customer;    
    
    var dialogOptions = {    
        url: customerItemEditUrl,    
        title: "Customer Detail",    
        dialogReturnValueCallback: getCustomers    
    };    
    
    SP.UI.ModalDialog.showModalDialog(dialogOptions);    
}    
    
function onAddCustomer(event) {    
    
    var dialogArgs = {    
        command: "Add"    
    };    
    
    var dialogOptions = {    
        url: "EditCustomer.aspx",    
        title: "Add New Customer",    
        width: "480px",    
        args: dialogArgs,    
        dialogReturnValueCallback: saveNewCustomer    
    };    
    
    SP.UI.ModalDialog.showModalDialog(dialogOptions);    
}    
    
function saveNewCustomer(dialogResult, returnValue) {    
       
    if (dialogResult == SP.UI.DialogResult.OK) {    
    
        // get data from dialog for new customer    
        var LastName = returnValue.LastName;    
        var FirstName = returnValue.FirstName;    
        var WorkPhone = returnValue.WorkPhone;    
    
        var requestUri = _spPageContextInfo.webAbsoluteUrl +    
                  "/_api/Web/Lists/getByTitle('Customers')/items/";    
    
        var requestHeaders = {    
            "accept": "application/json",    
            "X-RequestDigest": $("#__REQUESTDIGEST").val(),    
        }    
    
        var customerData = {                
            Title: LastName,    
            FirstName: FirstName,    
            WorkPhone: WorkPhone    
        };    
    
        requestBody = JSON.stringify(customerData);    
    
        $.ajax({    
            url: requestUri,    
            type: "Post",    
            contentType: "application/json",    
            headers: requestHeaders,    
            data: requestBody,    
            success: onSuccess,    
            error: onError    
        });    
    }    
}    
    
function onDeleteCustomer(customer) {    
    
    var requestUri = _spPageContextInfo.webAbsoluteUrl + "/_api/Web/Lists/getByTitle('Customers')/items(" + customer + ")";    
    
    var requestHeaders = {    
        "accept": "application/json",    
        "X-RequestDigest": $("#__REQUESTDIGEST").val(),    
        "If-Match": "*"    
    }    
    
    $.ajax({    
        url: requestUri,    
        type: "DELETE",    
        contentType: "application/json",    
        headers: requestHeaders,    
        success: onSuccess,    
        error: onError    
    });    
}    
    
function onUpdateCustomer(customer) {        
       
    var executor = new SP.RequestExecutor(appweburl);    
    var FullURL = appweburl + "/_api/web/lists/getbytitle('Customers')/items(" + customer + ")";    
    
    executor.executeAsync(    
       {    
           url: FullURL,    
           method: "GET",    
    
           headers: {    
               "accept": "application/json;odata=verbose",    
               "content-type": "application/json;odata=verbose",    
               "X-RequestDigest": $("#__REQUESTDIGEST").val()    
           },    
           success: onCustomerReturned,    
           error: errorHandler    
       }    
   );    
}    
    
function onCustomerReturned(data) {    
    
    var jsonObject = JSON.parse(data.body);     
       
    var dialogArgs = {    
    
        command:    "Update",    
        Id:         jsonObject.d.Id,    
        LastName:   jsonObject.d.Title,    
        FirstName:  jsonObject.d.FirstName,    
        WorkPhone:  jsonObject.d.WorkPhone,    
        etag:       jsonObject.d.__metadata.etag    
    };    
    
    var dialogOptions = {    
        url: "EditCustomer.aspx",    
        title: "Update Customer",    
        width: "480px",    
        args: dialogArgs,    
        dialogReturnValueCallback: updateCustomer    
    };    
    
    SP.UI.ModalDialog.showModalDialog(dialogOptions);    
}    
    
function updateCustomer(dialogResult, returnValue) {    
    
    if (dialogResult == SP.UI.DialogResult.OK) {    
    
        var Id = returnValue.Id;    
        var FirstName = returnValue.FirstName;    
        var LastName = returnValue.LastName;    
        var WorkPhone = returnValue.WorkPhone;    
        var etag = returnValue.etag;    
                  
        var requestUri = appweburl + "/_api/web/lists/getbytitle('Customers')/items(" + Id + ")";    
    
        var requestHeaders = {    
            "accept": "application/json",    
            "X-RequestDigest": $("#__REQUESTDIGEST").val(),    
            "X-HTTP-Method": "MERGE",    
            "If-Match": etag    
        }    
    
        var customerData = {               
            Title: LastName,    
            FirstName: FirstName,    
            WorkPhone: WorkPhone    
        };    
    
        requestBody = JSON.stringify(customerData);    
            
        $.ajax({    
            url: requestUri,    
            type: "POST",    
            contentType: "application/json",    
            headers: requestHeaders,    
            data: requestBody,    
            success: onSuccess,    
            error: onError    
        });    
    }    
}    
    
function onSuccess(data, request) {    
    getCustomers();    
}    
    
function onError(error) {    
    $("#results").empty();    
    $("#results").text("ADD ERROR: " + JSON.stringify(error));    
}    
    
function getQueryStringParameter(paramToRetrieve) {    
    
    var strParams = "";    
    var params = document.URL.split("?")[1].split("&");    
    
    for (var i = 0; i < params.length; i = i + 1) {    
        var singleParam = params[i].split("=");    
    
        if (singleParam[0] == paramToRetrieve)    
            return singleParam[1];    
    }    
}   

App.css

.ms-siteicon-a {    
  background-image: url(images/SiteIcon.gif);    
  background-repeat: no-repeat;    
  width: 75px;    
  height: 75px;    
}    
    
.ms-siteicon-img {    
  display: none;    
}    
    
.ms-core-siteTitle span a {    
  font-size: 18px;    
}    
   
#customersTable {    
  background-color: #999;    
  border-collapse: collapse;    
}    
   
#customersTable thead td {    
  background-color: #333;    
  color: White;    
}    
   
#customersTable td {    
  color: #222;    
  border: 1px black solid;    
  padding: 4px;    
  background-color: White;    
  border-collapse: collapse;    
}    
   
#resultsTable tr td {    
  color: #333;    
  padding: 4px;    
  border-collapse: collapse;    
  border: 1px solid black;    
  background-color: White;    
    font-size: 32px;    
}    
   
   
#toolbar {    
    margin: 4px;    
    padding: 8px;    
    background-color: #ccc;    
}    
   
   
#results {    
    padding: 8px;    
    font-size: 12px;    
}    
   
#results table {    
  margin: 8px    
}    
   
#results table, #results table td {    
    border-collapse: collapse;    
    border: 1px #444 solid;    
    padding: 2px 8px 2px 4px;    
    font-size: 20px;    
}    
   
#results h2 {    
    font-size: 18px;    
    color: #999;    
    border-bottom: 1px solid #999;    
    margin-top: 8px;    
    margin-bottom: 4px;    
}    
    
.ms-dialog #s4-ribbonrow {    
  display: none;    
}    
    
.ms-dlgTitle {    
  background-image: url("images/logo16.gif");    
  background-repeat: no-repeat;    
  background-position: 8px, 4px;    
  background-color: black;    
  padding: 1px;    
}    
    
h1.ms-dlgTitleText {    
  margin-left: 28px;    
  margin-top: 4px;    
}    
    
.ms-dlgTitle h1 {    
    font-size: 1.4em;    
  color:  white;    
}    
   
#dlgTitleBtns {    
  margin-top: 4px;    
  margin-right: 8px;    
}    
    
.ms-dlgTitle {    
    padding-bottom: 4px;    
    padding-left: 8px;    
}    
    
.ms-dlgTitle h1 {    
    font-size: 1.8em;    
}    
    
    
.dialog_input_section {    
    padding-top: 4px;    
}    
    
.dialog_input_section_title {    
    margin-top: 8px;    
    color: black;    
    border-bottom: solid black 1px;    
    margin-bottom: 8px;    
}    
    
.dialog_button_section {    
    margin-top: 16px;    
    border-top: solid #CCC 2px;    
    padding-top: 8px;    
    text-align: right;    
}    
    
.ms-dlgContent {    
    padding-bottom: 2px;    
}    
    
    
.ms-dlgFrameContainer {    
    padding-top: 4px;    
    padding-left: 8px;    
    padding-right: 8px;    
    padding-bottom: 0px;    
}   