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

Don’t leave security until last

For me, the most important consideration that should be thought about is the security of the underlying data. Too many times I have seen apps created without the necessary thought about what protective measures should be applied to the data.

Is there a risk if any of the data that I’m storing can be seen by other members of the organization? Do I need to lock that data away somewhere that gives me the utmost control over what goes into it? Do I need to configure permissions for each row or record in a table? Or do I need to go lower than that and apply security to a column?

They’re all questions that you need to ask. Secure by design is a key development principle that we should all be working toward. Creating an app and then trying to shoehorn security in afterward is extremely difficult, as I guarantee you’ll need to go back and make some quite fundamental changes. Whether those changes are to the data source itself...