The Power Platform Tools for Visual Studio provide the ability to quickly create, debug and deploy plugings. There are some other capabilities that are still currently in preview, such as the deployment of custom workflow activities, web resources and other integration components.
There are various organizations that for whatever reason, whether it be trust or security are not comfortable using the Microsoft-hosted agents, and would like to use self-hosted agents within their own corporate environment.
In this article, I will go through the steps of creating a self-hosted agent, and then configuring a pipeline that will move your solution between the different environments.
In this blog post I will demonstrate how to use Azure Service Bus and a Listener application to integrate between the Common Data Service (Dynamics 365 or Power Apps Model Driven Application) and an On Premise SQL Service database.
dynamics-365-sharepoint-online-integration-webapi
The next part of this solution is to configure Microsoft Azure. If you do not have an Azure account, you can create a Trial account of Pay as you go account. If you are a partner or have a BizSpark subscription you get a certain amount of credits per month, which should be more than enough for the type of implementation that needs to be done using Azure.
The easiest part of this solution is to configure SharePoint. There is no custom development involved, but just the creation of the document library, the folders, custom lists and the attributes that we want to use for the solution. We will need to start with the creation of the custom lists as they will be used for the creation of the lookup attributes.
Over the past few years we have encountered multiple scenarios where the Out of the Box SharePoint Integration component, did not fulfill the requirements of our clients using Dynamics 365 and SharePoint. Some of these had to do with capturing additional attributes in SharePoint, and sharing similar data across different entities in SharePoint.
In a recent article I explained how to establish a connection from a Console application to Microsoft Dynamics CRM On-Premise. In this post, I will cover the same steps on how to connect a Console application to Microsoft Dynamics CRM/365 Online using the Microsoft.Xrm.Sdk and Microsoft.Xrm.Tooling.Connector namespaces
Recently I have seen a lot of posts on the CRM Community of how to establish connection to CRM using a Console application. In this post I will review the steps of establish a connection. I will focus on CRM On-Premise using ADFS/Claims/IFD, and will provide additional samples on connecting to Dynamics CRM Online in a separate blog article.
The preview version of SSDT for Visual Studio 2017 (15.3.0 preview) is now available. This release introduces a standalone web installation experience for SQL Server Database, Analysis Services, Reporting Services, and Integration Services projects in Visual Studio 2017 15.3 or later.
