Power Automate: Send Instant Emails From Canvas Apps

In this blog, I want to dive into Power Automate. When I first started with the Power Platform I dove deep into Power BI which then made way for Power Apps. Soon thereafter I was introduced to Power Automate. I sure wish someone had told me about Power Automate when I was a teacher of middle schoolers. There were so many mundane daily and weekly tasks that I could have easily automated if I just would have been exposed to the program.

Power Automate is great for taking those routine or repetitive tasks and making them no longer a part of your daily routine. Sure setting up the Power Automate flow takes more time to get created, but once created you then can devote all that extra time you normally would have devoted to the task and now spend them on more mission-critical issues for your job.

In this video, I want to show you how you can send an automated email with just a click of a button. Since I learned Power Automate after learning Power Apps I wanted to do my first video that married the two technologies together. That’s what the Power Platform is all about.

In my demonstration, you will see how with a click of a button, icon, or image in a Canvas Power Application I pre-defined and formatted email can be sent out. This email will be dynamic in regards to the values that populate the email. The values will come from the record I select within the application itself.

If you are new to Power Automate or don’t think you want to learn a new program, but still want to send an email directly from your Canvas application I discuss how that can be set up as well.

I have quite a few Power Automate demonstrations that I want to showcase in the future so stay tuned and subscribe to the Pragmatic Works YouTube channel to stay up to date.

If you would like to see any of my other videos in my Power Platform series you can see them here Matt's Power Platform Series

If you enjoy my series and are interested in formal training on Power BI, Power Apps, Azure, or other Microsoft products you can use my code “Matt30” at check out when purchasing our On-Demand Learning classes to get an extra 30% off - https://pragmaticworks.com/pricing/

Comments

Best Practice To Trim Before Removing Duplicates or Merging In Power Query Editor

In last week’s blog, I wrote and did a video about how to remove duplicate records and keep the most recent entry as long as a date column was part of the data source. I came across the scenario while giving training on Power BI with my company Pragmatic Works. See the video below: This week, while doing another two-day training I came across a different scenario from a follow-up conversation from day 1. I had explained how to remove duplicate records and one of the students started working on a Power BI project she has for her company. On day 2 the student informed me that her remove duplicates step was not working. I said that is odd and I asked to see the data. In one of her table visuals, I could see that it appeared that a few of the records had duplicates based on the name column. After further investigation though, we figured out the culprit. She had done all the steps correctly, but it was a data integrity issue. In her data source, the perso

Relating "Related Tables" to Baseball because I Miss Sports

I miss sports. In particular, I miss baseball. Between learning more Power BI functions and the ins-and-outs of DAX, I've turned to Netflix to fill the deep caverns left in my soul since baseball season has been postponed. And as a result, I've thought more about tigers and big cats more than I ever have in my life. I know ALL about Carol Baskins and am fully on board for a spin-off centering on locating her lost husband. I've googled "is it really legal to own a tiger in a residential area?" Without baseball in April, I am barely hanging in there (kinda like Joe Exotic's eyebrow ring). So, I am filling the sports-sized hole by using baseball stats in Power BI to demonstrate pulling data from multiple tables and consolidating it into one table. Some of the data we want to consolidate also has to have some aggregations (which is fancy for "calculations") performed on it. In this demo I will attempt to break down what is really going on

Create A Record Without A Form In Power Apps Using PATCH

In Power Apps, forms are great to use to submit data to be recorded in your data source. They do not take long to set up and the functions used to submit the data are fairly simple. This simplicity, however, can come at a cost. The cost of using a form is you don’t have a lot of design control in terms of layout and design. If you don’t like the rigid structure of forms and want more freedom, then I’ve got the fix for you. You need to become acquainted with the Patch function. The Patch function allows you to update or create a new record in your data source. The Patch function requires you to identify your data source, decide if you want to update or create a record, and then point to your controls on the app that contains the data you are submitting. The coding is a little more involved compared to SubmitForm(FormName) that you use on forms. The payoff, though, for learning a little more advanced code is you get complete design freedom for your data input controls.

The Algebra Teacher Powers to B.I.

Search This Blog