At a local Dynamics-team meeting, we had a healthy discussion about Microsoft Flow and its fit for business applications as a cross-platform workflow engine. I've been a long-time user of If This Then That (IFTTT) and I'm excited at the prospects of having this kind of service-connecting tool right here within the Microsoft toolset. It shows the embracing of Connecting the Data with 3rd party services(if you will indulge me), without having to rely on custom code 🙂
Coming out of that meeting, Britta and I wished that the discussion had been recorded. It wasn't. But we put our heads together to outline the topics that were covered and discussed them on this episode of our podcast Implement This. The content is still relevant
You can listen at the top of this post, or click through to the episode on our website.
The Dynamics 365 Workflow engine, which is the behind-the-scenes part of the process engine, is massively powerful. For host Britta Rekstad, who has presented on how to use Dynamics workflow at multiple conferences, this is an absolutely critical aspect of the platform for new admins to understand.
Co-host Matthew C. Anderson shares about how some of his early experiences in configuring Dynamics 365 involved workflow. This experience also included a spoken agreement to be careful as the workflow engine (used without care) can cause some pain for other users and admins alike.
We seem to have different perspectives on using the workflow engine, however, there’s no disagreement on how important and powerful this tool is when implementing Dynamics 365. A very flexible tool, this part of the process engine sits out-of-sight to most users but serves an important role.
Have a question you’d like answered on a future podcast? Submit one by visiting implementthis.org
Let me start by saying I have high expectations around what “good” looks like when I’m buying something. When I buy a product or subscribe to a service, I expect a good customer experience. When I am considering a purchase, I want answers to my questions. When I want support, whether that’s through chat, email, or phone, I want someone with knowledge about the product I have (the exact one I have). When I go to their website looking for accessories, I don’t want to have to sift through gobs of irrelevant options for products I don’t own.
I’m not alone with these high expectations.
In my role as a Solution Lead, I regularly talk with people who could benefit from tightening up their customers’ experiences. Customer Relationship Management systems like Dynamics 365 have evolved beyond the traditional “sales forecasting” or “account management” systems into integrated platforms that enable better experiences for customers…without ever knowing that this interaction is powered by what has been historically viewed as “just a CRM system”.
Any Dynamics 365 online or internet-facing on-premises deployment can be hooked up to a website using the API—this isn’t new and many solutions take advantage of this (simple lead capture forms come to mind). There are ISV solutions as well as pure custom development options.
Microsoft has released their Dynamics Portals solution, which is a big, exciting step.
This solution is easy to deploy with all of the plumbing done for you to provision a website. Simply start with one of several available templates:
– Customer Self-Service Portal
– Partner Portal
– Employee Self-Service Portal
– Community Portal
– Custom Portal
– Partner Project Service Portal (requires Project Service solution)
– Partner Field Service Portal (requires Field Service solution)
Dynamics portals also support interaction tracking of logged-in users. Said another way, this means that by understanding the pages that someone visits, a better user experience can be provided through intelligent suggestions or relevant content.
But there are situations where the personalization needs to go further, or fold into a larger content and engagement strategy. CRM, social, web, e-commerce, in-store, email, mobile app…it’s a big list! Where do we look to?
I connected with a few different colleagues that know the content management and delivery side of this, who could answer some of the questions I had as someone with more of a CRM background. There were three big buckets that came up:
– Advanced lead capture – going beyond a simple “form on a page” – understand the journey that started before they filled out the form
– Enhance customer experience with CRM information – Personalize the website experience based on information about your relationship that come from CRM
– Enhance CRM with customer activity – collect information about anonymous users (both prospects and customers) and connect that history as you build a relationship
In order to meet the high (and rising) expectations for customer experiences, content management tools like Sitecore are your friend, and they include ways to have a deeper connection with your customers across platforms.
There are dozens of questions that come to mind when I start considering the possibilities of what a client’s next questions would be. A few include:
– Who should drive this kind of project, and who else needs to be at the table to ensure success?
– What are some of the milestones that can help measure incremental success of this kind of integration?
– When should we start tracking information about a prospect or client’s activity or preferences, then align that across so many different channels?
– Where is the balance point for the level of detail that should be passed between Dynamics 365 and the CMS?
– Why would we choose a consolidated platform vs. building integrations between services that are already in use?
– How do we make sure that behind the technology, we provide a great client experience across these different channels?
I feel a little like I’m standing at the top of a rabbit hole, excited to see just how deep it goes. Fortunately, I have a really smart team who can help drive answers to these questions. Let us know in the comments if there are specific aspects of this you are curious about.
This post originally appeared on the RBA blog.
It’s not often that Microsoft holds a webinar where they cover so many upcoming Microsoft Dynamics 365 features that are in preview (unless it is shown under the cover of a nondisclosure agreement). But in late June, it was like Dynamics Festivus came early.
There were many exciting details shared during the June “Executive Briefing” from Microsoft…but it also left some questions.
With the upcoming release of Dynamics 365 (9.0) there will be two different flavors of Dynamics 365
(If you’re using Dynamics 365 today–July 2017–you have Enterprise Edition)
Okay, that might not seem like that big of a deal, so allow me to elaborate. The Business Edition will be released with a greatly improved user experience (called the “unified client”) for web, phone, and tablet which comes with a grip of improvements over the current experience. There are many more features that will be available for Business Edition customers when it is released.
If you’re on Enterprise Edition today, you can’t just switch to Business Edition. This means that some new features will be immediately available to Enterprise Edition clients (including notable things like the unified client.
You might not want to anyway (even if it were allowed) because there will be some limits imposed in the Business Edition. Things like a limit of the total number of Users, Account records, and custom entities (with specific details to come).
The custom entity limit is a bit misleading, though, since it appears that the entities in apps available through AppSource will not count against this total. Effectively, this message is to look for a chance to buy an app instead of rolling-your-own when it comes to meeting your requirements.
If you’re an existing Enterprise Edition client…there’s a pretty good possibility the answer is “no”. Plenty of clients may have a low number of users, but the record limits and custom entity limits will likely cut down the number of people who would even be able to consider the change. Not to mention that it would be a separate instance of Dynamics that would need to be configured and have data migrated to it.
Instead, I think most Enterprise Edition customers should look forward to getting features as they’re made available (and keep your eyes and ears open for the Private and Public Previews that Microsoft mentioned).
If you’re still considering the Dynamics platform–then the Business Edition will have a lot to offer as you get rolling (and an upgrade path to Enterprise in the future).
Are you considering Dynamics 365 Business Edition in your organization? Share what you’re most excited about in the comments!
When deploying or upgrading a relationship management system, success of the project often hinges on people actually using the system. In fact, according to the February 2016 Forrester report, CRM Success Hinges On Effective Change Management, 46% of those surveyed Agree or Strongly Agree that user adoption struggles were encountered during their CRM implementation. This is where Learning Path can help.
With Microsoft’s recent addition of Dynamics 365 release of their customer engagement capabilities (sales, service, and marketing) they have included a killer tool for providing the right help/reminders at the right time: Learning Path for Dynamics 365.
Deployments of Microsoft Dynamics 365 typically include configuration. You add fields to forms and update business process flows to support the way your company operates. These updates make the system speak your language and drive your processes—and these are exactly the things that should be reinforced inside of the system (without having to search for documents held in a different system or dig around for printout reference cards).
Dynamics 365 Learning Path provides this personalized step-by-step help. Users are literally walked through a scenario with guidance on where to click and what type of information to enter.
A key enabler is that this guidance can span multiple pages. For instance, moving through a sales process may involve work with a Lead, Opportunity, Account (etc.) and part of learning this relationship is to move between records at the right time. Learning Paths allow you to show how and when to move between records.
It’s also worth noting that once users are comfortable with using the system, they can opt-out of this guidance. This means people won’t feel “nagged” about how to use the system after they’ve become familiar with it.
Walk-through guidance on its own is helpful up to a point but sometimes you’ll need to provide additional reference material. There is a balance between the amount of content on the page and the depth that people might need.
Too much information with every step can make an otherwise simple system seem cluttered and confusing. Learning Path has a great way to handle this with an expanding sidebar where you can provide this self-service material.
– Links to other content (e.g. SharePoint content)
Training and communication are important aspects of driving effective change in an organization and Learning Paths provides ways to engage with users right inside of the application. There are plenty of uses, but here are a few examples to get the ideas flowing.
Set up walkthroughs so users can follow along during initial training (and reference them later) – This is especially helpful when users are very unfamiliar with both the system and the process. It’s also a great way to help in training where there is a high student to instructor ratio.
Use Learning Path when introducing new or updated processes – As usage of the system grows there will undoubtedly be tweaks made to the way information is displayed on the form or how the business process flow progresses. Offer new and updated Learning Paths to help support these changes.
Create role-specific content when it’s useful – Learning Paths recognizes who the individual user is, providing them the appropriate context based on their security roles. So, for example, when looking at a Contact record a sales rep and customer service rep could see different content that helps them with different processes and key information relevant to their role.
Regularly update sidebar content to include answers to frequently asked questions – the nature of learning paths makes them a great first-stop for this kind of information. Make this an easy (and in-context) place to provide answers to FAQs
Embrace the configurability and personalization of Learning Paths and iterate, iterate, iterate! Even well-planned changes will have bumps in the road—don’t look at these as static content. Consider including a link to submit questions if your current content doesn’t cover something.
This post originally appeared on the RBA blog.
One of the most effective ways to become more productive and manage your time is by automating low-value, repetitive tasks. Every week new apps are released that will connect to your online accounts and do some work for you. I’m a huge fan of this progress, however, I get concerned about these services having an unintended effect of trading some of your authenticity away just to save a little time.
There is a growing popularity of automation tools like Zapier, If This Then That (IFTTT), and Microsoft Flow, and it’s becoming easier and easier for average people to build their own personalized automations.
Even easier are tools like dlvr.it which will monitor sites and automatically post to social networks on your behalf. I’ll admit that I’ve tried dlvr.it for a couple of months and it has saved me time because I don’t need to remember a laundry list of sites that I want to further discuss on Twitter (it does the posting for me). Unfortunately, things got weird for me when people re-tweeted and responded to my tweets about articles I hadn’t actually read yet.
That crossed a line for me. As informal as social media can be, people do react to tweets, posts, and shares in a very personal way. As a result, I recently stopped using this automation and decided to find a middle ground I am comfortable with.
This made me reflect on the ways automation can impact the perception of your authenticity. As I weighed the arguments, I expected that my opinion would change if I considered it from the perspective of an individual (e.g. my personal Twitter account) vs. an organization (e.g. my company’s Twitter account). To my surprise, the answer stays pretty similar for both situations.
Every year around the holiday season I get greeting cards from friends and family. I also get them from companies that I do business with. I’m never impressed with the generic holiday greeting cards from my insurance agent. It’s a great concept, but I can see that they were printed in bulk (with a mail-merge), include a laser-printed message and signature, and were sent from another state. How many people receive this kind of card and feel warm-fuzzies?
I like my agent, and I don’t think he’s even directly responsible for the cards (it’s the parent company that sends them out). Sadly, the card that’s being sent out on his behalf actually serves as a reminder that I’m not getting a personal card/call/email to wish me happy holidays.
I get plenty of other impersonal mailings from the insurance company, ones that I don’t mind at all. Who in their right mind would expect their billing statement to have a personal touch? The non-personal, but personalized, holiday greeting card is a perfect example of the wrong kind of interaction to automate.
Take a moment and think about something as simple as an order acknowledgment email for a purchase you make online. Few people today would expect this to be personally crafted and sent by a live person. In fact, for me, and many others I know, that email should be in my inbox right away. It’s a tangible thing that makes me feel satisfied that the order I just placed is real.
However, 10-15 years ago (or maybe even less than that) most people wanted to know that there was a human being looking after their order. Why is this?
They may have changed for something like an email that confirms an order, however, the prevailing expectation I see on social media is that people expect (and believe) that posts are coming from real people hitting the Post button. Make sure your authenticity is not compromised by over-automating this kind of interaction.
Setting these expectations grows increasingly important “bots” become more mainstream. Bots (a.k.a. chatbots) are growing in their ability to handle requests for information (through a request from somebody) and automatically respond with an answer (or with a request for additional details or context).
In my experience I’ve seen bots with very wide differences in how successful they are–but little irks me more than a website offering me a live chat with an agent…but then it turns out that the agent is actually a bot.
I’d like to reiterate that I am by no means speaking ill of the services provided by dlvr.it, IFTTT, Microsoft Flow, or others. These are very exciting tools that can improve the productivity of individuals and organizations alike. There’s a line when it comes to communication, though, where automating for productivity could compromise your authenticity–and I highly encourage that you take the time to ask yourself where that balance is for you.
Do you automate communication tools like email or social media? Do you think I’m overreacting? Sound off in the comments below.
Here’s a little how-to video that helps how to use Excel to solve the otherwise monotonous process of identifying duplicate column headers in Dynamics 365 / Dynamics CRM (or in any table on a web page). This addresses the underlying issue of the Failed to Generate Excel error message that shows up when clicking Export to Excel.
Microsoft Dynamics CRM (now Dynamics 365) has a great feature that lets you export to Excel very easily to use either Excel Online or Desktop edition to play with the data.. Unfortunately, it sometimes gives a nondescript error when exporting “Failed to Generate Excel”, which appears if two column titles (fields) in the export have the exact same name.
This could be an issue if your organization has a custom field with the same name as an out-of-the-box field and both are included in the view.
Manually identifying duplicate column names is an annoying and often slow process unless the columns happen to be in alphabetical order (and they never are). It would be easy to sort in Excel though…
Note, this is something I use a lot for one-off applications–but there are better ways to do this for the same page on a frequent basis.
Now that the Excel templates for Dynamics 365 have been released and in the wild for several months, it seems an appropriate time to share some tips for getting the most out of them (even if you’re just getting started).
The following items are focused on general user experience rather than advanced Excel functionality. (Crawl. Walk. Run. We’re crawling :))
When first testing the capabilities of Excel template functionality I ran into a generic “Failed to Generate Excel” error message when downloading the baseline excel file. After some searching I discovered that the error was thrown because my view had two columns with the same name listed. With a little re-work of the view I was able to consolidate the columns listed and successfully download the file.
The easiest way to avoid this is to be intentional with which fields are added to the excel template download. I had checked the box to select “all” fields for the opportunity entity, and there were some duplicates four out of the box vs. custom fields with the same name. In a real world use case it is important to make sure that the proper field has been selected. So I recommend taking the extra time to validate specifically which fields have been added to the view (and understand why each field is being included).
By default, PivotTables are not set up to automatically refresh based on the new data in the CRM Data table, forcing you to right click on each pivot table and click refresh after opening the template. This hassle is completely avoidable and very simple to fix when setting up the excel template.
BONUS TIP: Uncheck the save data option to make sure the exported CRM data is not stored with the template you’re building.
In the examples provided by Microsoft, they have inserted their charts and tables above the data set (by adding blank rows above the CRM data table). This approach is valid and is certainly a simple way to get started, however, using additional worksheets inside of the excel workbook allows greater control over formatting and can help keep the report looking nice and clean. Using this multi sheet approach will also save you from headaches when adding in pivot tables as the number of rows and columns will be variable in many common use cases.
Doing this is simple. At the bottom of the excel window find the list of tabs (those are the sheets) and click the plus arrow to add a new one. As a best practice, remember to give good names to each sheet.
BONUS TIP: You CAN rename the tab that has the dynamic data table from CRM. Doing this doesn’t cause problems when people use the templates.
This tip is all about the user experience (even if you’re the only person who will use it :)). If you have multiple sheets there’s probably one that makes sense to have open first. There’s a very simple and low-tech way to do this:
When you save the final excel template for uploading, make sure the “landing page” worksheet is active-at-that-exact-moment-of-the-final-clicking-of-the-save-button. This worksheet will now be the one that will be active when a user opens it in Excel (via download or in Excel Online). In this way you can guide their experience to the appropriate sheet without forcing them to click another tab.
Sometimes it’s important to see all the details of the records behind your charts graphs and analysis, but other times all you need is the summary. You can help further improve the user experience by hiding the worksheet with the CRM data table.
Doing so will not cause issues when using the final uploaded template. Additionally, for users who do want to see this data they could still unhide that tab if they’re feeling curious.
The utility of the Excel Templates functionality opens doors to many quick-wins in CRM 2016 (online, cloud-hosted, or internally-hosted). These tips are a few of the basics to keep in mind when getting started, but we’ve barely scratched the surface with what we can do.
Matthew’s post originally appeared on the Hitachi Solutions blog.