In this blog, we will see how to create the service connection for PowerApps Build Tools.
Pre-requisite: Azure DevOps
The service endpoint for the source and the target environment that you want to export and import the solution to. For example, https://powerappsbuildtools.crm.dynamics.com. Service endpoints can be defined under Service Connections -> Generic Service Connection in Project Settings.
Navigate to Project Settings -> Service connections -> Click on New service connection.
Select Generic in Service connection
Provide the below details for the generic service connection as follows:
Username – Username for connecting to the endpoint
In this blog, we will see how we can upload the video attachments into D365 using the Video Attachment Control – PCF Control.
The VideoAttachmentControl is used to upload any kind of video file which is of mp4 format as of now. It also lets you have a live preview of the video file uploaded and the files are stored in D365 as notes (Annotation).
Scenario – Once the field technician completes his work in the field, he can capture and upload the completed work as video. Without visiting the site inspector can play the video and review it.
Here is the reference link for the solution files and the source code.
$SolutionName – Name of the solution which you want to export the source instance.
$SolutionFilePath – Desired folder path to export the solution
$CRMSourceUserName – Username of the Dynamics 365 CE source instance
$CRMDestinationUserName – Username of the Dynamics 365 CE destination instance
$CRMDestinationPassword – Password of the Dynamics 365 CE destination instance
$CRMDestinationPassword – Password of the Dynamics 365 CE source instance
$CRMSourceUrl – URL of the Dynamics 365 CE source instance
$CRMDestinationUrl – URL of the Dynamics 365 CE destination instance.
After updating the values in the below script, you can copy and paste in Windows PowerShell and run it. This will establish the connection to the Dynamics 365 CE source instance and export the solution mentioned and import it into the Dynamics 365 CE destination instance.
In my previous blog, I wrote about how to set up a gated check-in, In this blog, we will see how to move the master data from source to target instance using our CI/CD pipeline.
Generally, we use the configuration migration tool to move the master data across multiple environments and organizations. Configuration data is used to define custom functionality in model-driven apps in Dynamics 365, such as Dynamics 365 Sales and Customer Service, and is typically stored in custom entities. Configuration data is different from end-user data (account, contacts, and so on). A typical example of configuration data is what you define in the Unified Service Desk for Dynamics 365 to configure a customized call center agent application. The Unified Service Desk entities, along with the configuration data that is stored in the entities, define an agent application.
Note: Disable plug-ins before exporting data and then re-enable them on the target system after the import is complete for all the entities or selected entities.
Define the schema of the source data to be exported: The schema file (.xml) contains information about the data that you want to export such as the entities, attributes, relationships, definition of the uniqueness of the data, and whether the plug-ins should be disabled before exporting the data.
Use the schema to export data: Use the schema file to export the data into a .zip file that contains the data and the schema of the exported data.
Import the exported data: Use the exported data (.zip file) to import into the target environment. The data import is done in multiple passes to first import the foundation data while queuing up the dependent data, and then import the dependent data in the subsequent passes to handle any data dependencies or linkages.
Instead of moving it manually we are going to automate this above process using Azure DevOps.