Dynamics 365+ To-Do = LOVE

There are several To-Do type programs out there, and everyone seems to have their own preference to what is the best tool to use. I will argue why To-Do is the best one for Microsoft users, and why Dynamics and To-Do now makes sense.

A video of To-Do if you are not familiar with the application:

I use To-Do as a tool in my every day work with Outlook and Dynamics. For this to work it is important that you have naming convention in place when working with Dynamics 365 and tasks.


On the opportunity I add a task that has a due date. I prefer to not use the use phone call, because tasks are pretty much the same thing. In my company we don’t have a CTI integration, and we don’t report on number of phone calls.


I am using server side sync in D365, so during the next sync my task will appear in Outlook with a view over my tasks. That is fine and all, but if you are like me, the reminders in outlook is full of tasks and calendars. It is too hard to keep track.


Now if you open To-Do, you will notice that it also has the list of tasks from CRM 🙂 Because there is no integration with Dynamics lookups, I use the names to remind me what the task was regarding.

When done, I close the task, and CRM is updated with a complete task.

To-Do is available as applications on all devices, and that is why I favor this application. They are continuously adding functions, to integrate it further with all Microsoft products. They are also working on integration with Planner so we can use one app for all tasks no matter where we are!!!

The art of creating relevant demo data

If it is one thing I have learned throughout the years, it has been to produce relevant demo data. Whatever you do, NEVER use data with the name “test”. The second a potential customer doesn’t relate to your presentation, they will loose focus.

Try to understand your customer before demo, and ask them to give some names of companies and products they sell. In the beginning your demo might only bee within a group of people that actually want your product, but eventually you might have to present to the people who hate change. It takes a little more time, but can be worth it in the long run.

A sample list you could as for in regards to sales demo could be:
1. List of 2-3 sales people
2. Short list of customers
3. Customers contacts (names only)
4. List of typical products/services they sell
5. A sample report of sales activity – Only if you have the time

It might sound stupid, but you have to remember that you are the person about to introduce change to the organization. Not many people are happy about change, and therefore you need to pay attention to the small details to keep their interrest.

1-4 are fair pieces of data that you easily can enter. Nr 5 is something I would do only if you had the time. A sales report might reveal a lot of fields/categories/processes they currently use. This can have a lot of value to include in your Oppty, but it might also take to much time to configure.

This blog is a part of a series of “Demo Sales – Simple Sales“, so I will only show simple examples. The demo I will be showing is based on sample data from MS.

Power BI RLS report for Dynamics 365

RLS stands for Row Level Security and is a function within Power BI used to securely manage what the users see. I am reusing the steps from the Power BI embedding blog, and continuing with the same dataset to define RLS. Another big thanks to Jeroen Vos for teaching me PowerBI.

We start the process in Power BI for Desktop. Open the same report, and then navigate to Modeling and Manage Roles.

This brings up a DAX console, and I will chose the “Address 1: Country/Region”

Now we can test the DAX by simulating how it is with another user login. This function is something I wish we had in Dynamics!!!

Notice that the data has changed!:)
NB! Remember to publish changes to PowerBI.com

Log into https://www.powerbi.com to complete the rest of the process

Next step is to add a user to the newly created security role. Navigate to datasets and open the security.

Last step is to Share the Dashboard with the user

Open Dynamics 365 and add a new Power BI Dashboard.

The Administrator (All data)

The Sales user (Only USA)

RLS reporting in Dynamics 365, secure and supported 🙂

Dynamics 365 autonumber now available in PowerApp config

The API approach has been available for a long time, but now the autonumber is available through the config. Jonas Rapp’s autonumber solution in XrmToolbox has been absolutely one of the best tools for this purpose so far, and not we might not need it any more. I belive the first release is missing some of advanced options that Jonas has, but it might work for most of us.

This is the release information regarding the PowerPlatform autonumber: Autonumber from MS PowerApps blog

BUT why is this cool? Well, because it mentions that we can convert existing text field to Autonumber. This means that we can get rid of the stupid workflows/javascripts etc that we have made over the years to give some entities names for the name purpose:)

NB! you can only change the field to autonumber via powerapps.com. The Dynamics classic doesn’t support this. Below is the name field from a new entity. For the first time in EVER I could change the field type!!:)

Dynamics 365 force classic mode from admin panel

I know we are supposed to use the UI, but it’s not ready for all purposes yet. Therefore it is nice to know that you can force the classic view for a little while longer. If for some reason you can’t use this approach, you can also change the URL like Jamie Bowman mentions here


Open Environment and then behavior and change the variable

The result is that you now can open the Customize to classic. This doesn’t force the other UI apps to classic, so you are still all good:)