PowerApps PL-900 Flashcards
Describe the business value of Power Platform services
analyze data by using Power BI
act with Power Apps
build solutions that use Microsoft Dataverse
create flows by using Power Automate
use connectors to access services and data
create powerful chatbots by using a guided, no-code graphical interface
Describe the business value of extending business solutions by using Power Platform
describe how Dynamics 365 apps can accelerate delivery of Power Platform business
solutions
describe how Power Platform business solutions can be used by Microsoft 365 apps
including Microsoft Teams
describe how Power Platform business solutions can consume Microsoft 365 services
describe how Power Platform business solutions can consume Microsoft Azure services
including Azure Cognitive Services
describe how Power Platform business solutions can consume third-party apps and
services
Describe Power Platform administration and security
describe how Power Platform implements security including awareness of Microsoft
Dataverse security roles, Azure Identity Services, and Access Management (IAM)
describe how to manage apps and users
describe environments
describe where to perform specific administrative tasks including Power Platform Admin
center, Microsoft 365 admin center
describe Data Loss Prevention (DLP) policies
describe how the platform supports privacy and accessibility guidelines
Describe Microsoft Dataverse
describe the Power Apps user experience
describe tables, columns, and relationships
describe use cases for solutions
describe use cases and limitations of business rules
describe the Common Data Model (CDM)
describe how to use common standard tables to describe people, places, and things
Describe Connectors
describe the native Dataverse connection experience
describe triggers including trigger types and where triggers are used
describe actions
describe licensing options for connectors including standard or premium tier
Identify use cases for custom connectors
Describe AI Builder
identify the business value of AI Builder
describe models including business card reader, detection model, form processing
model, and prediction model
describe how the Power Apps and Power Automate can consume AI Builder data
Identify common Power BI components
identify and describe uses for visualization controls including pie, bar, donut, and scatter
plots and KPIs
describe types of filters
describe the Power BI Desktop Reports, Data, and Model tabs
describe uses for custom visuals including charts or controls
Compare and contrast dashboards and workspaces
compare and contrast Power BI Desktop and Power BI Service
compare and contrast dashboards, workspaces, and reports
Connect to and consume data
combine multiple data sources
clean and transform data
describe and implement aggregate functions
identify available types of data sources including Microsoft Excel
describe use cases for shared datasets and template apps and how to consume each
Build a basic dashboard using Power BI
design a Power BI dashboard
design data layout and mapping
publish and share reports and dashboards
Identify common Power Apps components
describe differences between canvas apps and model-driven apps
describe portal apps
identify and describe types of reusable components including canvas component
libraries and Power Apps Component Framework (PCF) components
describe use cases for formulas
Build a basic canvas app
describe types of data sources connect to data by using connectors combine multiple data sources use controls to design the user experience describe the customer journey publish and share an app
Describe Power Apps portals
create a portal by using a template
describe common portal customizations
identify differences in portal behavior based on whether a user is authenticated
apply a theme to a portal
Build a basic model-driven app
add tables to app navigation
modify forms and views
publish and share an app
Identify common Power Automate components
identify flow types
describe use cases for flows and available flow templates
describe how Power Automate uses connectors
describe loops and conditions including switch, do until, and apply to each
describe expressions
describe approvals
Build a basic flow
create a flow by using the button, automated, or scheduled flow template
modify a flow
use flow controls to perform data operations
run a flow
modify a flow
Describe Power Virtual Agents capabilities
describe use cases for Power Virtual Agents
describe where you can publish chatbots
describe topics, entities and actions
describe message nodes, question nodes, conditions, trigger phrases, and the authoring
canvas
identify common pre-built entities
Build and publish a basic chatbot
create a chatbot create a topic call an action test a chatbot publish a chatbot monitor chatbot usage monitor chatbot performance
Components of Power Platform
Power Apps helps you build and deploy customized apps that work across web and mobile, embedded or standalone, on any device.
Power Automate lets users create automated workflows between applications and services. It helps automate repetitive business processes such as communication, data collections, and decision approvals.
Power BI (Business Intelligence) is a business analytics service that delivers insights for analyzing data. It can share those insights through data visualizations which make up reports and dashboards to enable fast, informed decisions. Power BI scales across an organization, and it has built-in governance and security allowing businesses to focus on using data more than managing it. Power BI helps you analyze and visualize data on a unified platform with data from internal and external sources.
Power Virtual Agents enables anyone to create powerful chatbots using a guided, no-code graphical interface, without the need for data scientists or developers.
Power Platform features
AI Builder lets users and developers add AI capabilities to the workflows and Power Apps they create and use.
Microsoft Dataverse is a scalable data service and app platform which lets users securely store and manage data from multiple sources and integrate that data in business applications using a common data model to ensure ease and consistency to users.
Connectors enable you to connect apps, data, and devices in the cloud. Consider connectors the bridge across which information and commands travel.
Data connectors
Data Sources - Tabular data - A tabular data source is one that returns data in a structured table format (SQL, SP). Function-based data - A function-based data source is one that uses functions to interact with the data source(Azure blob).
Connectors - the bridges from your data source to your app, workflow, or dashboard. (free and premium)
Triggers and Actions. Triggers are only used in Power Automate and prompt a flow to begin, Actions are used in Power Automate and Power Apps. Actions are prompted by the user or a trigger and allow interaction with your data source by some function.
build a custom connector.
Custom Connectors build a custom connector. This will allow you to extend your app by calling a publicly available APIA(application programming interface). Blank, open API, Postman
Data Loss Prevention - Policies
Data loss prevention (DLP) policies that can act as guardrails to help prevent users from unintentionally exposing organizational data. DLP policies can be scoped at the environment level or tenant level, offering flexibility to craft sensible policies that strike the right balance between protection and productivity. Business, non-business, blocked.
Data Loss prevention - Data privacy
Data as it is in transit between user devices and the Microsoft datacenters are secured. Connections established between customers and Microsoft datacenters are encrypted, and all public endpoints are secured using industry-standard TLS.
Data loss - Accessibility
One of the things that Microsoft values the most is making sure that Power Platform is accessible and inclusive to all kinds of users all over the world. An accessible canvas app will allow users with vision, hearing, and other impairments to successfully use the app.
Microsoft Power Platform
Microsoft Power Platform is a system that enables users to do three key actions on data that help them drive business: gain insights from data (Analyze), drive intelligent business processes via apps they build (Act), and automate business processes (Automate).
Microsoft Dataverse
API - cloud-based solution that easily structures a variety of data and business logic to support interconnected applications and processes in a secure and compliant manner. Managed and maintained by Microsoft, Dataverse is available globally but deployed geographically to comply with your potential data residency.
It powers Microsoft Dynamics 365 solutions
Microsoft Dataverse features
Security: Dataverse handles authentication with Azure Active Directory (Azure AD) to allow for conditional access and multi-factor authentication. It supports authorization down to the row and column level and provides rich auditing capabilities.
Logic: Dataverse allows you to easily apply business logic at the data level. Regardless of how a user is interacting with the data, the same rules apply. These rules could be related to duplicate detection, business rules, workflows, or more.
Data: Dataverse offers you the control to shape your data, allowing you to discover, model, validate, and report on your data. This control ensures your data looks the way you want regardless of how it is used.
Storage: Dataverse stores your physical data in the Azure cloud. This cloud-based storage removes the burden of worrying about where your data lives or how it scales. These concerns are all handled for you.
Integration: Dataverse connects in different ways to support your business needs. APIs, webhooks, eventing, and data exports give you flexibility to get data in and out.
MS Dataverse DB
Single instance of Microsoft Dataverse which stores data in a set of standard and custom data structures called tables.
Many can be created, 4 terabytes of data can be held.
Standard v Complex
Common data model (dataverse)
Common Data Model is a logical design that includes a set of open-sourced, standardized, extensible data tables and relationships
Relationships (dataverse)
Combing several tables in logical manner through unifying id
Environments in Dataverse
Environments are used to store, manage, and share your organization’s business data, apps.
Each environment is created under a Microsoft Azure Active Directory (Azure AD) tenant, and its resources can only be accessed by users within that tenant.
Busines rules (dataverse)
usiness rules allow you to apply and maintain business logic at the data layer instead of the app laye
Powerful way to enforce rules, set values, or validate data
Dataverse Admin
Settings that you will need are available in the Microsoft Power Platform admin center.
We can set - environments, data policies, data integration, Tenant
PowerApps - Description
Power Apps is used to build apps that allow you to take action on your data. Power Apps is great for replacing paper forms, legacy solutions, or just that spreadsheet that you and a few coworkers pass around. Power Apps offers advanced functionality and the ability for seasoned developers to design complex applications with ease.
PowerApps types
Canvas - Canvas apps are a great option when you want to build an app from a blank canvas. You start by choosing the screen size: tablet or mobile, then you have a blank screen from which to build. You can interact with data in your app by adding data sources.
Model driven - Model-driven apps build from data in Microsoft Dataverse. Power Apps will build you a great looking, fully functional app to act upon and interact with this data. With model-driven apps, there is no need to worry about choosing the app size; it is responsive, meaning it works on mobile or tablet with no extra work by you.
Portals - bring the power of no-code solutions to building externally facing websites. Through the Power Apps interface, you can build an anonymous or authenticated website that allows users to interact with data held in Dataverse.
PowerApps ML
Power Apps has “democratized” artificial intelligence by providing a wizard-based interface for building and training your model. This unlocks the power of Azure Machine Learning and Cognitive services without writing a single line of code or creating complex machine learning models.
Model types
Prediction - This model predicts whether something will happen or not based on previous data history. More details in the following section.
Form processor - This model extracts text from an image like the business card reader.
Object detector - This model identifies objects from an uploaded image or taken photo and then provides a count of the number of objects present.
Text classification - This model categorizes text by its meaning, making it is easier to analyze.
PowerApps security
To manage security for Power Apps, you can access https://admin.powerplatform.microsoft.com/. Here you will find options for creating and managing environments, monitoring licenses, working with Data Loss Prevention policies and managing Dataverse Data Integration projects. This allows you to manage the Power Apps throughout your tenant from one single place.
Power Apps also has its own set of PowerShell cmdlets for app creators, administrators, and developers that allow you to automate many of your administrative duties. A common use case of the PowerShell cmdlets is to automate the discovery and permission management of all apps in your tenant, allowing you to better understand and manage apps as they are created and spread throughout your company.
In addition, in the Power Automate learn module, you will see that Power Automate has the ability to automate these tasks. You can download the Center of Excellence starter kit, a collection of components or tools that are designed to help get started with developing a strategy for adopting and supporting Microsoft Power Platform, with a focus on Power Apps and Power Automate.
PowerApps key take aways
- Power Apps is a no-code/low-code platform that allows you to build apps with your business knowledge and existing skills.
- Power Apps has different offerings to meet your needs. Canvas apps, Model-driven apps, and Portals each have their own unique properties.
- Power Apps helps you build and deploy customized apps that work across web and mobile, embedded or standalone, on any device.
- You can build apps that follow your business processes instead of making your business process follow the software.
PowerApps creator journey
- Identify a business need that could be filled by Power Apps.
- Connect to any necessary data in your Power Apps.
- Design the app using controls, buttons, and an easy to use interface for your end user to interact with the data to accomplish the business need.
- Save and publish the app and test functionality.
- Once satisfied, share the app with end users to give them a better business process
Power Apps functions
Filter - This function is often used with galleries or tables of data to narrow down the rows returned from your data source. You do this by specifying one or more columns in your data set to perform a logic test on, which will allow you to return data that falls in a certain date range, has a set value, or was created by the user for example.
Match - This function allows you to check a value to see if it follows a given pattern. You can use this to check if the user entered a properly formatted email address and, if they did not, show them a warning that a valid email is required. This function serves well for conditional formatting.
Distinct - This function allows you to return the unique values from a list of data, making it easier to build dynamic dropdowns that show users only the valid values for the given column.
Math functions - Power Apps includes a range of math formulas for working with your data from the simple such as Sum or Average to the complex such as Atan and Sin to work with radians.
This is a small sampling of the large library of Power Apps functions that are available.
Power Apps model driven
Model-driven applications use a metadata-driven architecture.
Model-driven app design is an approach that focuses on adding dashboards, forms, views, and charts to your apps. With little or no code, you can build apps that are simple or very complex.
Model-driven app design is a component-focused approach to app development.
Power Apps model driven design steps
- Model your business data
- Define your business processes
- Build the app
With model-driven apps, the name says it all. Your primary design goal is to get your Microsoft Dataverse data model in order. With that in place, you can connect Power Apps, and a model-driven app will be created for you from that model.
Power Apps - Model Driven - Data
table - dataset of columns
column - column defines data type in the column
relationship - Relationships define how tables can be related to each other
choice - column filtering option with preset values (number:value)
As you begin the data modeling process, there are a couple of important questions to ask yourself:
- What type of data will your solution be storing and or collecting?
- How will this data relate or coincide with the other data you are working with?
Power Apps - Model Driven - User interface
Apps - determine the app fundamentals, like components, properties, the client type, and the URL.
A site map - specifies the navigation for your app.
Forms - include a set of data entry columns for a given table. A form can be used to create or edit an existing data row.
Views - define how a list of rows for a specific table appears in your app. A view defines the columns shown, the width of each column, the sorting behavior, and the default filters.
Power Apps - Model Driven - Logic
The logic components determine what business processes, rules, and automation the app will have.
Business process flow designer - walk users through a standard business process. Use a business process flow if you want everyone to handle customer service requests the same way. Or you can use a business process flow to require staff to gain approval for an invoice before submitting an order. They provide visuals on next steps based on the status of the data and facilitate other actions that you want to occur as the user uses the app. Business Process Flows let you bring automation to your app and make it more of a guided experience than just a place to enter data.
Workflow designer - automate business processes without a user interface. Designers use workflows to initiate automation that does not require any user interaction.
Process designer - create actions that are a type of process that lets you manually invoke behaviors, including custom actions, directly from a workflow.
Business rule designer - applies rules or recommendation logic to a form to set field requirements, hide or show fields, validate data, and more. App designers use a simple interface to implement and maintain fast-changing and commonly used rules. Define behaviors at the data layer. This is great for setting conditions for when a field is required, setting a default value, or even showing or hiding a field based on criteria.
Flows - Power Automate is a cloud-based service that lets you create automated workflows between apps and services to get notifications, sync files, collect data, and more.
Metadata
Data about data
Power Apps - Model Driven - Visualization
Chart designer - Charts are individual graphical visualizations that can appear in a view or a form or that can be added to a dashboard.
Dashboard designer - Dashboards show one or more graphical visualizations in one place that provide an overview of actionable business data.
Power BI - Power BI adds embedded Power BI tiles and dashboards to your app. Power BI is a cloud-based service that provides business intelligence (BI) insight.
Power Apps - security roles
The Power Apps environment includes predefined security roles. These roles reflect common user tasks, and the access levels that are defined follow the security best practice of providing access to the minimum amount of business data that is required to use the app.
Environment Maker - None - Users who have this role can create new resources that are associated with an environment, including apps, connections, custom application programming interfaces (APIs), gateways, and flows that use Power Automate. But these users can’t access the data in an environment. To learn more about environments, see Announcing Power Apps environments.
System Administrator - Create, Read, Write, Delete, Customize- This role has full permission to customize or administer the environment, including creating, changing, and assigning security roles. User who have this role can view all data in the environment. To learn more, see Privileges required for customization.
System Customizer - Create (self), Read (self), Write (self), Delete (self), Customizations - This role has full permission to customize the environment. But users who have this role can view rows only for environment tables that they create. To learn more, see Privileges required for customization.
Microsoft Dataverse User- Read, Create (self), write (self), delete (self) - Users who have this role can run an app in the environment and perform common tasks for the rows they own.
Delegate - Act on behalf of another user - This role lets code run as or impersonate another user. This role is typically used with another security role to provide access to rows. To learn more, see Impersonate another user.
Power Apps - Share model app
- Define security roles
- Associate security roles
- Share app with the defined role
Power Apps - Portals
Power Apps portals are built on top of Microsoft Dataverse.
Power Apps portals give internal and external users secure access to your data either anonymously or through commercial authentication providers like LinkedIn, Microsoft, Facebook, and Google, or enterprise providers such as Azure AD B2C and Okta. Portals also allow you to set authentication requirements, customize data for each user, and allow users to submit their information privately with straightforward admin controls.
Portals provde with a branded, personalized, self-service experience. Portals help you provide an organized, searchable knowledge base to deliver consistent, up-to-date answers and community experience for peer-to-peer support and direct interaction with your subject matter experts
Power Portal - template types for MS Dynamic
Community - Partner, Customer - Choose this option to provision a portal that is focused on an online community. This portal will contain features such as forums, ideas, blogs, and case management.
Customer self-service - Partner, Customer - This option provides the ability for portal users to search knowledge articles, submit cases, and participate in discussion forums to resolve issues.
Employee self-service - Employee - This portal allows employees to access a centralized knowledge article and to also submit cases.
Partner - Partner - Choose this option to build a portal where external partners can manage and collaborate on accounts and opportunities. Add-ons are available for Dynamics 365 Field Service or Dynamics 365 Project Service.
Customer portal - Enterprise B2B - The Dynamics 365 Supply Chain Management Customer portal is a template that provides portal access to Dynamics 365 Supply Chain Management data by using dual-write Microsoft Dataverse tables.
Portal from blank - Other - The Portal from blank option is meant for unique line-of-business scenarios where the other templates are not a good fit. The portal can be configured to address a variety of requirements. If Portal from blank is provisioned within a Microsoft Dataverse environment, specific features from the other portals can be incorporated into the portal later.
Power Apps - Portal - security
Users of Power Apps portals are tracked in Microsoft Dataverse as contacts.
Authentication - local/external
After the user is authenticated and associated with a contact, Power Apps portals use numerous tables to define authorization, that is, what a user is allowed to do.
Web roles allow an administrator to control user access to portal content and Microsoft Dataverse rows.
A web role can be associated with the following table rows:
- Website permissions - Define what (if any) front-side editing permissions that a web role should have.
- Webpage access rules - Define what pages are visible to a web role and what actions can be taken.
- Table permissions - Define what access a web role has to individual Microsoft Dataverse tables.
Power Apps - Portal - Components
Page template row that defines the layout and the behavior
Content snippets are reusable fragments of editable content that can be placed within a web template. Using snippets allows for targeted editing of parts of a page without affecting the overall content.
Table lists and table forms are used in Power Apps portals to define what data should render on the portal from Microsoft Dataverse
Power Automate
Power Automate is used to automate repetitive business processes. Beyond simple workflows, Power Automate can send reminders on past due tasks, move business data between systems on a schedule, talk to more than 275 data sources or any publicly available API.
Custom API are built using swagger file.
Common scenarios and capabilities of Power Automate
- Automating of repetitive tasks like moving data from one system to another
- Guiding a user through a process so they can complete the different stages
- Connecting to external data sources via one of the hundreds of connectors or directly via an API
- Automating desktop based processes with robotic process automation (RPA) capabilities
Power Automate - flow type
Event driven flows - These are flows that you build with a trigger and then one or more actions. There are a multitude of triggers and actions available, thanks to the existing connectors. You will see these as My flows and Team flows in Power Automate. The only difference between a My flow and a Team flow is ownership. With a My flow you are the sole owner, while a Team flow has more than one owner.
Business process flows - These flows are built to augment the experience when using Model-driven apps and Microsoft Dataverse. Use these to create a guided experience in your Model-driven apps.
Desktop flows - These robotic process automation (RPA) flows allow you to record yourself performing actions on your desktop or within a web browser. You can then trigger a flow to perform that process for you. You can also pass data in or get data out of the process, letting you automate even “manual” business processes.
Power Automate - flow parts / Trigger
Every flow has two main parts: a trigger, and one or more actions.
You can think of the trigger as the starting action for the flow. The trigger can be something like a new email arriving in your inbox or a new item being added to a SharePoint list.
- On schedule
- On change
- On button press
Power Automate - Flow Actions
Actions are what you want to happen when a trigger is invoked. For example, the new email trigger will start the action of creating a new file on OneDrive for Business. Other examples of actions include sending an email, posting a tweet, and starting an approval.
Some examples of types of actions you can have in a flow include:
Loops – Runs an action until conditions are met to move to the next step of the flow
Switch – Identifies a single case to execute based on the evaluation of input
Do Until – Executes a block of actions until a specified condition evaluates to true
Apply to each – Executes a block of actions for each item in the input array
Expressions – underlying definition that describes the actual logic that runs in your flow that can be manually writte
PowerBI - concepts
The major building blocks of Power BI are: datasets, reports, and dashboards. They are all organized into workspaces, and they are created on capacities.
Power BI - capacities
Capacities are a core Power BI concept representing a set of resources used to host and deliver your Power BI content. Capacities are either shared or dedicated. A shared capacity is shared with other Microsoft customers, while a dedicated capacity is fully committed to a single customer. Dedicated capacities require a subscription. By default, workspaces are created on a shared capacity.
PowerBI - Workspaces
Workspaces are containers for dashboards, reports, datasets, and dataflows in Power BI. There are two types of workspaces: My workspace and workspaces.
My workspace is the personal workspace for any Power BI customer to work with your own content. Only you have access to your My workspace. You can share dashboards and reports from your My Workspace. If you want to collaborate on dashboards and reports, or create an app, then you want to work in a workspace.
Workspaces are used to collaborate and share content with colleagues. You can add colleagues to your workspaces and collaborate on dashboards, reports, and datasets. With one exception, all workspace members need Power BI Pro licenses.
Workspaces are also the places where you create, publish, and manage apps for your organization.
PowerBI data set
A dataset (shared dataset) is a collection of data that you import or connect to. Power BI lets you connect to and import all sorts of datasets and bring all of it together in one place. Datasets can also source data from dataflows.
Datasets are associated with workspaces and a single dataset can be part of many workspaces. When you open a workspace, the associated datasets are listed under the Datasets tab.
PowerBI Dashboard
It is a single canvas that contains zero or more tiles and widgets.
PowerBI report
A Power BI report is one or more pages of visualizations such as line charts, maps, and treemaps. Visualizations are also called visuals.
PowerBI appSource
Microsoft and community members contribute Power BI visuals for public benefit, and publish them to the AppSource.
