Skip to main content

Using Microsoft Dynamics 365 Within Microsoft Teams


In my SCRIBE Online blog, I wrote about how we can use SCRIBE Online in Microsoft Teams.  In this post I am going to talk about how we can use Microsoft Dynamics 365 in Microsoft Teams.  For those that might not be familiar with Microsoft Teams, it was released by Microsoft in 2017 to help increase communication and productivity within Teams.  The best part about Microsoft Teams is it is 100% FREE.  Click here to download Microsoft Teams.  Since it's release there have be many updates and added connectors, that increase its functionality and usability.

To leverage Microsoft Dynamics 365 within Microsoft Teams we can use either the Website Tab or the Dynamics 365 Connector.  First we will start with how to add the Website Tab.
  1. In you team, choose the channel you want to add the tab too.
  2. Click the "+" in the channel you have chosen and you will get a pop-up
  3. Click on "Website"
  4. There will be a pop-up asking to input the tab name and URL.  At this point you need to decide if you are going to have the website launch to the default landing page for  Dynamics 365 or to a specific record in  Dynamics 365.
  5. Leave the "Post to the channel about this tab" checked.  This will create a thread in the "Conversations" tab.  This way any communication around the  Dynamics 365 record can be kept in one place.
  6. Click "Save".
Now, that we know how to add Dynamics 365 in the website tab, you might be asking; "How can I get notifications if there is an update to the record in Dynamics 365 without logging into Dynamics 365?"  That is a really good question and one that the Dynamics 365 connector solves.  At the top of the Teams UI you will see the "Breadcrumbs" of where you are.  This will be the team name followed by the channel.  After the channel name you will see three dots.  See below image.


To add the connector we want, click on the three dots.  This will bring up a menu.  In the menu click on "Connectors" (If you don't see connectors, wait a few minutes as this means you just created the team and it hasn't fully setup yet.).  In the pop up, you will see a list of connectors.  To filter these, click on CRM under "CATEGORY".

Next click on configure next to Dynamics 365.  Wait a few seconds and you will see a screen that will ask you to pick the Dynamics 365 environment and then choose a record.  Once you see this, pick the Dynamics 365 instance you want to connect too.   Once Teams connects to the instance, you will see the instance URL appear.  Now we can search for the record we want in CRM, typically these will be leads, accounts or contacts.  Since almost all other records are linked to these ones in some fashion.  Once we find the record we want in the search results, click on save.  You will see a new thread start in the "Conversations" tab.  Now when any activities are updated for this record, there will be notifications within Microsoft Teams.

I hope this helps you with Microsoft Dynamics 365 within Microsoft Teams.  Stay tuned for any updates to Microsoft Teams and the Dynamics 365 connector for Microsoft Teams.

Comments

Popular posts from this blog

Dynamics 365 v9 Unit Testing and .NET Confusion

Recently while creating a plugin for Dynamics 365 v9, I ran into an issue trying to connect to CRM via the tooling connector in my unit test project.  The underlying problem was that the .NET version I was using in my unit test was 4.5.2.  This was preventing me from being able to connect to CRM to create my organization service.  I updated the .NET version on my unit test project to 4.6.1 and was then finally able to connect.  I will also add that I am using the latest nuget package version for Dynamics 365 v9.

For consistence, I updated the plugin project I was working on to .NET 4.6.1.  Locally, everything was working great.  I was able to connect to CRM and make sure that all the methods I had written did what they where suppose to do using test driven development practices.

Then when publishing my plugin via the latest version of the plugin registration tool, I received an error and could not publish my plugin.  The error was due to the .NET version of my plugin project not bein…

SCRIBE Connector Development - Handling Array List

Are you working on creating a connector with SCRIBE's CDK?  In your connector do you have an array of strings or list of  strings that you need to pass?  SCRIBE makes this easy to do within the CDK and SCRIBE Online.

I came across this scenario on a connector I was creating that passes a JSON message to an API.  In the JSON message it had a list of strings for entity ID's. Here is an easy way to accomplish this:

1) Create you Property Definition as past or your Object Definition.
1: new PropertyDefinition 2: { 3: Description = "Use TOLIST() to pass in a list of entity id's.", 4: FullName = "Entity IDs", 5: IsPrimaryKey = false, 6: MaxOccurs = 1, 7: MinOccurs = 0, 8: Name = "PublishTo", 9: Nullable = true, 10: NumericPrecision = 0, 11: NumericScale = 0, 12: PresentationType = "string", 13: PropertyType = typeof(string).Name, 14: Use…

Getting Started Connector Development

One of the benefits of working with Scribe Online is how easy they make it to create connectors if one does not exist.  In this blog post we are going to look at how to get setup, if this is the first time you have made a connector for Scribe Online.  But, before we get into that, we should first make sure that a connector doesn't already exist that can handle what we need.

We can do this by looking in the Scribe Online Marketplace.  Still not seeing what you need?  Reach out to Scribe directly or ask in the Scribe forums if a connector exists for an application.  There are instances where a connector exists but is not listed in the marketplace.  An example of this is for a client that I built a connector for.  They didn't want to setup a system to run the on-premise agent, so they asked me to set up the connector to run on Scribe's cloud agent.  This meant that I had to submit the connector to Scribe for validation.  Once published the connector is in the Scribe marketpla…