Wednesday, August 31, 2016

Full Farm Backup fails - Causes and Solutions

Requirements to check before moving on to the Errors section..

  1. Shared Folder need to be created & full control has to be granted to timer job, SQL Server service accounts and CA's app pool account
  2. SQL Server VSS Writer service, that facilitates the backup/restore, should be running
  3. SharePoint Administration Service should be running on all servers of the farm

Error 1: Here WSS_xxx is any database.

Object WSS_XXXX failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup directory. SqlException: Cannot open backup device '\\Backup\spbr0000\0000015d.bak'. Operating system error 3(The system cannot find the path specified.). BACKUP DATABASE is terminating abnormally.

Possible Reason Solution
The path given for the backup is wrong Check the path & Correct it. It must be a Shared folder
Insufficient privileges, i.e. The Windows SharePoint Services Timer V4 (SPTimerV4) and the SQL Server service account perform backup/restore operations on behalf of the requested user. Hence these accounts should have full control on the backup locations While sharing the folder, granting 'Full Control' to 'Everyone' will not work. The domain account(ideally), under which the Timer Service & SQL Server service execute, should be explicitly granted 'Full Control' on the shared folder

Find SQL Server Accounts that carry out backup/restore by checking the below services...

SQLService.png

Sharing the folder:

Folder Sharing

Error 2: User Profile Synchronization service instance causes this issue.

FatalError: Object UPS failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup directory. SPDuplicateObjectException: An object of the type Microsoft.Office.Server.Administration.ProfileSynchronizationUnprovisionJob named "ProfileSynchronizationUnprovisionJob" already exists under the parent Microsoft.SharePoint.Administration.SPTimerService named "SPTimerV4". Rename your object or delete the existing object.

Possible Reason Solution
 The 'User Profile Synchronization service'(CA -> Manage Services on server) instance is in 'Stopping' state  Let the service instance be in a Start/Stop state. Not in 'ing' state.

Note: Usually this error is thrown when we try to unprovision a service instance which is already in 'stopping' state. Here the timer job may not be trying to unprovision the instance, however, it checks the job queue to ensure that no jobs are executing so that the system gets stored/backed up in a stable state.

Error 3: Search Service Application causing the issue

FatalError: Object Search Service Application failed in event OnBackup ...

Possible Reason Solution
 The Timer job service account doesn't have permission on the Search Service Application Grant Full Control permission to the timer job service account on the Search Service Application
 Search Service account doesn't have permission to the shared folder Share the folder to the search service account with full control

Note: Try narrowing down the permissions as much as possible. It's not advisable to grant Full Control unless it's really needed.

Original Post


by Saratchandra Peddinti via Everyone's Blog Posts - SharePoint Community

Tuesday, August 30, 2016

SharePoint Community Newsletter - Week 35

Hello and welcome to this week’s newsletter.

For this issue, it’s all about opportunities to learn from the community. We have some great posts from members who want to share thoughts and ideas with you (some even in book form!) and invite you to take part in the debate.

We also have some great free events to remind you about. With these, from the comfort of your own seat, you can cast your net even more widely to find the answers and information you need. Enjoy the newsletter!

Deploying SharePoint 2016: Best Practices for Installing, Configuring, and Maintaining SharePoint Server 2016 (Vlad Catrinescu)

Are you a SharePoint Admin that wants to learn how to properly deploy SharePoint 2016? In this book you will learn how to install and configure SharePoint 2016 in depth, and how to optimize your environment based on real world best practices. Readers will benefit from the most stable and performance driven SharePoint 2016 environments possible. Pre-Order the eBook or your hardcover copy today!

eBook : http://spvlad.com/DeployingSharePointeBook
Amazon.com: http://spvlad.com/DeployingSharePointUS
Amazon.ca: http://spvlad.com/DeployingSharePointCA

SharePoint as a Knowledge and Ideation Platform with Mike Oryszak (Christian Buckley)

In a recent webinar, Christian was joined by long-time community member Mike Oryszak (@next_connect) from B&R Business Solutions as they discussed the pros and cons of SharePoint as a knowledge management platform, and how idea management could be leveraged to bolster your KM efforts.

http://ift.tt/2bG6boK

Clearing the myths between Request Management service in SharePoint 2013 and Network Load balancer (Vignesh Ganesan)

I’m pretty sure that a lot of SharePoint people out there have written a lot about Request Management service in SharePoint 2013 and Load balancer configuration for a SharePoint 2013 farm, however there seems to be a lot of confusion among SharePoint practitioners in understanding the difference between these two …

http://ift.tt/2bP4yZq

Display SharePoint List Data in a Jquery Data Table (Viipiin Tyagi)

Everybody knows that technology is changing rapidly. There are many things that we can integrate together. In this article, we are going to see, how to integrate the data table with SharePoint.

http://ift.tt/2bG6b8a

Want to join your peers and dig beneath the surface of SharePoint and Office365? Get registered at one of our free events and find the real gems before someone else does:--

Our free events bring you all this – and some more besides - giving you innovative, interesting (and fun) insights into all aspects of SharePoint and Office365.

It doesn’t matter if you are starting out or becoming a bit of a guru, there’s an event that’s will help you. Check out the links below:

COLLAB365 SUMMER GAMES - Curated with our very good friends at Metalogix, the Collab365 Summer Games are designed to build SharePoint muscle, refine Office365 technique and build your skills to help you become a Summer Games Champion! Watch this space for more details and Get your free place now here - http://ift.tt/2aWl5ot

COLLAB365 SOLUTIONS DAY – September 14th - Join us from 16:00 UTC to watch demonstrations from some great vendors - Find out more and register here - http://ift.tt/2bG7zYs

COLLAB365 24HR GLOBAL CONFERENCE -Join the Collab365 team on the 19th - 20th October, for 24 hours of SharePoint, Azure and Office365 content. Get more details and register for your FREE place here - http://ift.tt/2bP4jNV

And Finally …
Over the coming weeks we are going to be posting a series of interview style blog posts all about you. They are going to be posted and promoted on SharePoint-community.net plus Collab365 Global Conference in a "meet the community" series. Take part here …

http://ift.tt/2bdTCPM


by Jon Manderville via Everyone's Blog Posts - SharePoint Community

SharePoint 2013 References

SharePoint 2013 Installation

  1. SharePoint 2013 Developer’s Installation Guide – LinkTech
  2. SharePoint 2013 Deployment Guide

SharePoint 2013 Architecture & Governance

  1. Microsoft SharePoint 2013: Designing and Architecting Solutions
  2. Microsoft SharePoint 2013: Planning for Adoption and Governance

SharePoint 2013 Development

  1. Beginning SharePoint 2013 Development
  2. Professional SharePoint 2013 Development
  3. SharePoint 2013 For Dummies
  4. Exploring Microsoft SharePoint 2013
  5. Microsoft SharePoint 2013 Developer Reference
  6. Microsoft SharePoint 2013 Inside Out
  7. Inside Microsoft SharePoint 2013
  8. Exam Ref 70-332: Advanced Solutions of Microsoft SharePoint Server 2013
  9. Exam Ref 70-331: Core Solutions of Microsoft SharePoint Server 2013
  10. QuickBooks 2013: The Missing Manual
  11. Custom SharePoint Solutions with HTML and JavaScript
  12. Microsoft SQL Server 2014 Business Intelligence Development
  13. Professional Visual Studio 2013
  14. QuickBooks 2013: The Missing Manual

SharePoint 2013 App Development

  1. Pro SharePoint 2013 App Development
  2. Microsoft SharePoint 2013 App Development

SharePoint 2013 PowerShell

  1. Beginning PowerShell for SharePoint 2013

SharePoint 2013 Business Intelligence

  1. Business Intelligence in Microsoft SharePoint 2013
  2. Pro SharePoint 2013 Business Intelligence Solutions

SharePoint 2013 Branding

  1. Pro SharePoint 2013 Branding and Responsive Web Development
  2. SharePoint 2013 Branding and User Interface Design

SharePoint 2013 Administration

  1. Professional SharePoint 2013 Administration
  2. Pro SharePoint 2013 Administration, 2nd Edition
  3. Microsoft SharePoint 2013 Disaster Recovery Guide
  4. Microsoft SharePoint 2013 Administration Inside Out

SharePoint 2013 Enterprise Content Management

  1. SharePoint 2013 WCM Advanced Cookbook
  2. Practical SharePoint 2013 Enterprise Content Management

SharePoint 2013 User Guides

  1. SharePoint 2013 User’s Guide, 4th Edition

by Prashant Bansal via Everyone's Blog Posts - SharePoint Community

Clearing the myths between Request Management service in SharePoint 2013 and Network Load balancer:

Alright. So the heading of this article would have pretty much given a brief explanation about what this post would be about and hence I’m not going to write a brief introduction session here about this post. I’m pretty sure that a lot of SharePoint Geeks out there have written a lot about Request Management service in SharePoint 2013 and Load balancer configuration for a SharePoint 2013 farm, however there seems to be a lot of confusion among SharePoint practitioners in understanding the difference between these two .I didn’t mean to offend anybody here but the features and functionalities of these two are so similar so that anybody would possibly get confused. So in this post I’ll be explaining what these two mean in detail and how they differ from each other (meaning where the boundary for Request Management service stops when compared to a load balancer).

Now let’s get into the meats and potatoes ….

1. Request Management service in SharePoint 2013 :

For those who are new to SharePoint 2013 or if you’re hearing about “Request Management service”  for the first time , please go ahead and take a look at my blog post on Request Management service .  I’ve given a detailed explanation on what “Request Management service” is all about and how it works. However, to put it in simple words….Request Management service take care of managing  incoming requests by evaluating the logic rules set against them in order to determine which action to take, and which machine or machines in the farm (if any) should handle the incoming requests . Now there’s a lot of mechanism which happens in RM service, please take a look on Spencer Harber’s article on Request Management service to know about that in detail. As always Spencer has did a fabulous job in explaining it on detail.

In addition to this there are couple of other important points that one should be aware of as far as Request Management service is concerned.

  1. Request manager is the first code that runs in response to HTTP requests. It is implemented in SPRequestModule
  2. Request Manager requires the SharePoint foundation web application service to be started on the server.
  3. Request manager service should only be started on a server that’s acting as a WFE, else it’s of no use.

1.png

2.Load balancer for SharePoint :

Now as you’re aware high availability in SharePoint is achieved in the web tier level by deploying multiple front end servers to serve web pages and host web parts. A load balancer directs traffic across these servers, monitors health and ensures that the best possible target is used for individual requests. The default SharePoint architecture works in such a manner that any server in the farm which has the “SharePoint foundation web application service “turned on will be acting as a Web Front end server. Hence you can go ahead and turn off this service on a server that is acting as an App server. However, if your servers have enough resources then there shouldn’t be any harm on leaving it on, as in case if you WFEs go down you can let APP server handle user web requests temporarily.

2.png

Now let’s discuss on how they differ from each other so that we don’t get confused by their similar functionalities:

The first thing which we need to understand is that the Request Management service becomes effective only when the user request gets passed the Network Load balancer which takes care of handling user traffic . As you’re aware the NLB is the one which takes care of handling user traffic and if a user’s request doesn’t even gets passed the load balancer then technically it means that the user’s request is not hitting the SharePoint farm where the Request management service is configured .To put it in simple words the user’s request need to pass the 1st gate which is the NLB and only upon the successful completion of that the user’s request will hit the appropriate Web front servers where the Request Management service will be configured . So once the user’s request hits the SharePoint farm then the RM service will validate the request and will then act accordingly. I believe the image below will give you a clear understanding of how this is configured for a SharePoint 2013 farm.

Dedicated mode:

3.jpgIntegrated Mode:

4.jpg

In both the modes you can notice that the user traffic first has to go through the HLB before it reaches the SharePoint 2013 farm where the Request Management service is configured. Now if you’re more curious in understanding the difference between the above said two modes ….In the first mode (i.e. Dedicated mode) you will have a SharePoint farm configured only for Request management service (meaning all the servers in that farm will have only the RM service turned on the WFE’s) .In this mode the SharePoint farm which has the RM service configured will be configured in such a way that it’s kept between the LB and the actual PROD server where the user’s content exist. The second one is called the (Integrated mode) where you will find the RM service being turned on all the WFE servers in the SharePoint farm. The first mode is pretty expensive bearing in mind the license costs and will be mostly used in very large SharePoint farm implementations .The second mode is pretty affordable because in this mode all the WFE servers which are part of the actual farm will have the RM service turned on in it.

To conclude RM service and NLB/HLB are two different things altogether and they don’t suffice the same purpose .The NLB/HLB takes care of sending the user request to the appropriate WFE’s whereas the Request management service takes care of how to handle that incoming request which is sent to the WFE server . Both these are optimal for any successful SharePoint implementation.

Thanks for reading this post …..Happy SharePointing!!!


by Vignesh Ganesan via Everyone's Blog Posts - SharePoint Community

Display SharePoint List Data In Jquery Data Table

Hi,

My first blog post on sharepoint-community.net

Everybody knows that technology is changing rapidly. There are many things that we can integrate together. In this article, we are going to see, how to integrate the data table with SharePoint.

So, what is a data table?

As per Data Table’s official site definition:
“Data Table is a plug-in for the jQuery JavaScript library. It is a highly flexible tool, based upon the foundations of the progressive enhancement and will add the advanced interaction controls to any HTML table.”

Scenario

We are starting our scenario.

Before starting with this post, we must have some basic knowledge of the following:

  • HTML Tables
  • Rest API in SharePoint
  • JavaScript Objects

First of all, create a SharePoint list, where we are going to retrieve our data and display it in our data table. For this, go to your SPO site and create a custom list. In my case, my list name is Employee, given below:

Employee

Now, add some columns to display in our list.

column

Some of the default columns are always there, when we add our custom columns to the list. Now, add some dummy data to our list, as shown below:

list

Note: Change the list view as per your requirement.

Now, we move to the functionality part, that suggests how we can get the data from SharePoint list. For this, we need two files; one is HTML file to render the data and another one is JS file to get the data from SharePoint list.

Go to Data Table CDN to get the required JS and CSS files.

We need to follow CDN scripts, that are required to be used in our functionality,

Now, create the HTML file in a text editor (In our case, we are using Sublime Text 3).

  1. <!DOCTYPE html>  
  2. <html>  
  3.   
  4. <head>  
  5.     <title>WiFi Home</title>  
  6.     <script type="text/javascript" src="http://ift.tt/1U8oWnO"></script> //External js file to get data from SharePoint List  
  7.     <script type="text/javascript" src="/SiteAssets/GetData_Wifi.js"></script>  
  8.     <link rel="stylesheet" type="text/css" href="http://ift.tt/29qPyQN">  
  9.     <link rel="stylesheet" type="text/css" href="http://ift.tt/29s0XMe">  
  10.     <script type="text/javascript" src="http://ift.tt/1XWLCXq"></script>  
  11. </head>  
  12.   
  13. <body>  
  14.     <table id="table_id" class="display" cellspacing="0" width="100%">  
  15.         <thead>  
  16.             <tr>  
  17.                 <th>Name</th>  
  18.                 <th>Position</th>  
  19.                 <th>Office</th>  
  20.                 <th>Age</th>  
  21.                 <th width="18%">Start date</th>  
  22.                 <th>Salary</th>  
  23.             </tr>  
  24.         </thead>  
  25.         <tfoot> </tfoot>  
  26.     </table>  
  27.     </div>  
  28. </body>  
  29.   
  30. </html>  

Now, we have to create JavaScript file (GetData_Wifi.js) to get the data from SharePoint list

For this, write a function to get the data, using REST API.

  1. function loadMyItems() {  
  2.     var siteUrl = _spPageContextInfo.siteAbsoluteUrl;  
  3.     var oDataUrl = siteUrl + "/_api/web/lists/getbytitle('Employee')/items?$select=Name,Position,Office,Age,StartDate,Salary";  
  4.     $.ajax({  
  5.         url: oDataUrl,  
  6.         type: "GET",  
  7.         dataType: "json",  
  8.         headers: {  
  9.             "accept""application/json;odata=verbose"  
  10.         },  
  11.         success: mySuccHandler,  
  12.         error: myErrHandler  
  13.     });  
  14. }  

Now, the next thing is how to bind this data to our view (HTML) via data table?

For this, let's put our success code in mySuccessHandler function (this is a part of asynchronous programming).

  1. function mySuccHandler(data) {  
  2.     try {  
  3.         var dataTableExample = $('#table_id').DataTable();  
  4.         if (dataTableExample != 'undefined') {  
  5.             dataTableExample.destroy();  
  6.         }  
  7.         dataTableExample = $('#table_id').DataTable({  
  8.             scrollY: 300,  
  9.             "aaData": data.d.results,  
  10.             "aoColumns": [{  
  11.                 "mData""Name"  
  12.             }, {  
  13.                 "mData""Position"  
  14.             }, {  
  15.                 "mData""Office"  
  16.             }, {  
  17.                 "mData""Age"  
  18.             }, {  
  19.                 "mData""StartDate",  
  20.                 "render": function(mData) {  
  21.                     var date = new Date(mData);  
  22.                     var month = date.getMonth() + 1;  
  23.                     return (month.length > 1 ? month : "0" + month) + "/" + date.getDate() + "/" + date.getFullYear();  
  24.                 }  
  25.             }, {  
  26.                 "mData""Salary",  
  27.                 "render": function(mData) {  
  28.                     var sal = new Object(mData);  
  29.                     var commaSep = mData.toString().split(".");  
  30.                     commaSep[0] = commaSep[0].replace(/\B(?=(\d{3})+(?!\d))/g, ",");  
  31.                     sal.rup = "<span>₹</span>";  
  32.                     return ((sal.rup) + " " + commaSep.join("."));  
  33.                 }  
  34.             }]  
  35.         });  
  36.     } catch (e) {  
  37.         alert(e.message);  
  38.     }  
  39. }  
  40.   
  41. function myErrHandler(data, errMessage) {  
  42.     alert("Error: " + errMessage);  

Our final JS file will look, as follows:

  1. $(document).ready(function() {  
  2.     loadMyItems();  
  3. });  
  4.   
  5. function loadMyItems() {  
  6.     var siteUrl = _spPageContextInfo.siteAbsoluteUrl;  
  7.     var oDataUrl = siteUrl + "/_api/web/lists/getbytitle('Employee')/items?$select=Name,Position,Office,Age,StartDate,Salary";  
  8.     $.ajax({  
  9.         url: oDataUrl,  
  10.         type: "GET",  
  11.         dataType: "json",  
  12.         headers: {  
  13.             "accept""application/json;odata=verbose"  
  14.         },  
  15.         success: mySuccHandler,  
  16.         error: myErrHandler  
  17.     });  
  18. }  
  19.   
  20. function mySuccHandler(data) {  
  21.     try {  
  22.         var dataTableExample = $('#table_id').DataTable();  
  23.         if (dataTableExample != 'undefined') {  
  24.             dataTableExample.destroy();  
  25.         }  
  26.         dataTableExample = $('#table_id').DataTable({  
  27.             scrollY: 300,  
  28.             "aaData": data.d.results,  
  29.             "aoColumns": [{  
  30.                 "mData""Name"  
  31.             }, {  
  32.                 "mData""Position"  
  33.             }, {  
  34.                 "mData""Office"  
  35.             }, {  
  36.                 "mData""Age"  
  37.             }, {  
  38.                 "mData""StartDate",  
  39.                 "render": function(mData) {  
  40.                     var date = new Date(mData);  
  41.                     var month = date.getMonth() + 1;  
  42.                     return (month.length > 1 ? month : "0" + month) + "/" + date.getDate() + "/" + date.getFullYear();  
  43.                 }  
  44.             }, {  
  45.                 "mData""Salary",  
  46.                 "render": function(mData) {  
  47.                     var sal = new Object(mData);  
  48.                     var commaSep = mData.toString().split(".");  
  49.                     commaSep[0] = commaSep[0].replace(/\B(?=(\d{3})+(?!\d))/g, ",");  
  50.                     sal.rup = "<span>₹</span>";  
  51.                     return ((sal.rup) + " " + commaSep.join("."));  
  52.                 }  
  53.             }]  
  54.         });  
  55.     } catch (e) {  
  56.         alert(e.message);  
  57.     }  
  58. }  
  59.   
  60. function myErrHandler(data, errCode, errMessage) {  
  61.     alert("Error: " + errMessage);  
  62. }  

Now, move to SharePoint part. First, upload the above JavaScript and HTML file to Site Assets library of SharePoint or whatever library you want.

Create a Webpart Page (Named DataTable) and store it in the pages or the site pages library.

Add a content editor to DataTable Page. Now, give HTML file reference to the content editor into Content Editor.

Content Editor

Click OK and save the page.

Now, our final output is shown below:

output

It’s Cool!


Now, play with the UI, provided by the data table plugin.

Conclusion: Thus, in this way, we see how we can work with DataTables and SharePoint together.

Did I miss anything that you may think is required? Maybe this is useful for someone. I hope you like it. Please share your valuable suggestions and feedback.


by Viipiin Tyagi via Everyone's Blog Posts - SharePoint Community

Manageable collaboration as the key to your CXM cycle vitality

When approaching customer experience management, companies traditionally focus on the CRM-based cycle, which is reasonable since no software knows customers better than CRM. In our practice, we also see CRM as the core of the 4-step approach to managing customer experience that includes data collection, analysis, targeted actions and result re-evaluation. However, the CXM chain has one more important component, and this is collaboration of CXM participants that ensures success of the entire cycle.

This is exactly where SharePoint comes up to the stage to take up the collaboration challenge and make the complex customer experience management process more dynamic, facilitate stakeholders’ communication and minimize their efforts.  

CXM-related collaboration is painful but vital

To show how important collaboration is in the CXM cycle, let’s start with an example straight away.

A US retailer with 1,000+ stores in 7 states registered a significant decrease of customer satisfaction in 17 stores. The investigation showed that this negative trend was caused by long queues at peak hours in 15 of 17 stores. CX managers developed a plan to change the situation. However, as soon as they initiated corrective actions, they got involved into intense negotiations with operational and HR departments. Moreover, CX experts met a strong resistance from store managers who weren’t ready for additional expenses without being sure that the measures would prove successful. This led to pretty modest results since real actions were approved only for 5 of 17 stores.

This short example shows that CXM-related collaboration can become a mammoth-heavy task, since it involves employees from absolutely different departments and of different hierarchical levels. To make things even worse, CXM collaboration can be painful and often leads to the conflict of interest, since CX-managers’ initiatives usually require quite deep changes to the established operational approach with no benefits guaranteed (in our case, improvements were eventually registered in 4 of 5 stores).

Full of human-related pitfalls, CXM collaboration cannot be left as it is, scattered and uncontrollable, since it engenders a whole range of negative consequences.

Unmanaged collaboration ruptures the CX cycle. Without efficient collaboration and all the stakeholders being involved into the discussion on an improvement plan, CX managers risk to get stuck at the stage of data analysis, unable to transform their insights into real actions.  

Sluggish collaboration slows down the CXM cycle. When it comes to enhancing customer experience, every day counts, and delays are inacceptable as they can make situation even worse and ruin a brand’s reputation. Dedicated collaboration tools should be adopted to ensure more effective and quick decision-making based on the strategy elaborated by all the parties and not exclusively on arrangements made during face-to-face meetings.

Collaboration gaps bring inappropriate results. As CXM collaboration involves employees of different hierarchical levels, CX managers should coordinate their actions with all of them. Not approved by all stakeholders, CX managers’ initiatives can cause not only conflicts between the CXM cycle participants but also lead to significant financial losses.

Managing CXM-related collaboration in SharePoint

Since CXM-related collaboration is often unpleasant and hides a whole range of pitfalls, the task is to facilitate it and make it more effective, dynamic and streamlined. Trying to adapt CRM software for these purposes may have a not-so-happy ending, since a company will have to venture quite a deep customization and face heavy license costs to provide access to all the stakeholders (who may simply reject working in a CRM).

Not to make the collaboration challenge even more problematic, it’s reasonable to delegate it to a dedicated platform with collaboration at its heart, such as SharePoint. Companies can both implement SharePoint for CXM needs as a stand-alone tool or integrate it with the corporate CRM. In any case, SharePoint offers large capabilities of transforming CXM collaboration into a well-managed and effective process.

Fine-tuning cross-department collaboration

SharePoint is a proven platform in terms of cross-department collaboration, thus it can successfully unite participants of the CXM cycle. There are several opportunities for this. For example, a company can develop a fully functional CXM collaboration site for stakeholders to work on each particular CXM case, discuss problematic issues and take decisions. Another feasible solution is to integrate a SharePoint-based collaboration solution with a CRM. This will allow CX managers to create independent collaboration boards linked with CX cases and subcases.

Transforming unmanaged collaboration into formalized CXM workflows

The biggest challenge of any collaboration is to evolve from spontaneous communication to a managed process with precise stages to complete. To structure CXM collaboration, companies can transform it into a traditional workflow that will include the following sequence of steps: discussion, decision-making, actions (started, delayed or ended), progress review, escalation and final result.

The workflow can be coupled with task management features for every workflow participant to see the to-do activities along with their precise deadlines.

Facilitating document management

To take the burden off a CRM, CXM-related document management can be organized within SharePoint. This way, all documents will be centralized in a general storage classified by customers, cases and CXM techniques. Documents will be easy to find, read, edit and shared with colleagues at any moment.

Creating CX knowledge base

SharePoint not only gives the opportunity to manage CXM-related collaboration and CXM tasks but also assists companies in creating their unique knowledge base for corporate CXM expertise. This would provide CX managers with the possibility to review older cases, study their details and apply more effective measures for new cases. It would also help onboarding CX managers to quicker adapt and understand the CX methodology of a particular company by studying corporate CX archives.

How to make it work?

Making such a CRM-SharePoint tandem work effectively is a challenging task that can be fulfilled only by the experts with a deep understanding of both customer experience management principles and SharePoint development to align a company’s CXM needs with the software capabilities.  

It’s also crucial to define a precise scope of the future CXM-related collaboration. This will help to design a tool that will help stakeholders to solve CXM issues easier and less painfully, along with making collaboration more result-oriented and controllable with customer experience improvement as a priority.


by Sergei Golubenko via Everyone's Blog Posts - SharePoint Community

Monday, August 29, 2016

Office 365 Patterns and Practices PowerShell Commands

By now you have heard about the great project that Microsoft and the Community have been working on called “Patterns and Practices”. If not, then you must have been sleeping.

read more


by via SharePoint Pro

SharePoint in The Azure Cloud

So you have come to that point where it is time to either adopt SharePoint as a platform, or maybe you already have it and are now looking to upgrade. The first question becomes, where do we put it?

The whole conversation about the “Cloud” makes this very interesting, which we won’t focus on for this post. Instead we will decide that Microsoft Azure is the place to do this and start to work out how viable it is as an option. Microsoft have done a great job of trying to sell you the Azure Cloud.

read more


by via SharePoint Pro

Office 365 Patterns and Practices PowerShell Commands

By now you have heard about the great project that Microsoft and the Community have been working on called “Patterns and Practices”. If not, then you must have been sleeping J

read more


by via SharePoint Pro

Sunday, August 28, 2016

Azure Resource Manager Template Visualisation with ARMVIZ

Azure Resource Manager Template Visualisation with ARMVIZ

Here's another quick tip for those of you, like me, working with the Azure Resource Manager in various ways. If you're designing templates, there's a pretty slick template visualization tool available called ARMVIZ.

Edit and Visualize your ARM templates

It's pretty basic and simplistic. It gives you an overview of what your Azure Resource Manager template looks like and visualizes them in a comprehensible diagram.

Designer:

Azure Resource Manager Template Visualisation with ARMVIZ

Editor:

Azure Resource Manager Template Visualisation with ARMVIZ

Visualize your own ARM Templates

Since you can easily choose a file from disk or copy-paste code into the editor in order to visualize it, you could also go to your Azure Portal and download the Azure Resource Manager Template (ARM Template) and simply use that in the tool to visualize your own, currently existing templates in Azure. Simple as that.

You can export the json template in various ways. I've previously written a guide for how you can do this using the ARM REST API, available here.

Learn more...

Check out the GitHub repository: http://ift.tt/1NC7ZJM

Check out this YouTube screencast by the author of the tool (previous version, but the concepts remain):


by Tobias Zimmergren via Zimmergren's thoughts on tech

Azure Resource Manager tools for Visual Studio Code

Azure Resource Manager tools for Visual Studio Code

Tip of the day...

If you're the Visual Studio Code kind of person, and you design Azure Resource Manager (ARM) templates for your Azure infrastructure, this extension might come in handy. The Azure Resource Manager Tools extension for Visual Studio Code is a light-weight alternative to the Visual Studio Enterprise template design interface.

Install and Enable Azure Resource Manager Tools for VS Code

From within Visual Studio Code, bring up the command menu (F1 on Windows) and enter ext install and hit Enter:
Azure Resource Manager tools for Visual Studio Code

Use the search box and enter azurerm and search for it, and install the extension as seen below:

Azure Resource Manager tools for Visual Studio Code

Once installed, hit the Enable button and you're good to go:

Azure Resource Manager tools for Visual Studio Code

You'll be prompted to restart Visual Studio Code. Do it, and then you can start editing any of your Azure Resource Manager .json templates with the added support of this extension.

Design your ARM templates, now with added support!

Once you've installed this nifty yet simple extension, you'll have support for intellisense, finding references/usages, peek at definitions etc, all from within Visual Studio Code.

Tip: Shift + F12 will show you usages/all references

Azure Resource Manager tools for Visual Studio Code

Tip: Hover a parameter to see the descriptions/help

Azure Resource Manager tools for Visual Studio Code

Summary

Personally I still like Visual Studio Enterprise for my template design, but if you're the VS Code kind of guy, this extension is great for helping out. I enjoy the simplicity and speed of Visual Studio Code, but still prefer all the features, templates and extensions that I have with the full-featured Visual Studio Enterprise. If you're on a Mac or otherwise running VS Code outside of Windows, this should be beneficial for your ARM template design.

For the full list of current, and future, features - check out the extension website: http://ift.tt/1QhTE8Y

Enjoy.


by Tobias Zimmergren via Zimmergren's thoughts on tech

Friday, August 26, 2016

Sympraxis’ SharePoint Client Side Development Pipeline – Where Should We Put Our Stuff?

This entry is part 2 of 2 in the series Sympraxis Client Side Development Pipeline

As I mentioned in my previous post, when Julie Turner (@jfj1997) joined Sympraxis, we quickly realized we needed to get smarter about managing our code and our overall development process.

One of the first things Julie and I discussed was where we should store our code. Even way back before SharePoint entered my life, I’ve thought of code as content. It’s just a different type of content that has different content management requirements. For this reason, I’ve never fretted too much about storing my code in a SharePoint Document Library or in the Master Page Gallery.

Code as Content

That works fine when you’re a development team of one. But as Julie and I started working on a project together, we knew we needed to do better. Plus, angst and all that. One thing that is key here – and is key in many conversations about stuff like this – is there is no one-size-fits-all answer. Managing code is like managing any other content in that there should be some governance around it. But the governance doesn’t have to be – nor should it be – the same in every instance.

So we thought about what we wanted to be able to accomplish. Basically, what our requirements were to get rolling.

  • We needed an offsite (meaning not just on our machines) repository. This would make us worry less about disaster recovery. We were both doing backups to the cloud (me with Crashplan and Julie with Acronis), but we wanted a repository that belonged to the company, not to either of us personally.
  • We wanted to improve our code reuse. It’s not that we build the same thing over and over, but like the functionality in SPServices, there are some things we do fairly often. In other words, our tricks of the trade. By storing all of our code in one place, we hoped we would make reuse easier.
  • We work with clients on project-based work. Sometimes we work with a client for a while, then they take over for a while, and we reengage with them when a new need arises. We wanted to make it easier for ourselves when that re-engagement happened: basically improve our speed-to-useful again.

As Julie mentioned in her post, she had used Team Foundation Server (TFS) Online at a previous job. I had touched TFS at a previous gig, but like many Microsoft tools it seemed way overblown for our needs. Plus, it’s really tuned for Visual Studio, which I never use.

Julie decided to set up a private Github repository, figuring it would be more palatable to me. I’m always a fan of using things that are simple (Github confused me for years, so I’m not sure it qualifies as simple!) and I liked the fact that we would be using something the wider tech community had stamped with a seal of approval.

GitHub_Logo

We went with an Organization Bronze Plan – which now seems to be obsolete. (Here’s a link to the old plans courtesy of the Internet Archive Wayback Machine.) This gave us up to 10 repos and unlimited users for USD$25/month. Not much money, really, and we figured 10 repos was plenty.

Once we had the repo, we thought about how to organize it. We started with three repos for our organization: clients, admin, and samples. Our thought was that we would put all of the client work artifacts into that one clients repo. It certainly addressed our requirements to work that way. The admin and samples repos would be for Sympraxis administrative stuff and demos or samples we used for speaking sessions, respectively.

This got us up and running. We were both storing our code in a central repository and we could use whatever code editor (or IDE, depending on what terminology you find acceptable) we wanted. I’m using WebStorm a lot these days, but I also use Sublime Text and SharePoint Designer, and… Yeah, whatever works. Julie came from using Visual Studio, but these days she’s mainly using Visual Studio Code.

One of the greatest things about this Brave New World is that what we use to edit code really doesn’t matter that much. I really started liking WebStorm when I realized that its tooling for Github actually made Github make sense to me. I love the ecosystem of plugins for Sublime Text. And no IDE understands SharePoint as well as SharePoint Designer does. So I get to use whatever I need for the task at hand, and so does Julie. We’re just putting the results of that work into the same place.

As we moved forward with this setup, we started to see a few flaws in our thinking. The great thing about being a learning organization (the learning group is YUGE at Sympraxis) is that we comfortably revisit our decisions whenever it makes sense. The clients repo quickly became unwieldy. (Some of you would say “Duh!” here, but we’re fine with the way this went.) We were still manually copying code into our clients’ environments or editing in place and taking copies to dump into Github. We were very happy with Github, but not the mechanics of how we were using it.  So all wasn’t rosy yet.

In my next post, I’ll talk about the next steps we took to tune things…

 


by Marc D Anderson via Marc D Anderson's Blog

Webinars: SharePoint Framework with Microsoft's Bill Baer and Vesa Juvonen

Webinars: SharePoint Framework with Microsoft's Bill Baer and Vesa Juvonen

Lately we've been really busy at Rencore with a lot of things. A thing in particular that we've been active with is the integration of SharePoint Framework analysis into our SPCAF tools.

It's an exciting time ahead, both for us and for anyone developing on the SharePoint stack. I've got a lot of questions, considerations and ideas for the SharePoint Framework, just like I know many others have.

We've managed to win over Microsoft's Bill Baer and Vesa Juvonen to join us in two of our upcoming webinars, where they will talk about the SharePoint Framework.

The webinars are hosted by us at Rencore with me as a moderator, and will have Waldek Mastykarz on the panel as well to discuss and answer questions.

That's right - You've got questions about the SharePoint Framework? Join our webinars and ask them to Bill, Vesa and Waldek directly :-)

August 31st: Introduction to Development using the SharePoint Framework, with Microsoft's Bill Baer

Webinars: SharePoint Framework with Microsoft's Bill Baer and Vesa Juvonen

Join Microsoft's Senior Technical Product Manager and SharePoint MCM Bill Baer and Waldek Mastykarz, MVP at Rencore, and learn how your organization will benefit the most from the new SharePoint Framework.

From Microsoft's vision to the value this new development model holds for organizations, you will get the full story!

The webinar will also include a Q&A where you can ask Bill and Waldek your questions about SPFx.

Sign up here!

September 6th: Deep-dive into Development using the SharePoint Framework with Microsoft's Vesa Juvonen

Webinars: SharePoint Framework with Microsoft's Bill Baer and Vesa Juvonen

Join Microsoft's Senior Program Manager Vesa Juvonen and Waldek Mastykarz, MVP at Rencore, and learn what SharePoint developers can do now to prepare for a smooth transition to the SharePoint Framework.

From the new approach towards developing, to the tips and tricks that will make your life a lot easier, we cover it all!

The webinar will also include a Q&A where you can ask Vesa and Waldek your questions about SPFx.

Sign up here!

Welcome :-)


by Tobias Zimmergren via Zimmergren's thoughts on tech

Thursday, August 25, 2016

SharePoint in The Azure Cloud

So you have come to that point where it is time to either adopt SharePoint as a platform, or maybe you already have it and are now looking to upgrade. The first question becomes, where do we put it?

The whole conversation about the “Cloud” makes this very interesting, which we won’t focus on for this post. Instead we will decide that Microsoft Azure is the place to do this and start to work out how viable it is as an option. Microsoft have done a great job of trying to sell you the Azure Cloud.

read more


by via SharePoint Pro

Wednesday, August 24, 2016

Office 365 Patterns and Practices PowerShell Commands

By now you have heard about the great project that Microsoft and the Community have been working on called “Patterns and Practices”. If not, then you must have been sleeping J

read more


by via SharePoint Pro

SharePoint check if user is member of a community programmatically C#

This post explains how to check if current user is member of a SharePoint community using C #.

The first method that i know is by using 

SPGroup members = web.AssociatedMemberGroup;

and browse users list. The problem I encountered is that the member list always contains the user even if he leaves the community.After some research I understand that SharePoint does not remove the user from the list of members when the user leaves but changes the property MemberStatusInt from 1 to 2.

Below how to check whether a user is always community member

SPWeb web = siteColl.RootWeb;

//Get Community Root

foreach (SPList list in web.Lists)
{

// get members list 
    if (list.Title.Equals("Community Members"))
{

//CAML query to check if current user is following community
     SPQuery query = new SPQuery();
     query.Query = "<Where><And><Eq><FieldRef Name= \"Member\"/><Value Type=\"Integer\"><UserID />          </Value></Eq><Eq><FieldRef Name= \"MemberStatusInt\"/><Value Type=\"Integer\">1</Value></Eq> </And></Where>";
SPListItemCollection colection = list.GetItems(query);

// if colection.Count==0 => user not following comunity 

}

}

I hope that this post helps you and sorry for my English.


by Saifeddine Sibouih via Everyone's Blog Posts - SharePoint Community

Tuesday, August 23, 2016

SharePoint as a Knowledge and Ideation Platform with Mike Oryszak

In a recent webinar, I was joined by long-time community member Mike Oryszak (@next_connect) from B&R Business Solutions as we discussed the pros and cons of SharePoint as a knowledge management platform, and how idea management could be leveraged to bolster your KM efforts. Mike was a 5-time SharePoint MVP and is one of my earliest connections from the SharePoint community after I left Microsoft back in 2009, having participated with him in many SharePoint Saturday and other events around the US.

You can watch an on-demand recording of our webinar here: From Ideas to Innovation - Formalizing Idea Management in SharePoint

Following our joint webinar, I invited Mike to discuss briefly some of the concepts covered in our session. Specifically, I wanted to hear more about his deployment experiences and talk about some of his customer experiences in using SharePoint as the primary platform for capturing all internal information assets. This is more than just using the platform to store documents -- but a focused knowledge repository to help drive the "ideation" process within the company. This is an important distinction, because we have many systems that store content, but few that enable us to improve enterprise-wide visibility into this collective knowledge. SharePoint has that potential, with some planning and effort. That's what I reached out to Mike to discuss:

[Christian Buckley] Mike, I appreciate you takin the time to rehash some of the topics we just covered in our webinar. Maybe you can give folks a background on your experience and company before we start?

[Mike Oryszak] Sure, no problem. As you know, I am a Senior Solution Architect with B&R Business Solutions.  The majority of my career has been working in the Microsoft stack, initially developing with ASP, COM and then later web based .NET applications.  Like many of the longtime community members I jumped on the bandwagon early on with digital dashboards and related technologies.  I generally claim 2002 as my official start since by then I was working with Portal Server 2001 in a production capacity and developing solutions.  The organization I worked for at the time was really into pushing the concepts of platforms and code re-use so the timing was perfect to adopt what SharePoint was to become; a platform for hosting unified business solutions.   

[CB] Great, thanks for that. Ok, let's jump into it: In our webinar, we kicked things off by talking about SharePoint as a knowledge management (KM) platform. How has the KM story for SharePoint evolved since the early days (let's say the 2003/2007 versions) of SharePoint?

[MO] In some ways, it seems like everything has changed.  You can start by looking at the format of the content, and how people communicate now.  In those days everything was absolutely document based, in many cases documents that had been scanned from a printed format.  Work in progress documents would of course be in Excel or Word.  Since this was a web-based system, one of the first things I really pushed for was taking some of that content that had previously been document based and move it to a format that is more accessible, easier to consume, and easier to locate; displaying it like a web page.  Why make somebody browse to a library and open up 10 documents to find what they are looking for when you can display a page of content.  Things like employee manuals, standard operating procedures, etc. were prime candidates.  Later when features like the blogs and wikis were added, I really looked to leverage those tools.  While neither are perfect implementations of those concepts, they were an improvement over prior capabilities and helped to move people away from primarily using documents.  Wikis are inherently collaborative, and blogs I’ve always felt offered a much better flexibility than say the announcements list/web part especially since it provides better support for organizing the content with categories and tags. 

[CB] The early versions of those features were really rough. In fact, I wrote a chapter in my 2010 book about making the out-of-the-box blog features "actually" work.
 
[MO] The product has come a long way since those early days, but more importantly the way we work has continued to evolve and people’s expectations are higher than ever.  It forces us to continue to innovate and push the boundaries of what we can do.   One of the bigger issues these days is how to leverage the knowledge you do have in the system and surface it appropriately so that you can take action on it.  With that in mind, we see less browsing for content and more dynamically loaded content suggestions based on relevancy or freshness and intuitive content search interfaces that show much smaller sets of data that can be quickly and easily refined. 
 
[CB] I often tell people that the most exciting new features in Office 365 and SharePoint are the search-based features. But Microsoft is really just responding to the demands of the marketplace. Surfacing content is an important aspect of KM. In your view, what are the strengths and weaknesses of SharePoint as a knowledge repository? Where do you see most customers making mistakes in how they deploy and/or use the platform?

[MO] I think at its core, one of SharePoint’s greatest strengths has always been, and continues to be, its flexibility.  Flexibility in what features an organization chooses to use, and how that can be applied to meet a business challenge like a knowledge repository.   I like that it can support informal, unstructured repositories as well as much more formal, structure repositories where there are formal approval and publishing processes to promote or finalize items.  It supports content in a number of formats, and it has only gotten easier to find and surface the relevant content. 
 
One of the bigger weaknesses I have experienced in the past few years is lack of good support for mobile devices including both phones and tablets. 

[CB] Sounds like a great partner opportunity!

[MO] As a consultant, I am more than happy to scope out work to build a beautiful and fully responsive site that can perform well on any device but the time and effort to do that is higher than it should be.  Users expect more, and it should be easier.  I know Microsoft sees this, but I think they continue to lag 3-5 years behind.  In addition many of my customers still using the traditional server version of SharePoint still haven’t implemented the system in a way that the platform is accessible to those devices.  It is trapped behind a firewall and requires a VPN connection.  This limitation isn’t an issue with SharePoint itself, but the overall corporate security policies that should be easy to address.

[CB] Jumping over to the topic of our webinar, what would you say is the value of incorporating idea management into SharePoint? And how does that play into SharePoint's strengths?

[MO] One of the unique and great things about how SharePoint is used in most organizations, is that it is accessible by all employees.  This is certainly true for organizations that use it for an Intranet, but also for department, collaboration, or project sites.  As such, it should get the most visits or eyes on the screen.  Incorporating idea management into a system that is frequently accessed is pretty critical since it increases your chances of getting users engaged in the idea management activities.  Secondly, many of SharePoint’s core features align well with defining content areas (sites, libraries, lists) around a topical idea with flexible security and notification features.  We also have built in features that make search for and surfacing content easier than it is in most systems.  The long term value of these ideas are based your ability to find it when you need to.  With these things in mind, I haven’t seen any solution that is widely adopted and more capable than SharePoint. 
 
[CB] Looking at organizations who have successfully deployed idea management, how much would you say is the technology versus end user education?

[MO] You definitely cannot do one without the other, however most of the tough decisions are rooted in culture issues and not technology limitations.  Who should be allowed to participate and how, then what do you do with that content.  Traditionally management wanted full control over that process and who could participate.  The concept of the idea box on a shop floor became sort of a cliché and was not taken seriously.  Things have changed dramatically though in the last 10 years and employees want to have a voice and be heard.  Modern workers are willing to be engaged in the process of ideation when the organization’s culture supports it and the proper incentives are in place.  Even more important, when you have high engagement throughout the workforce, the quality of the ideas is likely to be much higher, and the ability to refine and take action on them easier.  I believe the companies that are able to successfully manage this will be significantly more successful than those that avoid, ignore, or fail to implement idea management. 

[CB] We can train people on how to use tools, but how important is company culture, do you think?
 
[MO] Each organization is in a different point on the culture maturity curve, but everyone can take a step.  For organizations that are just starting out, we start things small to get that pendulum swinging in the right direction.  It could be something like a simple poll with a small set of choices to get people into the habit of providing feedback.  Executive sponsorship is critical, and incentives always help.  Who wouldn’t be willing to write up a short list of idea contributions for the chance to win extra time off or a night at the movies?  Successful organizations tend to budget for incentives and do a good job marketing the process and results along the way.  Never underestimate the value of a good communication plan. 
 
When the culture is right you can start to fine tune the technology.  One of the keys in my experience, is making the whole process easy for both organizers and contributors.  It helps to have a solution that can support the process from start to finish; from the initial idea, promotion of the idea, refinement, and then later implementation of that idea.  If there are a lot of manual steps in the process flow, it can disrupt the flow and lead to lost momentum and delay the overall implementation of the idea.  Organizations that are successful with idea management remove those impediments.  I have also seen gamification successfully employed in a number of scenarios which can be baked into the platform.  

[CB] Ok, a related question: what SharePoint features or capabilities would you say are underutilized by customers – maybe out of the box capabilities that could help them improve their KM efforts today? Any best practices you find yourself repeatedly telling customers about?

[MO] One area I spend a lot of time educating customers on is Search.  Traditionally I think people have underutilized search, or at least have not optimized it to increase their chance of success.  There really is a lot of power and some great features that can be leveraged there that often are not.  This includes generic search results which I think everyone is familiar with, specialized search centers optimized for a particular set of content, as well as search driven content aggregation and roll-ups.  The past few years I have focused much of my community speaking to getting familiar with things like the content by search web part, custom display templates, and optimizing your search settings.  There are some incredibly powerful tools here that often go underutilized in most environments. 

[CB] From what you understand (or interpret) from Microsoft’s roadmap, what is changing about how knowledge is captured and disseminated in SharePoint? And what will be the role of partners (ISVs and SIs) in that future?

[MO] At the core of my interpretation is the thought that they are trying to simplify things for the end user, and it is hard to argue against that.  As they simplify the complexity, I believe in some cases it comes at the cost of some features that are mission critical to some organizations.  Specifically thinking about things like the modern lists and libraries, which currently have some uncertainty.  I encourage everyone to participate in the discussion through the community and through http://ift.tt/2bewNOA.
 
My approach as a consultant and SI has changed significantly in the past few years.  In the past it was always very effective to build custom server solutions, and capable developers could build and maintain those solutions with ease.  With the way things have transitioned though, I am much more selective with clients on determining what should and should not be built into SharePoint.  And for scenarios where they want to build a robust application, but really only have the requirement that it be surfaced in SharePoint we will look to build the solution in something like Azure and expose it through something like the app/add-in model.  All of the capabilities are still there, upgrades should be easier, and it comes with the added bonus that it could be ported to other platforms or used independently of SharePoint. 

[CB] What kinds of services does B&R provide to help customers build out better knowledge management capabilities?

[MO] Any successful knowledge management implementation is going to start with successful planning exercises.  We have some really smart people on the team that can help work through planning sessions.  We can use that to help identify the goals, the requirements, the types and format for content and then start to align those with out of the box or custom features.  In most cases we look to build an overall implementation roadmap that will last multiple phases.  That is not necessarily because the technology is difficult or risky, but because we want users to have time to absorb the changes and allow any culture changes to happen.  In some cases we stay fully engaged through the future phases, in others we simply come back to monitor and recommend adjustments while the bulk of the work is done internally.  We are pretty flexible with our services, and our best customers are the ones where we have a true partnership. 

Thank you again for expanding on this topic, Mike. And for those who would like to hear more on this topic, you can watch a recording of our webinar here.


by Christian Buckley via Everyone's Blog Posts - SharePoint Community