Book Image

Microsoft 365 Fundamentals Guide

By : Gustavo Moraes, Douglas Romao
Book Image

Microsoft 365 Fundamentals Guide

By: Gustavo Moraes, Douglas Romao

Overview of this book

With its extensive set of tools and features for improving productivity and collaboration, Microsoft 365 is being widely adopted by organizations worldwide. This book will help not only developers but also business people and those working with information to discover tips and tricks for making the most of the apps in the Microsoft 365 suite. The Microsoft 365 Fundamentals Guide is a compendium of best practices and tips to leverage M365 apps for effective collaboration and productivity. You'll find all that you need to work efficiently with the apps in the Microsoft 365 family in this complete, quick-start guide that takes you through the Microsoft 365 apps that you can use for your everyday activities. You'll learn how to boost your personal productivity with Microsoft Delve, MyAnalytics, Outlook, and OneNote. To enhance your communication and collaboration with teams, this book shows you how to make the best use of Microsoft OneDrive, Whiteboard, SharePoint, and Microsoft Teams. You'll also be able to be on top of your tasks and your team's activities, automating routines, forms, and apps with Microsoft Planner, To-Do, Power Automate, Power Apps, and Microsoft Forms. By the end of this book, you'll have understood the purpose of each Microsoft 365 app, when and how to use it, and learned tips and tricks to achieve more with M365.
Table of Contents (18 chapters)

Defining naming standards

This topic is one of the most important and, alas, most neglected subjects when talking about Power App development.

Power Apps makes it easy to build, test, and publish business apps within your organization, with tons of easy functions and drag and drop components.

On the other hand, one thing that no one tells you is that it can be difficult to maintain those apps if you do not define some standards and think about the architecture.

Imagine that you have designed an app to manage your company's inventory, with more than 10 screens and lots of components inside it, 6 months ago (a few weeks as an example would fit perfectly as well), and then suddenly, you come across this:

Figure 12.18 – The controls and components of an app

What would you say – is it Button1_1 or maybe TextBox1_5? Imagine how many hours it would take you to remember the purpose of each component because you do not have it self explained...