In this article, I review the required steps of building and deploying your Power Apps solution from your Development environment to your test and production environments. We will add a approval trigger from Test to Prod, Unpack the solution and publish your managed solution as an artifact so that it can be used to import to the higher environments.
A few weeks ago, I wrote a blog post about embedding a Canvas App in a Model Driven form, and compared the options of whether, in my case I should have embedded the app using the Canvas App control, or as we implemented using an iframe on the form.
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.
We have all seen different articles and posts that detail the steps of how to embed a Canvas App within a Model-Driven form by adding the Canvas App control to a field on the form, but sometimes that might not be enough for the requirements that we have in place.
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.
Recently in the forums, there were a few questions on how to send emails to all of my customers. While there might be different options, and the right solution to this might greatly depend on the frequency that you need to be sending this as well as the number of contacts, I thought I would demonstrate a few different approaches to implement this using Microsoft Power Automate.
I have started working with AI Builder recently and yesterday I finally took a look at the Business Card scanner. I decided to check how this works in the different apps, both Modal Driven as well as Canvas Apps.
I ran my tests using 4 different types of business cards and wanted to see how well this works. The results overall were pretty good, but not perfect. It is still hard to expect perfect results, as not all Business cards are created equal.
