Book Image

Learn Microsoft Power Apps - Second Edition

By : Matthew Weston, Elisa Bárcena Martín
4 (2)
Book Image

Learn Microsoft Power Apps - Second Edition

4 (2)
By: Matthew Weston, Elisa Bárcena Martín

Overview of this book

Microsoft Power Apps provides a modern approach to building low-code business applications for mobiles, tablets, browsers, and Microsoft Teams. The second edition of Learn Microsoft Power Apps will guide you in creating well designed and secure apps that transform old processes and workflows. Learn Microsoft Power Apps starts with an introduction to Power Apps to help you feel comfortable with the creation experience. Using screenshots from the latest UI, you will be guided through how to create an app, building your confidence to start developing further. This book will help you design, set up, and configure your first application by writing simple formulas. You'll learn about the different types of apps you can build in Power Apps and which one applies best to your requirements. In addition to this, you’ll learn how to identify the right data storage system for you, with new chapters covering how to integrate apps with SharePoint or Dataverse. As you advance, you’ll be able to use various controls, connectors, and data sources to create a powerful, interactive app. For example, this book will help you understand how Power Apps can use Microsoft Power Automate, Power BI, and Azure functionalities to improve your applications. Finally, you will be introduced to the emerging Power Apps Copilot tool, which uses artificial intelligence to accelerate the app building process. By the end of this Power Apps book, you’ll be ready to confidently develop lightweight business applications with minimal code.
Table of Contents (27 chapters)
24
Other Books You May Enjoy
25
Index
Appendix

Summary

Throughout this chapter, we have started to uncover the ability to create groups of controls that we can use time and again. These are called Components. This allows us to use the same functionality multiple times, manage it in one place, and thereby saves us time as we don’t have to create the same functionality time and again.

Our components can be created locally within an app, or if we want to share the component with a wider audience across multiple apps, then we can share them in a component library. Component libraries allow us to manage components centrally and will prompt any other makers who are using the component if any updates are available.

Our components are versatile, allowing us to define our own properties to act as an interface with the parent app. These properties can be classed as input properties, where we pass data into the component for it to be used, or can be classed as output properties where data can be returned from the component to the app...