Recently, I started a journey with the PowerFX language as a Pro-Coder. The objective: to enable low-coders to author Plugin executions in PowerFX instead of with C#, finally opening up the power of event-driven logic to the broader Power Platform community.

This is Part 2 of a series of blog posts I am writing about that Journey - and it is pretty much the beating heart of the solution: A Plugin Package that includes the latest prerelease PowerFX Interpreter code so that at runtime we can grab PowerFX authored for the event, evaluate it, and commit changes to the record mid-transaction.

There is a generally simple method of detecting a mobile device where Location.Altitude > 0 || Acceleration.X > 0 being true will detect a mobile device (as opposed to a PC), but we now have "cross-over" devices with these sensors being used as office PCs - so how do we detect them? 

After learning about some of the latest advances in PowerFX from the great @MikeStall at the Power Platform conference this past September, I decided to author my own PowerFX implementation use case, and set about pondering what that should be... I eventually settled on the idea of Plugin execution context, mostly because the only PFX evaluator Open Sourced so far is the C# one, and @filcole had already beaten me to the punch with his amazing Custom API implementation!

This is the first of a series of blog posts I'll put up here on the community detailing that journey, as I have built--and continue to build--that concept and put it up on GitHub for the community to take and expand upon.

In this post (part 1) I will walk through what was the simplest part of the journey: writing a simple PCF Monaco Code Editor for PowerFX. This editor falls far short of the samples already on GitHub from the PowerFX team, but it is very Dataverse-friendly and that's why I felt this alternative needed to be authored.

DATAVERSE FORMULA COLUMNS

Formula columns are columns that display a calculated value in a Microsoft Dataverse table. Formulas use Power Fx, a powerful but human-friendly programming language. Build a formula in a Dataverse formula column the same way you would build a formula in Microsoft Excel. As you type, Intellisense suggests functions and syntax and even helps you fix errors.

CLICK HERE TO WATCH THE TUTORAIL VIEW

INTRODUCTION
This tutorial is to show how we can work with Dataverse Lookups and Choices columns within Power Automate. Many use cases require updating or creating new Lookup or Choices values when creating or updating Dataverse data records. First, we should know that the Lookup columns hold the related records' GUID values and the Choice columns hold the integer values of the Choices lists. So, when trying to update or create values in those tables, we have to keep in mind that we are working with the GUIDs and Integer values and not the actual display label or text values that appear on those columns if we are accessing the data from the editor in the Dataverse. CLICK HERE TO WATCH THE TUTORIAL

In this Blog we will see how to enable Address finder search in Canvas PowerApps.