Debug office Add-ins

You could get logs of internal errors on the Office Addin using following method. Its simple and easy and involved few steps achieve.

Open Windows registry editor (windows + R then regedit.exe) and follow the route “HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Wef\Developer\” and mention your location to write logs.

2017-07-24_12-00-23

Notes 

  • Runtime logging feature available in Office desktop 2016 version.
  • You must be admin of the considered system to perform this.

Important!

Initially, this is kept blank and keep in mind to reverse it back since it leads to performance issues.

Advertisements

View Picker Tree view of SharePoint Online and On Prem

If you locking for short cut to integrate SharePoint site hierarchy. The following hack would be a better option if you not willing to custom build control.

✍ How achive?

/_layouts/15/PickerTreeView.aspx

SharePoint site hierarchy

REST and OData with Office365 APIs

When communicate with Office or SharePoint APIs, its important fact that knowledge on representational transfer protocol and OData protocols while moving with deep customization’s.

what is REST (Representational State Transfer)?

In simple terms REST is all about below;

  • Predefined set of stateless operation which identified by URL
  • Responses may contain HTML, JSON, XML or any other defined format which supported
  • GET, POST, PUT, DELETE are most common forms of HTTP verbs

rest_api

Eg.

GET:
http:///_api/web/lists/GetByTitle('Test')
GET:
https://outlook.office.com/api/v2.0/me/MailFolders/sentitems/messages/

what is OData (Open Data Protocol)?

  • Equipped with query and creational capabilities on REST APIs
  • Initiated by Microsoft in year 2007
  • Format [http or https]://<REST Endpoint URL>/<query>
http://<end point URI>?$select=value&$filter=condition$orderby=value

Open Standardization?
Standards which are developed with the involvement of community (mostly with developers). Open standards inherited to office 365 API development in following manners;
• Most of Office 365 APIs are exposed as a RESTful APIs
• Its implemented with OData 4.0 (as for year 2016)

OData queries?
OData queries is common standard which elaborated above also included in the SharePoint and Office365 end point data querying. Its ultra simple if you know the basics and played with this. Follow the following links and be expert on this.

www.odata.org : Official site for OData

graph.microsoft.io : Explore Microsoft Office365 API with queries

OData validator to validate your REST endpoints

Note : If you noticed there are versions associated with most of cloud based endpoints. Cloud services are continuously pushing changes to its services as sooner changes are ready, so then returned patterns may changed for same query. To avoid custom applications get break due to changed on endpoint, it classifies under version metadata. Simply you can pick any version which satisfies your requirement.

Querying SharePoint Endpoints as below;

SharePoint REST service query option syntax
Courtesy : msdn.microsoft.com

 

Further references 

Clear | Remove | Delete Managed metadata (Taxanomy) column value in SharePoint List/ library

You may find many references to write into taxonomy columns (aka. managed metadata columns) but the clearing those is pretty much tricky.

Following code sample guide you through how you can clear the taxonomy column value in you custom client side application (JSOM) based on SharePoint.

//USAGE:
//clearWithValue =true => for clear saved taxanomy column values
//clearWithValue =false => wite into taxanomy column 

function saveValuesToManagedMetadataColumns(listName, fieldId, taxanomyLabel, siteUrl, clearWithValue) {

    //You many need seperate function to resolve GUID for the lable.
//Its based on your requirement and for now its hardcoded
    var taxonmyGuid = "9f75f519-51f8-4723-9182-7e8225a54031";
//Loading context and list
    var context = new SP.ClientContext(siteUrl);
    var list = context.get_web().get_lists().getByTitle(listName);
    //Getting item to update
    var camlQuery = new SP.CamlQuery();
    camlQuery.set_viewXml("<View>" +
        "<Query>" +
        "<Where><Eq>" +
        "<FieldRef Name=\'ID\'/>" +
        "<Value Type=\'Number\'>" + fieldId + "</Value>" +
        "</Eq></Where>" +
        "</Query>" +
        "</View>");
    var items = list.getItems(camlQuery);
//Load selected items to context
    context.load(items);
    //Loading MMS field
    var field = list.get_fields().getByInternalNameOrTitle("taxanomyColumnName");
    var txField = context.castTo(field, SP.Taxonomy.TaxonomyField);
//Load field to context
    context.load(txField);

    context.executeQueryAsync(function () {
        //getting term set ID
        var functionTermSetId = txField.get_termSetId().toString();
        //Term value build for update..this is not useful is your purpose only for clearing
//But for illustration..got below also to show off
        var termValue = new SP.Taxonomy.TaxonomyFieldValue();
        termValue.set_label(taxanomyLabel);
        termValue.set_termGuid(taxonmyGuid);
        termValue.set_wssId(-1);
//Iterate through collection and update
        var e = items.getEnumerator();
        while (e.moveNext()) {
            var item = e.get_current();

            //Save to taxanomy column
            if (clearWithValue == false)
                txField.setFieldValueByValue(item, termValue);

            //Clering taxanomy column
            if (clearWithValue == true)
                txField.validateSetValue(item, null);

            //Set noraml fields..If you have them too
            item.set_item('Title', metadataCollection.Title);

            item.update();
        }
        context.executeQueryAsync(function (sender, args) {
            console.log('Successfully updated item with ', args, serviceId, false);
        }, function (args) {
            console.log('Error on updating item with taxanomy value', args, serviceId, false);
        });

    }, function (args) {
        console.log('Internal server Error on updating item with taxanomy metadata', args, serviceId, false);
    });

}

References
http://sharepoint.stackexchange.com/questions/47719/how-can-i-set-empty-value-to-taxonomyfield-of-microsoft-sharepoint-client-taxono

Integrate SharePoint Documents with Office Web Apps in Custom Solutions

If you are finding way of integrating Office Web Apps(OWA)with your custom solution which built with SharePoint CSOM/ JSOM or with integration of any client site development. Specially in a scenario where you develop your own “SharePoint display template” following integration points will be useful;

View in office web apps

Following link will work; if your requirement is to open your document in OWA. This can be done with simply appending parameter as below;

<uri to your document>?Web=0

Eg:
http://mydomain.local/sites/OWASite/Documents/TechCentro.docx?Web=0

Edit SharePoint documents in OWA

Following way of integration with the Office Web apps which let you to pick your action is; means that whether your action may be read, edit or your default setting.

<Web absolute URi>_layouts/15/WopiFrame.aspx?sourcedoc=<Relative URi to document>&action=<Your action>

Summary of actions as below;

 

&action=default -> Gets default setting of the documents
&action=view    -> Open office app as a read only
&action=edit    -> Open office app as editable

Eg:

http://mydomain.local/sites/OWASite/_layouts/15/WopiFrame.aspx?sourcedoc=/sites/OWASite/Documents/BestPractices.docx&action=edit

You can be changed the default behavior with following approach
https://technet.microsoft.com/en-us/library/ee837425.aspx?f=255&MSPPError=-2147217396

Building URL to the Office Web Apps

If you thinking about how to build your URL; following illustration may be useful.

var owauri="_spPageContextInfo.webAbsoluteUrl" //absolute URL of the SharePoint site
+"/_layouts/15/WopiFrame.aspx?sourcedoc=" //static phrase
+"/sites/OWASite/Documents/TechCentro.docx" //Relative URL to the document
+"&action=edit //Action parameter

Useful resources

https://technet.microsoft.com/en-us/library/ff431685.aspx