RE2O34z_BAG_SL_4_5.mp4

One of the advantages to the deployment model that Dynamics 365 uses is the flexibility to stack things on top of each other. So, for example, if you're looking for a very specific piece of functionality, maybe you want to do chat functionality inside Dynamics 365 or maybe you're looking to do something specific to the healthcare industry, and you really want to bring in healthcare-based functionality, or maybe you're looking to leverage social media or integrate with other applications. Majority of the time, there's solutions that can be used to very easily add that functionality inside the application. So when I come into, for example, my administration center and I look at my organizations or my environments, I can see all of the specific solutions that are associated with them. So, for example, if I go ahead and I click on this "Sales Demo," I can see down here that there are specific solutions that are installed to support the functionality that I'm currently delivering as part of the application. This gives us a unique opportunity to be able to very easily leverage other functionality. So, for example, if I wanted to go ahead and maybe use an Azure Cosmos database for data source for virtual entities, I could go ahead and enable that solution inside the application. I also would have the availability if I wanted to go ahead and configure Dynamics 365 for Talent or use the community portal functionality. But all of this gives us the ability to add individual pieces of functionality based on what we want to do. Now the other thing that's nice about the solution development is oftentimes the features and functionality that you have inside the application, those are going to be updated from time to time. So the solution model also gives us the ability to come in and see what the current status of a solution is inside the application and make the determination as to whether or not we would need to update that solution to the current version. For example, "Project Service" and "Field Service," both recently underwent updates that increased the functionality capabilities of the application. So this gives us the ability to roll out solutions based upon what our specific needs are. Now this would be for items that either are currently installed or looking or have been implemented in the past. The other option that you have when you start talking about solutions is to leverage items that might already be a part of the application. This can be done through what's called "App Source." So when you go into "App Source," you have the ability to see all sorts of add-on solutions for Dynamics 365 based upon different levels of criteria. So, for example, if I was looking to go ahead and maybe do some connected field service functionality in a field service environment, I can go ahead and do a quick search for "Connected Field Service," and I would now see that there is a "Connected Field Service" icon. If I wanted to go ahead and maybe add TelephoneIntegration, I have an option here to go ahead and add "TelephoneIntegration." So what this allows us to do is to identify specific elements of the application or particular pieces of functionality, and then go ahead and implement that information based upon what our current needs might be within the application itself. So as I can see, there's a variety of authorized and preapproved vendors that already have solutions inside the application. So, for example, a lot of the functionality that you might utilize would leverage the Microsoft Dynamics 365 data export service. So if I wanted to go ahead and facilitate that, I can go ahead and hit "Get it now," and then I can fill in the registration information, and then push that information out into my environment. Some of the solutions that you'll see out here might be pay for solutions that have an intermittent trial that you can leverage. Some of the solutions maybe free solutions that you can very simply just install and deploy into your individual environments.