Michael Ghebremedin Dynamics 365 Notes

  Microsoft Power Platform Build Tools for Azure DevOps Part 2 Create a Release to Import your solution to various environments This is part II of Microsoft Power Platform Build Tool for Azure DevOps, in this article we are going to focus on how to create a release to deploy our solutions stored in our repository to various environments. Create a new release Click “ Empty Job ” Name your Stage “ Deploy To Test ” you can name your stage anything it suits you, based on your naming standards Here you have to assign the Stage Owner as well. In the following steps we are going to define: Artifacts , in our case is going to be our Git environment where we are storing our unpacked solution Stages , deployment to various environments we can create subsequent stages if one follows the other Pre-deployment conditions Post-deployment conditions Artifacts Project:- Select your Project Source(repository):- your repository ...

  I am going to write two articles 1 st one will be how to use DevOps Pipeline to Export your solution and add it to Code Repository 2 nd one will be how to Create a Release to Import your solution to various environments As a per-requisite for this article its a good idea to familiarize yourself the various parts of DevOps, you will have a more successful implementation if you have a good knowledge of what DevOps: Repos Pipeline Pipeline Environments Releases Library Task groups Deployment groups </> XAML are. For this article we are going to focus more on how to Create a Pipeline, being familiar with PowerShell Script will be helpful as well. The following documentation from Microsoft is a good reference https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tools To start with Create a Folder under your Repository, in my case I called the folder “D365_Solutions” New Pipeline Select “Use the classic ed...

We have been relying on Ribbon workbench to add or edit Buttons to Dynamics 365 and I have to admit it has been one of my favorite tool. Now we have a new tool provided by Microsoft, this is still on Preview mode, here I will be covering how to try the new functionality. To access the preview please navigate to the following URL  https://make.preview.powerapps.com/ For this sample I have created a Solution that contains a model-driven app. Select your model-driven app in Power Apps and click on the …   and Click on Edit in Preview Here you will be able to Edit your Model Driven App, navigate to the entity you would like to Add or Edit ribbon, click on the … and click on Edit Command bar (preview) Here we have the ability on which of the following we would like to edit the ribbon Main gird Main form Sub view Associated view For this exercise we will select Main form One thing to be mindful, we can not edit out of the box buttons yet, I am sure Microsoft will provide an...

  After trying Add a custom app module to the Field Service (Dynamics 365) mobile app | Microsoft Docs and failing multiple times, with error message of bad XML, I starter getting curious.  So here is my solution Create a solution and include your Model Driven App Export solution and Extract customization.xml file Locate the <AppModule> node  Add the following Xml <appsettings> <appsetting uniquename="{name of your App with prefix}_ChannelAvailability"> <value>{name of your App}</value> <iscustomizable>1</iscustomizable> <displayname default="App channel availability"> <label description="App channel availability" languagecode="1033" /> </displayname> <description default="Default Description."> <label description="Description." languagecode="1033" /> </description> <settingdefinitionid> <un...

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...

  How to deactivate Opportunity in Dynamics 365 with  Power Automate Flow   This is going to be a simple article, to deactivate an Opportunity in Dynamics 365 through power Automate Flow, you just have to create an Opportunity Close Activity record   Make sure Status and Status Reason are properly set. Opportunity = opportunities({Guid of Opportunity})  

Dynamics 365 Power Automate Flow Send Email In This Article we are going to describe a section of Power Automate Flow where we are going to create Email Message for Dynamics 365. Following this approach is going to make sure that the email message generate will be visible in our Activity Feed and the appropriate Email Message record are created in Dynamics 365 1.         Create a New Record a.        Entity Name “ Email Messages ” 2.        Set From, To, Cs and Bcc a.        You can not type email addresses on these fields b.        You are to create a reference to one of the following                                           ...