Search Content

Sometimes, you need a quick visual or report within your Power Apps app without relying on Power BI. While Power BI is often the go-to solution for visuals, reports, and dashboards, there are scenarios where an alternative approach is preferred. In this blog post, we'll explore how to create visually appealing and interactive reports using Power Apps' HTML control, catering to specific business needs. Power Apps reporting is a must in any good maker's toolbox. Meeting the Customer's Requirements with Power Apps Reporting: Recently, we had a customer who required a concise pop-up report showcasing invoicing volume across various time horizons. The report needed automatic color-coding through conditional formatting based on period comparisons, and it had to display data for both the company as a whole and specific regions. We collaborated with the customer to develop a solution that fulfilled their needs. The App and Data: This app primarily caters to executives on the go, accessible through their mobile phones. However, the app is responsive, enabling users to view it from an iPad or a web browser. For a detailed walkthrough of the app's functionality and formulas, check out our YouTube video Build Power BI Style Reporting with Just Power Apps | Create Beautiful Reports Easily . To source the data, the customer had three data center regions, each with its own SQL Database housing key data. Initially, we attempted to perform extensive calculations within the app itself. However, to optimize performance, we transitioned to creating a SQL Server view in each region, consolidating the necessary data. This approach offloaded the computational power to SQL, reducing the load on the mobile device. Leveraging the Power Apps HTML Control: To achieve a visually appealing table design, we employed the Power Apps HTML control. This control enabled us to apply formatting for table structure, bolding, and implement the color-coded conditional logic that enhanced the report's readability. It's worth noting that while the organization already had a rich set of Power BI reports and dashboards for in-depth analysis, this Power Apps app served as a quick snapshot of the business's status. Optimizing Performance: Considering that the app is frequently accessed on the go, performance played a critical role. To enhance efficiency and avoid redundant calls and calculations, we utilized nested "With" functions in our code. The first "With" function loaded the three records, one per data center. The second "With" function executed the calculations required multiple times. For example, to color-code the "Today" amount, we summed up the total from today's data in the three regions and compared it to yesterday's total from the same regions. By performing the calculation once and reusing the results, we significantly optimized performance. Conclusion: Through a combination of HTML customization, thoughtful utilization of "With" functions, and a well-designed pop-up, our customer now has easy access to all their key business metrics at their fingertips. They can perform quick data analysis while on the go, without relying on bulky reports or dashboards. This solution has resulted in delighted executives, equipped with essential data for informed decision-making. If you need assistance in building similar solutions for your business or have any questions about the Power Platform, please check out our Services  or fill out the contact form below. We can assist you with everything from fixing one small problem to taking on full-scale projects. We even offer mentoring and Power Platform Training  if learning is your top priority. So don't hesitate to reach out and let us help you make the most of your Power Apps experience! If you prefer to learn on your own, there is a downloadable app included with this video in our YouTube training library for only $15/month!

In this video, you will learn how to update your data source like SharePoint using bulk update methods. ForAll is great but slow so instead we learn to use the JSON function to format our collection and then send it to Power Automate flow to Parse the JSON and then Apply to each. A much faster method that avoids your users from having to wait. Click the video below to get started! Click the link to view Shane Young's YouTube channel: https://www.youtube.com/c/ShaneYoungCloud Key Timestamps: 0:00 PowerApps Bulk Updates 1:18 Demo of Patch vs. Power Automate flow speed 3:00 Review what not to do and overview of the process 6:05 Create the collection to update from 7:32 Create a flow to bulk update your data source using Compose, Parse JSON, Apply to Each, and Create Item 13:20 Refresh your Power Automate flow in your Power Apps app 14:47 A couple of things to think about when using this method for Bulk Updates Additional Learning: Power Platform University Are you looking for full, personalized Power Platform training? Do you want a mentor to help guide you on your journey? Do you prefer real world content instead of academic concepts? Then Power Platform University from PowerApps911 is for you. Learn more here . If you prefer to learn on your own, there is a downloadable app included with this video in our YouTube Training Library for only $15/month!

Power Platform licensing explained so you learn all of the things you need to know plus you get a free Power Platform certification. What more could you want in a video? Power Apps Licensing explained Microsoft Power Automate Licensing explained Power BI Licensing explained Power Virtual Agents licensing explained CLICK THE VIDEO BELOW TO GET STARTED! Click here to view Shane Young's YouTube channel: https://www.youtube.com/c/ShaneYoungCloud/videos Key Timestamps: 0:00 Power Platform Licensing Guide and Certification 3:50 Power Apps Licensing Explained 9:42 Power Automate Licensing Explained 11:26 Power BI Licensing Explained 13:55 Power Virtual Agents Licensing Explained Additional Learning: Power Platform University Are you looking for full, personalized Power Platform training? Do you want a mentor to help guide you on your journey? Do you prefer real world content instead of academic concepts? Then Power Platform University from PowerApps911 is for you. Learn more here .

You like Power Apps Best practices so here is five of them all for my early builders and makers. Best practices include: The age old debate: Patch vs. Submit form What is the best data source? Building smaller apps. Is beauty really in the eye of the beholder? Choose your words carefully! Click the video below to begin! Click here to view Shane Young's YouTube channel: https://www.youtube.com/c/ShaneYoungCloud/videos Key Timestamps: 0:00 Power Apps Best Practices These tips and best practices are for makers who are just beginning their Power Apps journey. This content comes from the teachings of Power Platform University by PowerApps911. 1:45 Don't make one giant app Build multiple small apps to avoid crashing or errors within Power Apps. When you build an app that is too 'big', the maker will see an increase in time it takes to access the app. 4:41 Prefer Patch, not Forms Forms aren't flexible and don't work offline. Patch is faster and let's you have more control. 6:52 Function over form "Pretty apps that don't work are pointless." Make your apps functional, not focusing on the look only. 8:17 Don't use reserved or common words for variables or columns! Don't use common names for variables, data sources or columns to make it easier on yourself. Examples are: Date, Amount, Time, Status, Value, Activity, Data. 10:08 Dataverse is the best data source if you have a license. Dataverse is the fastest and has the most features which makes it the best data source. Although, it does require a license. If you do not have premium licenses, SharePoint is the best. Additional Learning Power Platform University Are you looking for full, personalized Power Platform training? Do you want a mentor to help guide you on your journey? Do you prefer real world content instead of academic concepts? Then Power Platform University from PowerApps911 is for you. Learn more here .

This post is for you if: • You build Power Apps or Power Automate flows that you want to move between environments or tenants • You are trying to understand the building blocks of Application Lifecycle Management (ALM) in the Power Platform • You use SharePoint as a data source, and you want to quickly change the site or list that your app or flow is connected to If you don’t like reading, then you can always watch SharePoint Environment Variables for Power Apps and Automate Solutions video on YouTube. It goes more into detail and gets all the step-by-step fun. Note: Solutions are a massive topic with many nooks and crannies. This post is focused on Power Apps Solutions built that use SharePoint Environment Variables only and in no way is exhaustive. Heck, I am exhausted just trying to write this one scenario. 😁 What are Solutions in Power Apps and Power Automate? Solutions are a way to package up your apps and flows and all the supporting pieces so that you can move them from one Environment to another. If you have intentions of making your work portable or doing ALM then you need to learn to love solutions. What can be packaged in a solution? Power Platform solutions can contain the big things like Power Apps Canvas Apps and Model-driven Apps, Power Automate cloud flows, Power Virtual Agent Chatbots, and Power Bi Dashboards and Reports. But it also lets you take along some key Dataverse pieces like Table definitions, Choices, and Security roles to name a few things. But what if you are using a different data source like ole faithful SharePoint? You cannot include your SharePoint lists but what you can do is leverage Environment Variables and Connection References. This allows you to build your app or flow to use the variable as a data source. Then when you move your app or flow to a new environment you can change where the variable points are. Boom. Now you are mapped to a different list or table without having to rework your app or flow. Very powerful stuff. So now you can build an app/flow to work with your dev copy of the SharePoint list on the dev site. Build and test as you see fit. Done? Great, now export your solution and when you import into your production environment you repoint the Environment Variables, and everything works. You can map a different site and list. What is a Managed Solution vs. an Unmanaged Solution? Long story short? Managed solutions are ones where you make all changes to your app, flow, or other Solution pieces from a dev environment. Then when you import it to another environment the pieces are available, but they are not editable. Unmanaged are the opposite. When you import the solution into another environment everything is editable. One point of confusion. You don’t set a Solutions type when you create it, only when you export it. So, your decision is not locked in, every time you export you get to choose. When should you use Power Apps Solutions? This answer will be a tad controversial. 😁 But here are some answers based on my opinion and experience. If you are building a Model-driven application, then you should always use Solutions. Solutions were originally born for Model-driven and Dataverse and they work the best in those scenarios. There is a lot of goofiness that you will trip over if you try to build them outside of Solutions actually. Do you want to build parent child power automate cloud flows? Then those have to be built in a solution, that is literally the only way the action you need is available. More details in this video on Power Automate child flows . What about Canvas apps and Cloud flows? In my opinion I am only building them in Solutions if I want them to be completely portable. So, if I was doing ALM scenarios then yes. But if you are building your apps in production and don’t plan to move them anywhere then say no thank you to Solutions. Why? Because Solutions introduce more moving parts and hoops to jump through, no reason to deal with them if you don’t plan to leverage their functionality. Controversial? Probably. Practical advice? Absolutely. Now keep in mind that my advice here isn’t forever. Microsoft continues to improve Power Platform Solutions and at some point, using them 100% of the time will probably be the norm, that norm just isn’t today. Overview of how to build a Power Apps Solution with Environment Variables Now that you have a solid understanding of what Power Platform Solutions are and when to use them let's go over at a high level how you would use them. Remember you can see the steps in action by jumping over to YouTube and using our video on Power Platform Solutions and Environment Variables . There are timestamps in the video description if you want to jump to a specific portion. Create a Solution To get started go to Make.PowerApps.com and on the left click on Solutions. Then from the top bar click on New solution. Here you can provide a Display name, select a Publisher (use the Default publisher if you are unsure), and then hit Create. After a few seconds you will have a new empty solution ready to go. Create an App in your Solution From the top bar click on New > App > Canvas app. Provide an App Name, the Format, and click Create. This will take you to the Power Apps studio you are used to. Now click on Settings, scroll down a bit, and enable Automatically create environment variables when adding data sources. Be sure then to save and refresh. Now open your app up again and add your SharePoint list as a data source when you do so it will automatically create your Environment Variables. 🙂 Very cool. Be sure to note the name of the Site and List variables that it is creating for you. Now build your app out to meet your needs. Save and close when you are done. Create a Power Automate cloud flow in your Solution From within your Solution click on New > Automation > Cloud flow > Instant flow. Give your flow a name, choose the manual trigger, and click Create. Add the SharePoint action Get items and for Site Address choose Enter a custom value from the dropdown. Now in your list of Environment Variables choose the Site environment variable you created when adding your data source to your canvas app. For List Name it is the same process; choose Enter a custom value from the dropdown but this time choose your list Environment Variable. Make any other customizations you want to your flow, Save your flow, and close so you return to your Solution. There you go, you now have an App and a flow in your Solution wired up and ready to go. Congratulations. Get ready to Export your Power Platform Solution To make importing your Solution more wizard like you will want to edit your environment variables before you export. From the Solutions Objects screen (where you see all of the apps, flows, environment variables, etc.) click on your List Environment Variable. From the property panel that opens on the right look at Current List dropdown and click the … to the right. Here select Remove from this solution and close the panel. Repeat the same steps for the Site Environment Variable. By taking these two steps it will force the Import process to prompt you to choose a new list and site. Export the Power Platform Solution On the far left click on Overview. This screen shows you all of the details about your Solution. In the top bar click on Export. Click the Next button from the property panel on the right. Choose either Managed or Unmanaged Solution and click Export. After a minute or so you will see a green bar across the top of the screen where you can click Download. This is your Solution. Importing your Power Apps Solution Now that you have created your Power Platform Solution you can import it anywhere you want. Most likely you will at a minimum want to switch to a different Power Apps Environment. Then from the left click on Solutions and from the Top Bar click on Import solution. From the right panel click on Browse to find the Solution you previously imported and click Next. The first screen will have details about the Solution click Next. Then you will be prompted to connect your Connection References, choose your SharePoint connection and click Next. Now for Environment Variables you need to select your Site and List then click Import. If you need help implementing this solution or have any questions about the Power Platform, please check out our Services  or fill out the contact form below. We can assist you with everything from fixing one small problem to taking on full-scale projects. We even offer mentoring and Power Platform Training  if learning is your top priority. So don't hesitate to reach out and let us help you make the most of your Power Apps experience! If you prefer to learn on your own, there is a downloadable app included with this video in our YouTube training library for only $15/month! Also, there is so much more to learn about Power Platform Solutions and SharePoint Environment Variables, but this guide hopefully gets you started well. Shane

Hello Power Platform enthusiasts! If you've ever found yourself knee-deep in an Excel file, wishing there was a magic button to transform it into a Power App, then today is your lucky day! Microsoft's CoPilot AI is here to make your Power App dreams come true. This revolutionary feature allows you to convert your Excel files into Power Apps with just a few clicks. Yes, you read that right - a few clicks! Now, I know what you're thinking, "Shane, this sounds too good to be true. There must be a catch!" Well, there isn't. But there is a video. In our latest tutorial on the PowerApps911 YouTube channel, we dive into the nitty-gritty of this process. We show you how to navigate the nuances, troubleshoot potential issues, and ultimately, turn your Excel file into a fully functioning Power App. So, why not take a break from reading and give the video a watch? Turn Excel into an App with Copilot Magic Back already? Great! As you saw in the video, the key to a successful conversion lies in the proper formatting of your Excel file. CoPilot AI is smart, but it's not a mind reader. It needs a well-structured Excel file to work its magic. So, before you start, make sure your data is clean, organized, and ready for transformation. Let's dive into the step-by-step process and some important things to keep in mind. Overview of creating an App from Excel using Copilot 1. Prepare Your Excel File : Before you start, make sure your Excel file is well-structured and organized. 2. Access the Feature : Navigate to Power Apps and look for the option to start with data. Here, you'll find the option to upload an Excel file. 3. Upload Your Excel File : Select the Excel file from your device that you want to transform into a Power App. 4. Create Your App : After uploading, you'll see an option to create an app. Click on it and let CoPilot AI do its thing. In a matter of seconds (or maybe a minute), your Power App will be ready. 5. Customize Your App : Once your app is created, you can customize it to your liking. Remember, this is a fully functioning Power App, so you have all the capabilities at your disposal. Important Things to Keep in Mind - No Need for Tables : Your data doesn't have to be in a table. CoPilot AI can work with ranges just as well. - First Sheet Only : CoPilot AI only looks at the first sheet of your Excel file. If you have data on other sheets that you want to include, you'll need to move it to the first sheet. - Formatting Matters : If you've formatted rows in Excel (like setting them as currency), CoPilot AI will see these as modified and include them, even if they're blank. So, be mindful of your formatting. - Don't Forget to Close Excel : A common mistake is to leave the Excel file open when trying to import it. Make sure to close it before you start the import process. - It's a Premium Feature : This feature is built on top of Dataverse, making it a premium feature. But trust me, the capabilities you'll gain are well worth it. In the grand scheme of things, this is a game-changer. It's a fast track from Excel (let's face it, not the best data source) to Dataverse (Power Apps' best data source). It's like upgrading from a bicycle to a sports car. Sure, they'll both get you where you're going, but one will get you there a lot faster and in style. So, are you ready to take your Power Platform journey to the next level? Are you excited to turn those Excel files into Power Apps? I thought so. But remember, if you hit any bumps along the way, we're here to help. Just scroll down to the Contact Us form at the bottom of this page. Whether it's this Excel-to-Power-App transformation or any other Power Platform challenge, we've got your back. Until next time, keep exploring, keep learning, and keep powering up! Shane Young, PowerApps911

Hello there, Power Apps enthusiasts! Are you looking to take your Power Apps skills to the next level? Or perhaps you're just starting out and want to learn the ropes? Either way, you're in the right place! Today, we're diving into one of the most powerful (pun intended) features of Power Apps - the Patch function. Introduction to the Patch function The Patch function is a game-changer when it comes to saving data in Power Apps. It's like the secret sauce that can transform your apps from good to great. But what exactly is the Patch function, and how can you use it effectively? Let's break it down. The Patch function allows you to create and modify records in your data source. It's a step up from forms, which can be limiting when you're looking to build more complex apps. With the Patch function, you can handle individual inputs and create new records in your data source with ease. Sounds exciting, right? But before we get ahead of ourselves, let's start with the basics. The structure of the Patch function is pretty straightforward. You start with the function name (Patch), followed by the data source you want to update, and then the changes you want to make. It's as simple as that! Here's a basic example of a Patch function Patch(Employees, Defaults(Employees), {Title: "New Employee", FirstName: "John", Age: 30}) In this example, we're creating a new record in the "Employees" data source. The new record will have the Title "New Employee", the FirstName "John", and the Age 30. Updating an existing record with Patch But here's where it gets interesting. The Patch function is incredibly versatile. You can work with different data types and fields, including text, number, date, and Boolean. This means you can customize your data saving process to suit your specific needs. For example, if you want to update an existing record, you can do so by specifying the record you want to update. Here's how you can do it: Patch(Employees, Gallery1.Selected, {Title: "Updated Employee", Age: 31}) In this example, we're updating the record currently selected in Gallery1. We're changing the Title to "Updated Employee" and the Age to 31. Patching using controls Now, let's take it a step further. Instead of hardcoding the values in our Patch function, we can use controls as inputs. This allows us to create more dynamic and interactive apps. Let's see how we can do this. Suppose we have a text input control for the employee's first name (inpFN), a text input control for the employee's age (inpAge), and a toggle control for whether the employee is good at their job (tglGood). We can use these controls as inputs in our Patch function like this: Patch(Employees, Gallery1.Selected, {Title: "Updated Employee", FirstName: inpFN.Text, Age: Value(inpAge.Text), GoodAtJob: tglGood.Value}) In this example, we're updating the record currently selected in Gallery1. We're changing the Title to "Updated Employee", the FirstName to the text in the inpFN control, the Age to the value in the inpAge control, and the GoodAtJob field to the value of the tglGood toggle. This way, you can make your apps more interactive and user-friendly. Users can input their own values, and these values will be used to update the records in the data source. It's a powerful way to save data in Power Apps and make your apps more engaging. Complete Patch walkthrough Now, I know what you're thinking. This all sounds great, but how do you actually use the Patch function in Power Apps? Well, we've got you covered. We've created a comprehensive tutorial video that walks you through the process step by step. In the video, we start with a blank app and a simple data source (a SharePoint list, in this case). We then demonstrate how to use the Patch function to create a new record and update existing ones. We also show you how to work with different data types and fields, and provide tips on troubleshooting and optimizing your Power Apps for better performance. So whether you're a Power Apps newbie or a seasoned pro, this tutorial is a must-watch. It's a great introduction to the Patch function and a valuable resource for anyone looking to enhance their Power Apps skills. Remember, saving data in Power Apps doesn't have to be complicated. With the Patch function, you can create more complex apps and manage your data more efficiently. So why wait? Dive into the world of the Patch function and start transforming your Power Apps today! Happy patching!

When it comes to building applications with Power Apps, one of the most common questions we get is, "What is the best data source for Power Apps?" After building thousands of apps and training over 10,000 people, we feel confident in providing some answers. In this blog post, we'll rank the top five data sources for Power Apps and discuss their pros and cons. 5. Microsoft Excel: The Underdog Coming in at number five is Microsoft Excel. Yes, we know Excel runs the world. If Excel disappeared tomorrow, the economy would probably stop because every business in the world relies on it. However, when it comes to building Power Apps, Excel is a less than ideal data source. While Excel is great for ideas and can serve as the foundation for building an app, it struggles with updates and read/write operations. So, while we love Excel for its versatility and ubiquity, we recommend using it for inspiration rather than as a primary data source for your Power Apps. 4. Other Data Sources: The Wild Card Power Apps supports over a thousand different data sources, from Salesforce and MySQL to AWS and Azure. These data sources are all better than using Excel as a data source, making them our number four pick. 3. SharePoint: The Popular Choice Coming in at number three is SharePoint. It's a controversial choice, we know. SharePoint is a beloved tool, and it's the most popular data source for Power Apps. However, it's not without its challenges. While SharePoint works great for smaller data sets, it struggles with performance as the data grows. It also has limitations with delegation, particularly with the search function. Additionally, SharePoint's security model can be a challenge when building Power Apps. Despite these challenges, SharePoint remains a solid choice, especially for those just starting with Power Apps. 2. SQL Server: The Speed Demon Our second pick is SQL Server, particularly Azure SQL Server as a service. SQL Server is a premium data source, meaning it requires premium licensing. However, it's incredibly fast, scalable, and offers a great security model. It's also capable of handling complex views and stored procedures. If you're already invested in SQL Server, it's a fantastic choice for your Power Apps. 1. Dataverse: The Champion Finally, our top pick for the best data source for Power Apps is Dataverse. It's the fastest, most feature-rich, and has the best security model. Plus, it's the only one that Power Platform is built on top of, which means it's the first to receive new features and updates. Licensing Considerations While Dataverse and SQL Server both require premium licensing, the benefits they offer, such as scalability and security, make them worth the investment as your Power Apps usage grows. As you start to build more apps and your needs evolve, investing in premium licensing can provide you with more features, functionality, and scalability. Choosing the Right Power Apps Data Source Choosing the right data source for your Power Apps depends on several factors, including your existing infrastructure, your team's skills, and your project's requirements. If you're just starting out, SharePoint is a good choice. If you're already invested in SQL Server, stick with it. If you're looking for the absolute best performance and features, go with Dataverse. Remember, the best data source for your Power Apps is the one that best meets your needs. If you're interested in learning more about these data sources, check out our video where we dive deeper into each one.

Are you ready to take your Power Apps skills to the next level? If so, it's time to dive deep into the concept of delegation. Understanding delegation is crucial for building efficient and high-performing applications, and this blog post is here to guide you through it. Also, remember I literally consider it IRRESPONSIBLE to build a Power Apps app without a full understanding of delegation. There are so many weird and bad things that can happen to the users of your app if you ignore this topic. Making the wrong decisions due to incomplete data Poor performance because queries are executed locally Lost or duplicated data due to viewing limits What is Delegation in Power Apps? Delegation in Power Apps is the process of retrieving data from a data source on an as-needed basis. Instead of pulling in all records at once, Power Apps retrieves records as requested, which is essential for performance and efficiency when dealing with large data sets. Connecting Power Apps to a Data Source To demonstrate how delegation works, let's connect a Power App to a SharePoint list and add a gallery to display the data. When Power Apps initially connects to the data source, it retrieves the first 100 records. As you scroll through the gallery, Power Apps retrieves more records, ensuring that data is loaded efficiently and only as needed. This is called pagination and is not configurable. Delegable vs. Non-Delegable Queries When working with data in Power Apps, it's important to understand the difference between "delegable" and "non-delegable" queries. Delegable queries are those that the data source can handle on its own, such as filtering records. Non-delegable queries are those that the data source can't handle, and Power Apps has to process them locally. An example of a non-delegable query is the 'Search' function when used against SharePoint. Power Apps provides a warning when you're using a non-delegable query with a blue underline and a yellow warning icon. However, it's important to note that Power Apps doesn't always accurately indicate when a query is non-delegable. Understanding the Data Row Limit for Power Apps Delegation The number of records Power Apps retrieves for non-delegable queries is determined by the "data row limit" setting, it defaults to 500 and can be set to a maximum of 2000. This setting is crucial for managing the performance of your Power Apps, especially when dealing with large data sets. Delegation Across Different Data Sources Delegation works differently across various data sources. For instance, some queries that are non-delegable in SharePoint become delegable in Dataverse. Understanding these differences can significantly impact the functionality and performance of your app. Avoiding Common Pitfalls with Power Apps Delegation As you navigate the world of Power Apps and delegation, be aware of common pitfalls and misconceptions. For instance, don't assume that a query is delegable because Power Apps doesn't indicate otherwise. Always test your app thoroughly to ensure it's retrieving and displaying data as expected. Conclusion Mastering delegation in Power Apps is crucial for building efficient, powerful, and responsive applications. By understanding the ins and outs of delegation, you'll be well-equipped to handle large data sets and ensure a smooth user experience. Ready to see these concepts in action? Check out our comprehensive video tutorial on mastering delegation in Power Apps Or if you are just fed up with Power Apps Delegation and need to call in the professionals we can help. Just scroll down to the Contact Us form at the bottom of this page. We have lots of ways we can help from a quick ad-hoc video call to full on project work. Happy app building!

Did you know that you can include Multiple Data Sources into the same form in your Power App? This scenario takes an existing Power App and adds additional data sources to it, specifically to use with dropdowns inside of a Form control to replace simple text input fields. You can use a technique like this if you want some consistent and/or sortable input data saved to your data source. But remember, you can have many different data sources in a single app, the nuance here is that we’re going to use those data sources inside of our Edit Form. In the video, which originally aired Feb 23, 2018, Shane Young demonstrates how to use multiple data sources with a Power App form. The goal is to create a Power App that connects to both an Excel file and a SharePoint list, providing users with drop-down menus and allowing them to add new records and edit existing ones. In the app, we will have drop-down menus for the "Department" and "Favorite Color" fields. The "Department" drop-down is populated from an Excel file, while the "Favorite Color" drop-down is fed from a SharePoint list. From our existing App, we need to add data sources. As an update to what is in the video, you can now select the Add data option from the command bar (or the Data tab from the side menu), then you can enter “excel” in the search field, and then select the Excel Online (Business) connector. Next you would “Choose a Location” where your Excel spreadsheet resides. Then find the document itself, select the table from the Excel spreadsheet, and finally connect it to your app. Doing this adds a new data connection for the Excel file. In a similar manner, we can add another data connection for the SharePoint list. Then the app has access to both data sources. Next, Shane focuses on the "Department" drop-down. As it is, it displays data from the existing data source, which is not what we want. So, we unlock the card, delete the existing control, and add a drop-down control in its place. Shane configures the drop-down to use the "Departments" table from the Excel data source. After setting it up, he runs the app to check the drop-down functionality, which works as expected, showing the different departments from his spreadsheet table. Inserting a new control into the form card causes some warnings on the screen, caused by some data card properties. Any properties of the form card referring to the deleted control will need to be updated to refer to the new control. The card’s Update property has to be changed to reflect the dropdown control such as: controlName.Selected.Value This ensures that a text value is passed back to the data source for the form. Once the card is wired to the dropdown control, the last fix is to update the Default value of the new control which needs to be based on whether it's a new form or an edit form. He does this in the Power fx entry field by using this formula: If(EditForm1.Mode = FormMode.Edit, Parent.Default, “ “) Next, Shane proceeds to add the "Favorite Color" drop-down. He unlocks the card, removes the default value, and inserts a new drop-down control. Shane sets the "Items" property to the "Colors" table from the SharePoint list data source. He also fixes a warning by specifying the correct column in his SharePoint list and uses a SortByColumns function in the Items formula to sort the colors alphabetically. Additionally, Shane addresses another issue by refreshing the data source, since the dropdown was showing some duplicates from the previous SharePoint list version. After refreshing the data source, the duplicates disappeared. It’s a reminder that when you make any changes to your data while editing your app, you need to refresh your data source to see your data source changes! The modern experience differs from the video, in that now you select the Data tab from the left-side rail and then the … (more actions) to the right of the SharePoint list and Refresh . That’ll do the trick. Finally, Shane ensures the default value for the "Favorite Color" drop-down is set correctly based on whether it's a new form or an edit form, with a similar formula, however, he uses an underscore “_” which is an item in his “Favorite Color” column. To test the app, Shane verifies that the "Department" drop-down is working correctly and displays the appropriate value for each record. He also tests the "Favorite Color" drop-down by creating a new record and verifying that it allows users to choose from a list of colors. In conclusion, Shane successfully demonstrates how to use multiple data sources with a Power App form. By connecting to an Excel file and a SharePoint list, users can access data from different sources and interact with the app seamlessly. The app provides drop-down menus for data entry, allowing users to select from various options, and enables them to add new records and edit existing ones with ease. The bonus tip provided additional insights and troubleshooting techniques for a more efficient app-building experience. PowerApps Multiple Data Sources - YouTube

User management in Power Apps can be a multifaceted task, especially when dealing with various data sources. In this guide, we'll explore four primary methods to retrieve user information in Power Apps, along with the schema of each user type, to provide a comprehensive understanding of user management. 1. The User Function The user function in Power Apps is a built-in function that returns basic information about the currently logged-in user. The schema includes: Email : The email address of the user. DisplayName : The full name of the user. Picture : The image associated with the user's profile. This function is often used to personalize the user experience within the app by displaying the user's name or picture. 2. Office 365 Users Office 365 users connection in Power Apps provides a rich set of properties related to users within your organization: DisplayName : The display name of the user. Mail : The email address of the user. JobTitle : The job title of the user. MobilePhone : The mobile phone number of the user. OfficeLocation : The office location of the user. This connection is valuable for accessing detailed user profiles and can be used in various scenarios like employee directories or organizational charts. 3. SharePoint Person Column SharePoint person columns store user or group data with a specific schema that includes: Claims : The claim associated with the user. Department : The department of the user. DisplayName : The display name of the user. Email : The email address of the user. JobTitle : The job title of the user. Picture : The picture of the user. These columns are commonly used in SharePoint lists to store information about users or groups, facilitating collaboration and content management. 4. Dataverse Users Table The Dataverse users table is a powerful feature in Power Apps, storing information about users with fields like: SystemUserId : The unique identifier for the user. PrimaryEmail : The primary email address of the user. FullName : The full name of the user. BusinessUnitId : The business unit associated with the user. Title : The title of the user. This table is essential for managing user-related data within Dataverse, supporting various functionalities like security roles and team memberships. Connecting the Dots Connecting the dots between these different methods requires a deep understanding of the schema of each user type. Email addresses are often used as the primary key to match users, but attention to details like case sensitivity is crucial. Conclusion Understanding Power Apps users and their properties is vital for building robust applications. By exploring the user function, Office 365 users, SharePoint person column, and Dataverse users table, you can gain a comprehensive understanding of user management in Power Apps. Want to see these concepts in action? Check out my video tutorial where I demonstrate these methods and provide practical examples. Become an expert in handling Power Apps users today! And if you get stuck when it comes to dealing with Power Apps Users or anything else in the Power Platform remember we are here to help. Just scroll to the bottom of the screen and use the Contact form. We are happy to help. Thanks Shane

Embarking on your Power Apps journey can be both exciting and a bit daunting. But worry not, as we have compiled a set of tips to help you navigate through the initial stages with ease. Let's dive in! Forms are Your Friend When you are first starting out with Power Apps, the key is getting results. Don’t focus on crazy scenarios or complexity; just focus on getting and working with data. To that end, the Forms control is your friend. There are really cool things you will evolve to use in Power Apps, like the Patch function and independent controls. Add a form, pick your data source, decide which fields you want to work with, and add a button to SubmitForm; just like that, you are in business. This approach allows you to quickly start working with data without getting bogged down with the complexities that can come later as you become more comfortable with Power Apps. Flow: The Double-Edged Sword As you delve deeper, you will encounter Flow, a tool that can be both a friend and a foe. While it offers a range of functionalities, it is crucial to use it judiciously. You might find tutorials encouraging you to integrate Flow for tasks as simple as sending an email, but pause and consider if it is necessary. Power Apps itself offers functionalities to perform such tasks efficiently, keeping your app environment simple and streamlined. Renaming Controls for Efficiency In your Power Apps environment, you will work with a variety of controls. A handy tip to keep your workspace organized is to rename the controls that you reference elsewhere. This not only makes your formulas more intuitive but also facilitates a smoother Power Apps experience. So, as you work through your app, take a moment to rename those essential controls to something more descriptive, saving you time in the long run. Labels: The Unsung Heroes in Troubleshooting Labels are a powerful tool in your Power Apps toolkit, especially when it comes to troubleshooting. They allow you to visualize variables, controls, and outputs, helping you to understand what is happening in your app at any given moment. For instance, if you are working with variables, using labels can help you to quickly identify what value a variable holds at a particular stage in your app. This can be a lifesaver when you are trying to debug an issue, helping you to quickly identify and resolve problems. Moreover, labels can also be used to leave yourself notes and hints, helping you to remember why you implemented a particular piece of code in a certain way. So, don't overlook the humble label; it might just be your best friend when it comes to troubleshooting your Power Apps. App Checker: Your First Line of Defense Against Errors In the top right corner of your Power Apps studio, you'll find the App Checker, a tool that should never showcase a red dot. This red dot indicates errors in your app, and it's a signal to stop and address the issues immediately. Addressing errors as soon as they appear helps in maintaining the health of your app, preventing small issues from snowballing into larger, more complex problems. Make it a habit to regularly check the App Checker and ensure that your app is error-free, setting a smooth path for your Power Apps journey. Power Apps Just Wants What It Wants Understanding that "Power Apps just wants what it wants" can be a game-changer in your development process. This fundamental lesson emphasizes that Power Apps doesn't care how you arrive at a solution, as long as you satisfy its requirements. For instance, when setting the font size in a label, Power Apps requires a number. How you derive that number, whether through a simple number input, a mathematical operation, or a function that returns a number, is up to you. The key is to satisfy the requirement of Power Apps, giving you the freedom to find solutions that are both efficient and effective. Conclusion If you are digging these ideas and want to go deeper then checkout this Power Apps Beginner Video . As you step into the vibrant world of Power Apps, keeping these tips in mind will surely steer you in the right direction. Remember, the journey of becoming a pro starts with a single step. Equip yourself with these tips and start your Power Apps journey on the right foot. Happy app building! OR if you get through this and are still feeling stuck. Then scroll down the page and fill out our Contact form. We have everything from 1on1 mentoring and training to full project services to help you out.