In this post I want to take a look at using the client-side taxonomy picker wrapped up as an AngularJS directive, in an app running on an Officer 365 site. In a subsequent post I'll expand on the how the code works, but this post is just intended to give a quick overview of it.
You can download the code from Github here: https://github.com/matthewyarlett/AngularJS-Client-side-Taxonomy-Picker-Directive
The Taxonomy Picker control comes from the Office 365 Developer Patterns and Practises site.
The files for this app are uploaded to a folder on the root of the site. The apps parent file, app.html, is added to a page via Content Editor Webpart.
The app looks like this:
To use the directive, follow these basic steps.
1. Add the CSS and script references to your apps html page.
The Taxonomy Picker control comes with it's own CSS, so you need to include this.
<link href="../angularjs-taxonomy/Styles/taxonomypickercontrol.css" rel="stylesheet" />
You need to add a reference to the JS file the directive is declared in, as well as all of the Microsoft Scripts that the SharePoint Taxonomy Picker requires, as well as the scripts the app requires.
<!-- Load the constant variables --> <script type="text/ecmascript" src="../angularjs-taxonomy/config/config.constants.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/models/models.js"></script> <!-- Load third party scripts --> <!-- AngularJS, Sanitize, resource --> <script type="text/ecmascript" src="../angularjs-taxonomy/scripts/angular.min.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/scripts/angular-sanitize.min.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/scripts/angular-resource.min.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/scripts/angular-route.min.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/scripts/ui-bootstrap.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/scripts/jquery-1.9.1.min.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/scripts/taxonomypickercontrol.js"></script> <!-- All of this scripts are used to create the app. --> <script type="text/ecmascript" src="../angularjs-taxonomy/app.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/config/config.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/config/config.taxonomy.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/common/common.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/common/logging.js"></script> <script type="text/ecmascript" src="../angularjs-taxonomy/controllers/controllers.js"></script>
2. Add the directive as a dependency to your app.
(function () { 'use strict'; var app = angular.module('app', [ //inject other Angular Modules 'ngSanitize', 'ngResource', 'ui.bootstrap', //add the tax picker directive 'ui.TaxonomyPicker', //inject App modules 'common' ]); })();
3. Add the directive to the page (you can add multiple instances of it).
When add the directive, it has several attributes that can be set to control the behaviour of the taxonomy picker.
Most aren't mandatory, but you must add the data model (via ng-Model), and you must add the pp-ready-to-load attribute (which tells the directive the data model has updated, and is ready to be used).
Possible attributes and they're values
| Attribute | Possible values | Default value | Required? |
|---|---|---|---|
| data-ng-model | An array, containing a list of terms, in the following format: var termsArray = [{ 'Name': object.TermLabel, 'Id': object.TermGuid}] | null | Yes (you must supply a model to the data-n-model attribute, but it contain a null value) |
| data-pp-ready-to-load | true | false | false | Yes (the taxonomy picker will not render until this value is set to true) |
| data-pp-is-multi-valued | true | false | false | No |
| data-pp-width | Any numerical value, followed by 'px' | 220px | No |
| data-pp-termsetid | The GUID of the termset. E.g. a5bd4ff2-2823-4ea2-8dd6-2d02c845493b | null | No |
| data-pp-is-hashtags | true | false | false | No |
| data-pp-is-keywords | true | false | false | No |
An example of adding a the taxonomy picker that references a termset;
<div ui-Taxonomy ng-model="vm.terms" pp-ready-to-load="{{vm.loadTaxonomyPickers}}" pp-termsetid="a5bd4ff2-2823-4ea2-8dd6-2d02c845493b" pp-is-multi-valued="{{true}}" id="taxPickerGeography" ></div>
An example of adding a the taxonomy picker that references the hashtags termset;
<div ui-Taxonomy ng-model="vm.hashtags" pp-ready-to-load="{{vm.loadTaxonomyPickers}}" pp-is-hashtags="{{true}}" pp-is-multi-valued="{{false}}" id="taxPickerHashtags" ></div>
An example of adding a the taxonomy picker that references the keywords termset;
<div ui-Taxonomy ng-model="vm.keywords" pp-ready-to-load="{{vm.loadTaxonomyPickers}}" pp-is-keywords="{{true}}" pp-is-multi-valued="{{true}}" id="taxPickerKeywords" ></div>
4. Load the data for the model.
Before initialising the directive (via changing the value of the property used in the data-pp-ready-to-load attribute to true), ensure you up the data model used for the taxonomy picker with the current data (if any).
For example, you might perform a REST call to get the current values in a list item. You would then create the model for the taxonomy picker when data from the REST call is returned.
After updating the data in the taxonomy pickers model, you would then change the value of the property used in the data-pp-ready-to-load attribute to true.
The code below shows an example of doing this.
//App Controller (function () { 'use strict'; var controllerId = 'appCtrlr'; angular.module('app').controller(controllerId, ['$scope', appCtrlr]); function appCtrlr($scope) { var vm = this; vm.data = []; vm.context = null; vm.terms = []; //The data model for the taxonomy picker requires an array of values. Each value //represents a term, and has the Id and Name properties. The Id property takes the //terms TermGuid and the Name property correlates to the terms Label property. vm.terms = [{Id:"dc146209-c1b2-697e-c0e2-9259ba19e750",Name:"Failed Inspection"}]; vm.keywords = []; vm.hashtags = []; vm.loadTaxonomyPickers = true; init(); function init() { //init code. //e.g. get data via REST and set the data model. } } })();
As a side note, when you perform a REST call to Office365 or SharePoint, for a taxonomy
field, the data comes back as an object that has the TermGuid and Label properties, as seen in the following screen capture from Fiddler:
Internally, the Microsoft Client-side Taxonomy control requires the field properties as Id and Name,
which is why we format the input object with those properties above.
However, for the sake of usability, you can also pass in the raw value from a REST call. In this case, the init function might look like this (no formatting of the data takes place):
function init() { getData().then(function(data){ vm.data = data; vm.loadTaxonomyPickers = true; if (!$scope.$root.$$phase) { $scope.$apply(); } }) }
And the HTML for the control, might look like this (note the vm.data.tags.results object that is passed in as the model).
<div ui-Taxonomy ng-model="vm.data.Tags.results" pp-ready-to-load="{{vm.loadTaxonomyPickers}}" pp-termsetid="a5bd4ff2-2823-4ea2-8dd6-2d02c845493b" pp-is-multi-valued="{{true}}" id="taxPickerTags" ></div>
That's it - as far as initialising and using the control goes.
To use the value(s) of a the taxonomy picker directive while the page is open, simple reference the taxonomy picker model, like you would any other property within a controllers data model.
<span data-ng-repeat="r in vm.terms track by $index"> {{r.Name}} <span style="color:BURLYWOOD;">(Path: {{r.PathOfTerm}})</span><span data-ng-if="!$last">, </span> </span>
Persisting the value(s) of the a taxonomy picker control is just as easy. You use the data in the taxonomy pickers model to write back to the server.
In the example below, I have a model used in a REST call for updating a list item that has a taxonomy field. Data from the model (used by taxonomy picker directive) is formatted for the REST call. Each term in the array of terms is transformed into a term string, that can be passed to the server via the REST call.
sr.models.shipInfoModel = function (id) { this.Id = id ? id : -1; //"pa28754972f84ff7a6bf3e4762f23e23" is the hidden text field (automatically) created for the taxonomy field //This is the field that you need to use to update the taxonomy field via REST. //You need to format selected terms as GUID|Label pairs this.pa28754972f84ff7a6bf3e4762f23e23; this.__metadata = { type: 'SP.Data.SrShipRegisterListItem' }; } function populateShipInfoModel(srcModel, tagsTerms) { var dstModel = new sr.models.shipInfoModel(srcModel.Id); //Update the taxonomy field values if(srcModel.Tags && srcModel.Tags.results){ if(srcModel.Tags.results.length == 0){ dstModel.pa28754972f84ff7a6bf3e4762f23e23 = ''; }else{ for(var i = 0; i < srcModel.Tags.results.length; i++) { var t = srcModel.Tags.results[i]; dstModel.pa28754972f84ff7a6bf3e4762f23e23 = dstModel.pa28754972f84ff7a6bf3e4762f23e23 + ';' + t.Name + '|' + t.Id; } } } dstModel.__metadata.etag = srcModel.__metadata.etag; dstModel.__metadata.id = srcModel.__metadata.id; dstModel.__metadata.uri = srcModel.__metadata.uri; return dstModel; }
And that's it!
