Back in Tip 276 we talked about the challenges of administering CRM Online/Dynamics 365 without being a global admin. There really hasn’t been a good answer for companies that don’t want their deployment admin to be a global administrator.
The good news is this has changed with the introduction of the Dynamics 365 Service Admin role. This new Office 365 role allows you to grant users permission to administer Dynamics 365 tenants without having to be an Office 365 administrator. Users with the Dynamics 365 Service Admin role can perform the following tasks:
- Configure new instance
- Backup and restore
- Sandbox copy
- Approve email addresses
- Create and access support requests
- Access the service health
- Access message center
You can also restrict Dynamics 365 Service Admins to specific organization instances by assigning a security group for which the admin is not a member to the instances you do not want them to access. Also, Dynamics 365 Service Administrators do not consume a Dynamics 365 user license.
While this will be welcome news for many, keep in mind that you still have to be nice to your Office 365 Global Admin, as you will still need him or her to:
- Test and enable mailboxes
- Add licenses to users
- Access service settings for other Office 365 apps, like SharePoint or Exchange.
For more details see “Use the Dynamics 365 Service admin role to manage your tenant” on TechNet.
Why does my Help Button look different than someone elses?
The icon changes depending on whether you have opted in or out for Learning Path.
Don’t know how to switch in and out?
Enable Learning Path
I created two dashboards and assigned each one to a different security role. However, users without the roles assigned to the dashboards are seeing both dashboards. What’s going on?
Whenever I come across an unexplainable security test result in Dynamics 365, the first thing I do is check the teams assigned to the users in question. In most cases, the unexpected result is caused by user being a member of a team that has a security role that grants the user access to application components to which their user roles do not.
- Don’t use the same roles for team security and user security.
- Limit the team role permissions to only the privileges needed by the team.
- Consider separating the roles used by users and teams from the roles used to grant access to role based forms and dashboards–this will prevent unintentional sharing of the role based components with users and teams that should not see them.
Recently, I had experienced a significant failure with the Dynamics 365 for Tablets client. It had seemed to present itself out of the blue, without any real reasoning or trigger behind it. As we reviewed the errors presented via developer tools in Chrome while loading the tablet client in a browser, we saw a significant error related to the metadata sync.
Developer tools output from Chrome Browser when accessing Tablet app via browser
We also found when we attempted to Prepare Client Customizations for the solution, we received the following error message:
D365 cryptic error message when attempting to prepare client customizations for the mobile client
As it turns out, the mobile client metadata was corrupted due to a null reference issue in a Word template. Document templates are tied to metadata of entities and attributes, which is unfortunately not checked for nor handled via exception by D365 when metadata generation takes place. Once we removed the corrupted template, this resolved the issue.
Moral to the story: When you delete an attribute or entity, verify the commensurate changes are made to any Word or Excel Templates, else Mobile client will fail in a quite spectacular way!
– Your friendly neighborhood CRMHobbit
One of the limitations of the Dynamics 365 (and 2016) mobile app is personal charts and views shared with another user do not display in that user’s mobile app. Saved personal views and charts that I own (or that a team on which I’m a member owns) do display in the mobile app.
As a workaround, if you have personal views or charts that you want to be available on mobile for a group of people, instead of sharing the views and charts with them, create a team, add all of the people to the team, and assign the personal views and charts to the team. That will make these items available on the team members’ mobile devices. And don’t forget to add yourself to the team, otherwise you will lose access to your views and charts.
My friend Mehmet “Sputnik” Ozdemir is insane. When he asked me how to convert a long and tedious workflow into an action, instead of painstakingly reproducing it step-by-step, I told him that it’s not possible, he’s dreaming and the only sensible thing to do is to call that workflow from the newly minted action.
Did I mention he’s insane? Because he managed to come up with the instructions on how to convert a workflow into an action. Sounds too good to be true? Well, actually it does work every time in 83% of the cases. Readers digest version:
- Start with a realtime workflow. Convert an asynchronous into a realtime. Less chances of failure.
- Backup the orgs
- Create a temp solution (let’s call it: Workflow To Action Conversion)
- Add the existing Workflow that you want to convert to an action into this solution (eg: Generate Sales Metrics)
- Create an empty action in the temp solution (eg: Generate Sales Metrics Action)
- Export the solution (WorkflowToActionConversion.zip)
- Extract WorkflowToActionConversion.zip and browse to Workflow folder
- If everything has gone to plan you should have two files in here that correspond the workflow and the empty action. Open both *.xaml files into a tabbed editor (I like Notepad++)
- In the Action*.xaml file search for: <mva:VisualBasic.Settings>Assembly references and imported namespaces for internal implementation</mva:VisualBasic.Settings>
Select this line and everything below it and replace it with the same section from the Workflow*.xaml file. Save the Action*.xaml file.
- Put the Action*.xaml file back into the WorkflowToActionConversion.zip
- Import the WorkflowToActionConversion.zip
When looking at solutions available for my Dynamics 365 organization, I saw that there were two solutions available for Gamification. “Fantasy Sales Team” and “Gamification.”
So what is the difference between these solutions? Does “Gamification” include all of the functionality in Fantasy Sales Team?
Scott Durow to the rescue:
FST was essentially a preview and should no longer be used – Gamification replaces FST and is fully supported. There are some nice UI improvements but the biggest thing for me is that logins are now controlled using O365 rather than a separate username/password.
Other reasons to use the new Gamification solution:
- Total players (sum of all games): From 250 in FST to 15 Simultaneous Games with 500 players each in Gamification
- Expanded Roles: From a user being locked into a Player or Fan role to determining the role by game (e.g. Player in one game, fan in another)
- KPI Manager Role in CRM: The ability for a non-admin user (e.g. Sales Manager) to create KPIs
- Default KPIs: 10 default KPIs to get from install to first game in minutes
- Quick Setup: From install to active in minutes rather than the 24-48 delay in FST
- Enabling Public Stream in StreamTV
- Upgraded User Interface including responsive UI for mobile devices
- Single Sign On with Office 365 / Dynamics 365
- Multi Language Support
Wanted to know what’s in the latest Microsoft Portals release but were afraid to ask? Fear no more and point your browser to a kb article Portal Capabilities for Microsoft Dynamics 365 Releases.
Now we only need to pursuade the other teams like Field Services and PSA to do the same.
And I’m out of words at this point – that must be my shortest tip ever.
My production CRM Online environment was upgraded to Dynamics 365 last week, and I was very excited to use the new stacked UI on mobile. If you haven’t heard, Dynamics 365 mobile will now display multiple dashboard charts on the same screen in mobile, reducing the amount of left/right swiping users must do when viewing dashboards on mobile.
However, when I logged in the next morning after my upgrade, I still saw the old “one chart per screen” view. What gives?
Turns out that when the mobile app is connected to a CRM 2016 environment that is upgraded, the new “compact” view is disabled by default.
Here’s how to enable it:
- Click the home button to go to the start screen.
- Tap the (…) button in the lower right corner.
- Tap Settings.
- Tap “Contact View.”
- Toggle “Stacked Components” to Enable
- Click OK.
You will now enjoy a more productive, less “swipey” Dynamics mobile experience.
On the most recent episode of CRM Audio we discuss using Microsoft Flow to create a task in Wunderlist when a task is assigned to me in Dynamics 365. On the surface, this looks like an easy process. Have a flow triggered when a task is created in Dynamics, have a condition that ownerid=me, and then create the task.
After trying this and failing miserably, I knew something was missing. I tried “ownerid = Joel Lindstrom” and “ownerid = [my user id GUID in CRM]”, and neither would work.
Thanks to a helpful example from David Yack, I learned the error of my ways.
Instead of specifying the ID of the user, the follow approach will actually work.
- When a task is created.
- Add a step to get current user’s O365 profile.
- Add a step to get the CRM user record of the task owner in Dynamics
- Add a condition to compare an attribute of the user record with the same field on the O365 user profile. In this example I used primary email address.
- If they match, create your task.
Though this is a few more steps than my original failed attempt, it is actually better, as it doesn’t hard code the user name or ID.