Power Platform is maturing rapidly, and users are really loving the new platform for citizen development. The only natural thing to do for Microsoft was to alter the licensing model now that they see how users are working with the platform.
Normally I am the first one to hate on all changes, but this time I am not sure I hate it. I am actually seeing some opportunities here that I didn’t see before.
I am seeing this from a Dynamics perspective, and not Office. There are 2 different ways of viewing this change.
From what I read, we can now setup a 10$ pr user pr month and create a sales app with both Model Driven and Canvas AND Portal. Within the app we are also capable to run as many flows as we want without the need for a FLOW plan.
You might still need one Enterprise or Proessional license in the bottom for the entities to be installed on the CDS, but after that you can create your own simple apps.
NB! I am sure that Microsoft will introduce some other restrictions later on to separate the apps (Sales, Customer Service etc), but currently this is not the case.
Microsoft has used words like “seamlessly” integrated when speaking about Dynamics 365 and SharePoint, and I have hated it since day one. CRM and SharePoint never seemed to get it right, and after a while I feel they just gave up. The current state of the integration is in most cases utterly useless.
The larger companies will require scalability and security. The integration has none of these in combination. The standard integration has absolutely no idea what security is, and therefore opens all documents for everyone with site access. In larger organizations they might want to separate the BU’s or even more granular access like team access in CRM. This is where you have to use 3rd party tools like Connecting Software. The second you start adding security to folders, you will hit the cap of 50k something unique permissions in a DocLib.
The smaller companies have the highest requirements in regards to simplicity. They expect it to be easy to drag/drop files, navigate a simple folder structure, merge documents from CRM that end up in the SP folder etc. In general the smaller companies are always benchmarking the CRM system against smaller collaboration solutions, and therefore expect simple usage. Again the standard isn’t enough.
Microsoft Teams, the new hope
So with the introduction of Teams + Dynamics integration, we might be somewhat closer to a solution for collaboration that could work. For the first time it makes sense to include others outside of Dynamics 365 to collaborate on the documents. A salesperson could now easily work together with others in the organization that don’t have the Dynamics license. I will show you how in a later blogpost.
Does this mean that we can use the word “seamless” in regards to integration? NOPE, but we are one step closer. My biggest concern is still that the product teams working on this seem to be forgetting to solve the simple features. When you merge a document out of Dynamics, it should be easy to put it back in to Dynamics (SP folder) where it belongs! We should need to have solutions like Documents Core Pack or Xperido for the simple templates.
Anyway. Stay tuned for the next blog when I show how cool the new integration with Teams is:)
There is something wrong with the BI content pack for Dynamics 365. It might be my setup, but this is what I have to do before demos to fix the connection problem. The issue is related to the content pack filters locked. So after completing the setup you will se an almost blank BI dataset. I haven’t figured out why, but figured out a way around.
I will go through the steps to fix the report and make it ready for demo.
If you can’t find the Dynamics tracking app in OWA you are not alone. It is simply not supported (yet). Not quite sure why. As you can see in the pictures below, I have one with the new OWA and the other with the old OWA
Don’t think this is normal, because I have not been able to reproduce the error since. I created a very simple flow on top of a few custom entities. I used both the Dynamics connector and the CDS connector while testing. When I was going to clean up my mess, I got an error when deleting.
That being said, when I tried to reproduce the flow SDK step, I was not able to. This meant that I was able to delete an entity with an active flow, and I would say that isn’t optimal either?
I tried removing the flow, but that didn’t help.
Had to add the SDK step, and then delete the step before it was ok.
I have tried reproducing the error, but not able to. Still don’t know how flow registered a plugin step in Dynamics, or why it didn’t remove it when trying to delete.