Dynamics 365 For Operation Blog

Continuing from my previous post , in this one I’ll go through the other two steps of Power Automate(formerly known as Microsoft Flow) and Power Apps. Power Automate(formerly known as Microsoft Flow) This is a simple three-step workflow. I am using the Azure Automation connector to call the Azure Automation runbooks to start and stop the VMs. The Power App initiates the call Is an Azure Automation connector and the action is Create Job Then the status is returned to the Power App. The status is the VM power state which is either “running” or “stopped” Power App Creating the Power App is as simple you can learn more about Power Apps here . I made use of the Create an app feature on the SharePoint which basically created the app for me and I’ve made a couple of tweaks to make it work for me. These are some of the key features of the Power App that I’ve added which brings everything together: Dropdown which filters the list by Product. I have differ

I’ve been trying to figure out how I can manage my Azure VMs using PowerApps. There are probably better ways of doing this so I would like to know your ideas too. I'll take you through what I have done. There are four components to this: SharePoint – this has a list of VMs that I want to control from PowerApps   Azure automation process automation with Runbook and module galleries  – I’m using the runbook for process automation Power Automate(formerly known as Microsoft Flow)  – automate VM start and stop by integrating SharePoint and Azure Automation PowerApps – used to build Azure VM Manager This is basically what my end result looks like: I will break it down into different pieces covering each component separately. 1. SharePoint This is simply just a list of machines that are under my Azure subscription which I wish to control from my PowerApps. You can read more here  about how to create a SharePoint list. In the next step, I'm using Azure Automa

While running an MSBUILD on RetailSDK in version 10 I came across an error that didn’t make sense because I wasn’t using it at all. This particular HardwareStationSamples solution would not build in the SampleExtensions . After a little bit of research I found out that the reference was in fact a CRT project. The Assembly prefix had changed to the one I had set up in my customization settings in my BuildTools folder hence the dll name was different. I changed it back to Contoso and rebuilt the CRT solution: CommerceRuntimeSamples.sln, under RetailSdk\SampleExtensions\CommerceRuntime I ran MSBUILD once again… no errors this time around.

You will need the following information to run the PowerShell script on your development machine: - ProjectCollection: https://yoursourcecontrol.visualstudio.com/DefaultCollection - AosWebsiteName: "AOSService" - VSOAccessToken: "yourToken" - AgentPoolName: "Default" 1. Open up PowerShell in Administrator mode, change directory to C:\DynamicsSDK and run this command: .\SetupBuildAgent.ps1 -VSO_ProjectCollection https://yoursourcecontrol.visualstudio.com/DefaultCollection -AosWebsiteName "AOSService" -VSOAccessToken "yourToken" -AgentPoolName "Default" This will download the Build agent onto your development environment. 2. Now create a build definition for the project .\BuildEnvironmentReadiness.ps1 -VSO_ProjectCollection https://yoursourcecontrol.visualstudio.com/DefaultCollection -ProjectName "YourProjectName" -VSOAccessToken "yourToken" -AosWebsiteName "AOSService" Yo