Knut is a salesperson at Point Taken. He just came across a HUGE deal that he has registered in Dynamics 365. This deal is so big that Knut will need the assistance of several resources to deliver. One of these resources is Kjetil, a SharePoint consultant.
Knut enters the details needed for the Dynamics 365 deal
Knowing that this opportunity is HUGE, Knut starts by creating a new channel in the Offers Team (name is “General” for demo purposes).
Knut has now setup the structure for collaboration, and is ready to connect Teams and Dynamics 365 together. Well done KNUT!! 🙂
Add the Dynamics 365 connection for the tab in the channel
Knut chooses the correct opportunity record.
When Knut is done, he can see the newly created connection message in Teams. The above message indicates that Teams and Dynamics successfully connected.
The harmony begins
Kjetil begins right away with the PowerPoint they will need to win this deal. Kjetil does not have a license for Dynamics, so he creates the PowerPoint in Teams because this is the natural place for collaboration.
Knut can now choose to navigate Teams or Dynamcis 365, because the systems are working with the same document location.
Knut and Kjetil represent 2 different work processes, but are harmonizing well when referring to the ONE TRUTH document. Well done you to!!!
So this part 2 of the setup is not mandatory, but will help you change some preferences and look/feel of the integration. The settings area will also give you direct access to the chat bot, and I will explain more about that later.
Open the Dynamics 365 app in Teams
In settings you choose what environment you are showing, and the app. The App has to be UI app for it to show. Because this user might not need full access via Teams, maybe you should consider making a smaller app just for Teams.
The last setup you can do is connecting the BOT to your data.
Now it is possible for the chatbot to read and work with data in Dynamics.
The configuration of the client is pretty straight forward. A typical office product, and that is a good thing:) FYI, it does not install a solution file within Dynamics, and I like that a lot… Never been a fan of the overcrowding of solution files (Hint hint portals.. hehe).
Start på opening the system settings from Dynamics and locating the “Enable Dynamics and Teams integration”.
NB! Before starting, I would create a new Team and a new channel just for the sake of simplicity. Also create a new record in CRM that you want to connect to.
It took me about 3 minutes before I received my complete message, so be patient!
Open teams and locate the App Store within teams and search Dynamics. You will find it on the “…” menu on the left side.
Add to the team you created. In my case “Tilbud” and then click Open
Next step is connecting it to the channel in the team, and hit “Set up”.
Now it will ask you for an entity to connect to, so I am going to choose the Opportunity I created before I started the configuration “Teams Opportunity”.
If it all went well, you will now see a new tab in your channel with the name of the record. You also see a message that the record is connected.
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:)
We all have different ways of demonstration the product, so I chose to create a video showing how I demonstrate in the simple sales presentations. I have only focused on the core essentials in sales during this demonstration.
There are several discussions regarding the use of CDS connector VS the Dynamics connector in the Power Platform. Recently I have been updating my knowledge a lot on PowerApps, PowerBI and Flow. The odd thing is that these environments behave quite different even thought they are so closely connected in regards to connectors.
how much longer will they co exist, and why are they even different?
So here are my thoughts about the current state April 2019 (this might be outdated in one month 😂)
Look at the Yellow columns. They show the display name of the Options Set, so no more need for hacks to convert the fetch from numbers to names. Obviously a huge benefit that this solution will update when the Option Set values update also!
PowerApps CDS vs Dynamics 2 – 1
But wait… It might not be over yet. While tampering with lookup controls for PowerApps I found out that CDS simply doesn’t have the lookup fields in the data!
CDS connector (Simply doesn’t have any lookups):
Dynamics Connector (With lookups):
Data presented is still in a GUID state, but there is a workaround for that:)