Let's Make a Power App: Round 2

In this second installment, we will start to build our app. Now, I will not just guide you click by click of building the app, but more importantly, I will do my best to explain how all the coding and features are working in the background so you can take this knowledge to design an app specific to your needs.

Below is a list of items we will be covering:

1. Setting colors for text, backgrounds, and images

2. Setting up variables do to the heavy lifting for us throughout our whole process

3. Showcase an external website https://imagecolorpicker.com/en/ that helps with color palettes that are aesthetically pleasing to your end-user

4. Insert images, shapes, and text

5. Insert galleries that reference our created data sources from our first video

The goal of these next few blogs and videos is to build an app, but not do it too quickly. I want to let the information soak in one week at a time without overwhelming anyone. If you think the videos cover too much or not enough material for one session please email me at mpeterson@pragmaticworks.com so I can modify the future sessions.

If you would like to follow along click for click it is important that you watch the session 1 video for setting up your Power Apps environment.

Session 1 Video: Power Apps Session 1

Session 2 Video: Power Apps Session 2

Enjoy and have fun!

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