0% found this document useful (0 votes)
187 views

Introduction To PowerApps-1

This document discusses building model-driven applications in PowerApps. It begins by introducing model-driven apps and their components, including entities, fields, relationships, and option set fields. It then covers user interface components like apps, site maps, forms, and views. The document explains how model-driven apps provide easy authoring, cross-platform publishing, and cloud and on-premises connectivity. It also discusses using Microsoft Flow for automating workflows. Finally, it presents a time card approval demo and discusses hiring a PowerApps developer on demand from Pragmatic Works to build apps and workflows.

Uploaded by

jaya chandra
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
187 views

Introduction To PowerApps-1

This document discusses building model-driven applications in PowerApps. It begins by introducing model-driven apps and their components, including entities, fields, relationships, and option set fields. It then covers user interface components like apps, site maps, forms, and views. The document explains how model-driven apps provide easy authoring, cross-platform publishing, and cloud and on-premises connectivity. It also discusses using Microsoft Flow for automating workflows. Finally, it presents a time card approval demo and discusses hiring a PowerApps developer on demand from Pragmatic Works to build apps and workflows.

Uploaded by

jaya chandra
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 20

Building Your First Model-driven

Application in PowerApps
Brian Knight
@BrianKnight
[email protected] 1
About Me
• Founder Pragmatic Works
• 14 Years as MVP
• Author 16 books

[email protected]
Canvas Apps help business-power-users to create and use
custom business apps across platforms
using Excel and PowerPoint skills

Connect to data & Create apps, forms, and Use apps on any
systems you’re already workflows without device – both web
using easily writing code and mobile
Focus on Canvas Apps

Canvas apps Model-driven apps


Start with user experience Built on the Common Data Service for Apps
WYSIWYG designer Start with a data model, relationships, and
Task- and role-based apps business processes
Mash up data from 200+ sources Build End-to-End business applications
Plan 1, PowerApps for Office Plan 2
Common Data Service for Apps
Standard entities that represent commonly used concepts
and activities across a variety of business & app domains

Ability to extend the standard entities by adding custom


fields and relationships

Add custom entities to support your scenario and application

Create calculated and roll up fields to provide consistent


calculations across apps

Define business rules and validation to ensure data quality

Easily import and synchronize your data using Power Query

Sophisticated security model providing row level security and


even models hierarchies.

Production ready pro developer SDK allowing CDS for Apps


access from any pro-dev application
Business Process Flow

 Visual indicators that tell users


where they are in the business
process
 Reduce the need for training 
 Configurable to support
common line of
business methodologies
Server Side Logic

 Server-side logic bound to entities,


works across all apps
 Create calculated and roll up fields
 Easily create validation and set field
defaults
 Update related entities with
synchronous workflows
Model-driven app components - Data
Component Description Designer

Entity An item with properties that you track, such as a contact or account. Many standard PowerApps entity
entities are available. You can customize a non-system standard entity (production designer
entity) or create a custom entity from scratch.
Field A property that is associated with an entity. A field is defined by a data type, which PowerApps entity
determines the type of data that can be entered or selected. Examples include text, designer
number, date and time, currency, or lookup (creates a relationship with another entity).
Fields typically are used with forms, views, and searches.
Relationship Entity relationships define how entities can be related to each other. There are 1:N PowerApps entity
(one-to-many), N:1 (many-to-one), and N:N (many-to-many) types of relationships . For designer
example, adding a lookup field to an entity creates a new 1:N relationship between the
two entities and lets you put that lookup field on a form.
Option set field This is a special type of field, which provides the user a set of predetermined options. PowerApps option set
Each option has a number value and label. When added to a form, this field displays a designer
control for the user to select an option. There are two kinds of option sets; option sets,
where the user can only select one option, and multi-select options sets, which allow
more than one selection.
Model-driven app components - UI
Component Description Designer

App Determines the application fundamentals such as components, App designer


properties, client type, and URL for your app.

Site map Specifies the navigation for your app. Site map designer

Form A set of data-entry fields for a given entity that matches the items Form designer
that your organization tracks for the entity. For example, a set of
data-entry fields that where user’s input relevant information to
track a customer’s previous orders along with specific requested
reorder dates.

View Views define how a list of records for a specific entity is displayed View designer
in your application. A view defines the columns to display, width of
each column, sort behavior, and the default filters.
Easy Authoring
 Truly WYSIWYG – full control
over user experience, use it as
you build it
 Create app logic with familiar
Excel-like expressions
 Mash up data from multiple
sources right at the app level
Cloud and on-premises connectivity

 Built-in connectivity to 200+ cloud


services, files, databases, web APIs,
etc.
 Seamless hybrid connectivity to on-
premises systems via the On-
Premises Data Gateway
 Build custom connectors for
everyone to leverage

Enterprise-grade Cloud and on-premises connectivity Pro-developer extensibility


Cross-platform

 Publish instantly to iOS, Android,


Windows, and the web
 Sharing apps is like sharing
documents
 Manage across environments
Microsoft Flow is a service for automating workflows
across apps and services

Connect to data & Create workflows Edit flows on web Approve requests
systems you’re already using triggers & and mobile or manage them
using; create the data actions without code on web and mobile
you need or scripts
• Internal applications
• Replace manual workflows
• When digital transformation
to your company means
PDFs being emailed
• Need to create mobile
internal apps for field crew

PowerApps with Flow Best


Fits
Time Card Demo

Requirements:

1. Bill by project
2. Project manager approves timecards

Ingredients
3. PowerApps for app
4. Microsoft Flow for approvals
PowerApps Developers Are Expensive
•Chances are, you may not need a full-time developer help
•Ramping up existing talent is equally expensive

* ZipRecruiter National Average


With Pragmatic Works, pay a
fraction of what you would pay
for a full-time resource and get
a developer-on-demand.

Expert Shared Development


Power Platform Pros Shared Development
• No onboarding or setup free
• Each Month:
• 32 hours of new expert
development from same developer
• 8 hours of support on-demand
(<2-hour response SLA during business
hours)

• Bring on the scope creep!


Pragmatic PowerApps Process

Onboard Build Backlog Work Backlog Support


• Gain access to tenant • Rank the most important • Work for 32 hrs on a set of • If problems arise, work on-
• Create support and features and apps needed problems on scheduled wk demand
governance process • Work on mockups • Present progress and build • 8 hrs of quick fix hours
next priority list available
Have Any Questions?
We’re here to answer questions about your enterprise
Power BI environment!
This is a Header
THIS IS A SUBTITLE

You might also like