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.
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
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.
Last Friday, while working with one of our clients on an integration issue between Dynamics and the Microsoft Exchange global address book, he asked me if there was a way for them to have automated creation of events (calendar items) in their Microsoft Outlook calendar where the source of the data was an Excel spreadsheet in OneDrive. This is a short post, but might help someone out who needs to implement this.
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.
Since the announcement by Microsoft at the Microsoft Business Applications Summit last month, and even before, I’ve been eager to take a look at the new SQL Connection for the Common Data Service Endpoint. What this means is that we can not write and execute SQL queries against the entity data.
Creating navigation in a Power Apps portal application is straight forward, and can easily be done using Web Link Sets, but how about showing to the user where they are in the process and modifying the style of each element once the user has finished entering the data for that page. We have done this a few times and this involves the combination of liquid and JavaScript code on the different pages.
Over the past year, I played here and there with AI Builder, and particularly form processing, but have found that it was somewhat cumbersome for some of the forms that I wanted to build, especially when working a lot in the government space. Yesterday, May 4th, Microsoft announced some new changes to the AI Builder Form processing that allows recognition of undetected fields. I decided to test this out, and in order to implement this, used the IRS W-9 form, which is not such as easy form to implement.
