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.
For those of us who have been using Microsoft Dynamics from the early days, the only names that we ever knew for the data schema elements has been entities, fields and attributes, records, and for the different fields types where we will be seeing the changes applied option sets, picklists and two option values.
As part of the controls that are available for Model Driven apps in unified interface we have the Option Set PCF custom control. Recently I encountered a weird behavior in these controls. I am not sure whether Microsoft would consider this as a bug or a feature, but I wanted to discuss this here, so that possibly it can help other who are encountering the same issue.
In this blog post I will review the recent announcement from Microsoft Ignite, where we saw first hand Project Oakdale, or Power Apps within Microsoft Teams. The post will show you how to enable Power Apps within your teams tenant, and how to start working on your first app.
Recently, while working on a project that needed to update the Exchange rates in CDS, I was tasked at finding a solution that would be able to retrieve data from a SQL Server hosted on an Azure Virtual Machine. There were so many different approaches, and security was the main one, but I decided to do a deep dive and testing out how Power Automate will be able to accommodate these requests.
In my current role the matter of using a data lake has come up, and I wanted to get ready in case this implementation will become a need. I followed instructions from some of the published Microsoft blogs, and this blog post provides step by step instructions on how to configure the Azure Storage account to enable the Export to Data Lake feature as well as running the same process from within the Power Apps Maker Portal
For anyone who has experience with Microsoft Omni channel interface, and has enabled the 2020 Wave 2 Release Plan, there is a new app that appeared with the name Customer Service Workspace (Preview). As noted in the release plan, the multisession app allows customer service agent to multitask on several customer cases simultaneously and seamlessly switch among issues without losing context of the in-progress work.
Today, July 8, 2020, Microsoft released the Power Platform and Microsoft Dynamics 365 2020 Release Wave 2 plan documentation with a list of all the features that will be made available in the Wave 2 timeframe which starts October 2020 until March 2021. Going through all of the features is almost impossible unless you want a few hundred pages of documentation.
I have been working in the Government space for a few years now, and most implementations of the Dynamics and Azure tenants and environments are hosted in the Government Cloud. This means that there are a lot of restrictions that we have to deal with, not only from Microsoft but also from the internal IT policies.
As I was going through one of my solutions in the last few days, I noticed that there are a few changes that were made to the Solution experience, and wanted to share this with everyone. Usually we see a change appear here and there, but it seems like Microsoft is trying hard to simplify the experience and add the missing pieces that are available in classic and not yet available in the Modern experience.
