Anuja Bhojani

This post will show how to read the Taxonomy Term Store with JSOM. Taxonomy Term store can be accessed in a SharePoint App, with permission scope of Taxonomy. To be able to use the JSOM API for Taxonomy you need to reference SP.Taxonomy.js found in _layouts/15/ the best way to reference this would be in the document ready. $(document).ready(function () { var scripRef = _spPageContextInfo.webServerRelativeUrl + "/_layouts/15/"; $.getScript(scripRef+ "SP.Runtime.js", function () { $.getScript(scripRef+ "SP.js", function () { $.getScript(scripRef+ "SP.Taxonomy.js", function () { context = SP.ClientContext.get_current(); //Call your code here. getTermStores(); });});});}) Read from Taxonomy function getTermStores() { session = SP.Taxonomy.TaxonomySession.getTaxonomySession(context); termStores = session.get_termStores(); context.load(session); context.load(termStores); context.execute...

Already, there are so many articles published about the new features and changes in SharePoint Designer 2013 that it’s a little late to write about this. But I think this would be useful. There are many new functionalities and enhancements added into SharePoint designer 2013. Added features allow designers to do more with workflows without requiring a developer to write custom code. If you select SharePoint 2013 option while creating workflow, you will get the following list of new features 1. Stages With 2013, concept of stage is introduced. It acts as containers in workflow, which allows one to structure the workflow from one stage to the other. Stages can be added to a workflow by clicking on Stage icon. Key points for Stages: All actions in the workflow must be contained in a stage A stage can hold one or more workflow actions, and will also have only one  Transition to stage  area.  The  Transition to st...

Workflow is getting cancel with the HTTP 500 error.  Problem: RequestorId: 9dea9a29-bb82-214a-0000-000000000000. Details: RequestorId: 9dea9a29-bb82-214a-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 500 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["30"],"SPRequestGuid":["9dea9a29-bb82-214a-92f0-943af4411ac2"],"request-id":["9dea9a29-bb82-214a-92f0-943af4411ac2"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Fri, 31 Jan 2014 20:19:03 GMT"...