Business Application Platform: PowerApps | Business Applications Spring 2018 Release

>>Thank you for
joining us today. We’re going to be talking about the new PowerApps capabilities available in the April release. Before we get into
those details, we want to talk about
the framing that we use to think about PowerApps. We use a digital feedback loop which is something
that you’ve heard about consistently throughout
the other streaming videos in the digital event which talks about how we go connect
together customers, products and people to actually enable
digital transformation. And we do that through the six main offerings
of marketing, sales, services, operations,
financials and talent, which together create
a great deal of data which can go feed back and forth
between these applications, to go transform how you
engage with those customers, your products as well
as your employees. A key underpinning of this digital feedback loop
is the platform elements. That’s PowerApps,
Microsoft Flow, PowerBI, Azure and the
Artificial Intelligence capabilities for Microsoft. And these platform capabilities are an essential ingredient to the digital feedback loop
for a few basic reasons. The first is that when you ever want to go
do digital transformation, the easiest way is to go buy an application
off the shelf. And with Dynamic 365 we have a plethora of
options available to you which all make it
very easy to just take something and quickly change how you actually run your business. The next bit, and this is
where the platform becomes very important is that none of those applications are
perfect right off the shelf. You have to go customize them and tweak them to
match what you need to actually make
your business processes run as you need
for your industry. And the platform is how
you go about changing things like the sales and service offerings
from Microsoft? And the third bit is
equally important. The reality is there isn’t
always an app for that. Sometimes you can’t just go
buy something off the shelf. Instead, you have to go
build it and to build it we have a great platform here at Microsoft to
go make that real. And a good visual to think
about that, is this one. If you imagine digital feedback
loop has the big elements that are available through
the SaaS applications from Dynamics 365, there’s all kinds
of small pebbles in between those that
are key to actually doing the digital
transformation making digital feedback loop
real for your business. And this last mile is
enabled by the platform. The platform makes
it incredibly easy to quickly build applications that integrate tightly
with your data and your existing business processes that you use within
your organization. And this is really
that last mile, that last element of
what it takes to truly transform how you engage
with your customers, your products and
your employees or your people. And if we go and
think about what does that platform really mean? The Business
Application Platform? If you drill into
it you can see that there’s PowerApps and PowerBIs, the two big elements of it. PowerApps is all about
rapid application development, quickly creating
experiences embedded in all your other
business processes and applications tailored to what your business needs and PowerBI which is
all about creating insights and
intelligence on top of the data as part
of your business. And these elements
integrate with a few other core products
or core capabilities. The most important of which
is the Common Data Service. Where the Common
Data Service for applications which is
what underpins PowerApps. It’s where all your system
of record data is stored as well as
Microsoft Flow which makes it incredibly easy to do
business process automation and workflows on top of that data and on top
of your applications. For PowerBI, it also has a Common Data Service for intelligence which
is what actually enables you to
quickly build insights and optics into the data that you’ve accumulated
from your applications. Together these two
elements create the business application
platform, PowerApps and PowerBI. And what’s great about
them is they also share the Common Data Model. The Common Data Model is
a really important detail for what the Business
Application platform enables because it’s a well-defined consistent schema to describe your business data
and your business objects. In addition to
the Common Data Model, there’s connectors and
data integration capabilities so you can very easily
reach data that may not be in the Common Data
Service whether it may be inside of SAP,
workday or salesforce. Over 200 different services have completely native
integration with PowerApps and PowerBI out of the box if that’s where
your data is today. And, what’s so unique
about PowerApps and PowerBI from Microsoft is the tight integration we
enable our Dynamics 365, Office 365 as well as your standalone business
applications that you create. If you go inside of
SharePoint lists, the way that you actually
change the experience for your end users
is with PowerApps. There’s way you go
create workflow and automation is through
Microsoft Flow. Same thing applies if
you’re on Microsoft teams or a bunch of other
Office 365 offerings. If you go to Dynamics 365, it’s completely natively built on top of the
PowerApps platform. That means you can go customize all your dynamics applications using the same knowledge
and tools and capabilities that you
see in PowerApps which enables our customers
to that earlier point to go tailor
our SaaS applications to exactly what they need
to go change their business. And of course for that last mile that we
were talking about, you can go build
your standalone applications and your standalone experiences on top of PowerApps and PowerBI. And when that may not be enough, when maybe you have
to go an extra mile, you can go drop into Azure. And Microsoft has
incredibly tight integration between PowerApps and
PowerBI and Azure to make it very easy to go bring in developer code through
APIs connectivity or just logic that may be beyond what you
want to go do in a high productivity application
platform like PowerApps. And to show these
things in action, we’re going to talk about
three real customer examples that are out in the wild today. First, we have Metro Bank. Metro Bank uses Dynamic CRM to actually manage all of its
engagement with its customers. And this is a great
story of how you take Dynamics 365 off the shelf. You can actually
quickly change how you go engage with your customers. But in their case,
there is more to it. They want to go have
an experience where they greet people who
walk into the bank. And to do that they
built the PowerApp. So with Microsoft PowerApps
they were able to go build a tailored experience for their greeters,
an app called m-greet, so that whenever you
walk into the bank they can give you a high touch, highly tailored
experience specific to what it is to be
a Metro Bank customer. And this connectivity between Microsoft and Metro Bank
really transformed and enabled that close
customer engagement which is so important to
Metro Bank as a company. And that’s what the story
really is all about. You can take Dynamics 365
off the shelf, change how you do
business and as needed, you can turn around and
drop into PowerApps to go build experiences as needed, as required and just exactly how you want them to go
engage your customers. Another great example
is G and J Pepsi. Here is a great story of how they change how
they engage with their product as well as how they empower
their employees. If they had a problem as the largest family owned Pepsi Bottler in
the United States, and that they wanted to go audit individual grocery stores
to make sure that the placement of
the Pepsi products is up to their standard and up to the agreements they already reached. To do that, it was
a paper process. People would go out
with clipboards and if they wanted to go order more inventory or
anything like that, they had to go make phone calls
and send text messages. However, with
PowerApps and PowerBI, they were able to transform
what this process looks like. First, they were
able to go build a mobile application
so that people who actually went into
these grocery stores to go do these inspections
and these audits, they could use PowerApps to record and track
every single thing that they noticed and whether
or not they were actually getting the placement that
they expected and wanted. And, to go beyond that, to really change the process and how they actually
managed their products, they were able to go and
add a function to go order more inventory or
request more delivery to that store which is the thing that before couldn’t
really be enabled, certainly not enabled digitally but they could go
transform that because they had PowerApps running
on a mobile app to go be brought into the store and actually help with that process. And as a result of
all the data from PowerApps flowing into the common data
service for applications, all kinds of other great
capabilities lit up. And primarily,
that’d be PowerBIs. It’s very easy to create
PowerBI dashboards on top of the Common Data
Service which allow them to go get insights that
they couldn’t do before. And this again is
a story of how you can go transform the way you
engage with your products. And the third example
is TransAlta. So TransAlta is a very large
company that’s based out of Canada that manages repairs
of electric wind turbines. And to do that, one of
the common problems they had is if a turbine
breaks off hours, how do you determine
whether or not to go inspect and repair it at that moment or to wait until business hours or more
scheduled repairs? And the way it worked before
was either you always send people or you had to
make a judgment call about whether or not
it made economic sense. However, they were
able to go convert this to a digital process, to digitize that decision
making framework to decide whether or not they
wanted to go actually and repair these wind turbines. And this process was a huge success in
terms of actually driving significant
savings and in just a matter of
a month actually pay for the development
of the PowerApps or the PowerApp itself
because they were able to go and prove
that business process of wind turbine repair
by bringing that into a digital framework
and digital system. So that’s what’s so important and so unique
about PowerApps across these three customers is
the real story of how you can transform that last mile
of engaging with your customers or that last mile of how you track your products or again that last mile
in the case of TransAlta of how your employees interact with your products. And this really
tells that story of the complete digital
transformation and digital feedback loop that we
were talking about earlier. What we’re seeing across all these different
customers and across all these different
industries is two basic principles of what application development
is training like. The first is the IT application
development is shifting towards low code,
high productivity environments. And the reason for that
is because it enables incredibly rapid application
development to respond to the changing business needs and regulatory needs of
a modern company. And that is only really
possible with a platform like PowerApps because it makes it so easy to actually
go build an application. The second is those high productivity
application platforms, or be it around
the data that you actually already collect
for your business, your CRM data, your ERP data. And the reason for that is
what we talked about earlier, it’s all about transforming how you engage with
your customers, your products and
your employees, and that data is
naturally stored inside your CRM and
inside your ERP. So you really want to have
that tight connection between your high productivity
application platform and these business applications
like CRM and ERP. And this story and
these two basic trends that we’re noticing in
the industry are what have driven us as Microsoft
to ship these three products, PowerBI, PowerApps
and Microsoft Flow to really deliver on
that promise to our customers. And we have major investments of them in the Spring release of this year to go
make them be even more unique in the marketplace. And what’s super core to each of these application
platform components, is that they’re Cloud-first. That means very easy sign up, very easy setup
and no deployment. You can get going in
just a few minutes. Second is it has, all around is single data store. What that means is we have
the Common Data Service behind PowerApps, behind
Microsoft Flow and enabling intelligence
and PowerBI on top of it and we make that
very easy without having to go do data movement
or data integration. And what’s great about
that as well is that Dynamic 365 natively stores all of its application
data for sales, service and marketing directly in the Common Data Service. And the third bit
is we recognize, all your data may not be
in the Common Data Service, it maybe in other systems. And to make that just as easy, we ship with over 200 connectors to the industry
leading system of records and business
applications to make it so that you can connect to
where your data is today. And that’s an
incredibly key element of the platform is
something we support natively out of the box with no coding and for
no additional cost. Additionally, we support an incredibly rich cross-platform
development framework which makes it easy to
go build applications and workflows and BI that
may run on iOS devices, Android devices, in
the browser or on a Windows PC. All of those are
supported natively out of the box and you
only have to build your applications
and your experiences once in a work across
all those different platforms. Additionally, everything
is essentially manageable. One of the biggest concerns
we have when we talk to customers is that with
this easy to use platform, you’re going to have
an explosion of applications and workflows and BI
inside of your company, but we make it easy as an IT department to
take control to have Data Loss Prevention policies or DLP policies to make sure that data doesn’t leak
out of your organization. There’s also incredibly
powerful reporting and our team support as well, so you can track what people are doing in your organization
and make sure they’re only
behaving according to your policies and
compliance and regulations. And lastly, and something
that is particularly unique for what we have
with our platform is that there are no cliffs. You can start with
something incredibly simple and get more and
more advanced all the way to building an entire end
to end application without having to go abandon this high productivity
application platform. And we do that because
of our Azure integration, our Office integration,
our dynamics integration, each of these three offerings. And to make that story real, let’s look at this diagram
of the ‘no cliffs’. First SharePoint embedded forms. There’s tens of thousands of authors already
building experiences embedded in SharePoint
which are reaching an even larger number of users using the
PowerApps capabilities. Whenever you build the PowerApp, you can bet it right on a SharePoint list to replace
the default form experience. And that means
the same skills you use for your business applications
you can also go put in your productivity
applications. Something unique to
what Microsoft offers. Next, you can go build relatively simple or
straight full line of business applications. And to demonstrate this,
we’ll talk about a real story. Brian Dang is a teacher based out of Orange
County who went and built PowerApps
digitally transform how he runs his classroom. And he actually did
this in a way where he built different PowerApps
to help the students learn more efficiently as well as a game application app
to help students track how well they’re doing on tests and how well they’re doing from attendance perspective. And Brian tells
a story about how PowerApps changed
his classroom and that it dramatically improved
the results on tests as well as efficacy of the coursework that
they’ve learned so far. And Brian has
no coding experience. He’s not an engineer.
He’s a teacher by trade. Went to school to
be a teacher, but he was able to go take
PowerApps off the shelf and start to transform
that last mile of his classroom. Another great story
is Mohammed from Harkey Pharmaceuticals
based out of Iraq. A real consumer of PowerApps. They had a process which was heavily manual between e-mail, paper and Excel files
to go track, visit other pharmacists
and doctors. But Mohammed, again, with
no technical training, without being a developer, he’s actually a pharmacist by schooling was able to build a completely digitally transform
process with PowerApps, Microsoft Flow and PowerBI to change how Harkey
Pharmaceuticals engages with and helps their customers operate better and then make
sure that their employees are able to better
track the work that they do and what they’re doing from a territory management
perspective. Again, no development
experience but able to go transform that last mile for his company
using this platform. The fourth item. This is Evan. He works at a consultancy called Confluent which helped
a company called IPS. And Evan is a developer or basically an
engineer by trade. However, he was able to
use PowerApps to build an incredibly robust
complex application to change the way IPS does electric motor
inspection and repair. And they did this using the powerful WYSIWYG capabilities
available in PowerApps. You can have a picture
of a particular motor and as people go and inspect it, they can click where
they’ve actually inspected, where they see issues and
rate different problems, and by doing this they were
able to go from a pen and paper white board process
that fully digitized process. And this digitized
process is able to actually enable all kinds
of new customer experiences. Before they wouldn’t
be able to reach out to their customers
and let them know that the repair is almost done, but now they can do that because each stage and piece
of the process to go repair the motors is
tracked digitally and you can go generate things
like e-mails and so forth. And again something that’s
not available off the shelf, not even available by customizing something
off the shelf, but a custom line of business application that’s
very complex it had to go be built using
the PowerApps platform to go make that real. And lastly, I say
the most complex. We have ISVs and partners who are building
on top of the same platform. This is a picture of
the bank’s site team. They’re a professional
development organization. They sell software
and they’re building their entire application
around better engaging customers when they go
walk into banks on top of the Common Data Service
and on top of PowerApps integrate
with Dynamics 365. This is a full development team
with source control, dozens of engineers
and they’re able to go make it work using
the same platform. They don’t have to go look into building
everything from scratch. From the most simple
SharePoint form to the most complex
ISV application. All they can happen
without cliffs on a single business
application platform which includes PowerApps, PowerBI and Microsoft Flow. And this is really
what our vision is. We’re all about
democratizing app creation. We want to make it possible
for people who could never change their business to start changing
their business today. And this is something that
Microsoft is not new at. This is something Microsoft has an incredibly rich legacy
of doing from Excel, Access, InfoPath,
Visual Studio and Visual Basic across all of
these different things, Microsoft has been
at this for decades. And really what we
look at with PowerApps, Microsoft Flow and
PowerBI is the cloud re-imagination of
those particular capabilities, and we see that momentum
in the market. If we go look there’s tons and tons of huge logos
that you may recognize. There’s over 1.1 million monthly active users on this PowerApps
and Microsoft Flow. There’s over 213,000
organizations. All of them are using these capabilities to transform how they actually
run their business. And we’ll talk about through another demo in just a couple of minutes a real example of
how a customer has done that. And just another element
of it is PC Mac. They did a review of the low-code high productivity
application platforms out there and PowerApps
was their editor’s choice. And that’s because it just has so much power that
you could go use. And again, really what
that means is no cliffs. You can start simple, basic UI, basic forms over data, but as needed you can earn
more and more expressions and more and more capabilities without having to go to
a different platform. And this broad spectrum
of capabilities including the ability to go dive into Azure is something that
only Microsoft can do. And to show how real that is, we’re actually going to turn
it over to Ryan Cunningham, who’s going to do a live demo
and actually build a real PowerApp that matches one of
our customer scenarios.>>I want to talk
about Intercars today. Intercars is the
largest distributor of automotive spare parts and
repair supplies in the EU. They serve 16 countries, they cover on more than 10,000 individual customer locations. Now their field salesforce
of more than 600 people, that means they
are visiting almost 100 locations a month
for some people. That’s a constantly mobile on
the go frontline workforce. Now, what we’ll talk about
is how PowerApps can start to help with some of those
frontline business scenarios, automate the types of
processes and build the applications
that you just can’t find anywhere else
or buy off the shelf. Let me give you an example
of one of those scenarios. Now Intercars sells not
only automotive spare parts. They also sell repair supplies
like this tool chest. They come stocked with tools and individual wrenches
and socket sets and that’s a great deal for them the day that they sell it. But a year down the line, half of these wrenches
are missing. Some of the sockets are broken, and restocking this tool chest becomes a whole different
proposition entirely. The classic method of
that seller who has 20 minutes a month to
be on the site to bring in a 200 page parts catalog and flip through it page
by page and try to find this one particular
little socket set to make a manual order just was not
scaling with that business. So today we’re going to
talk about how a company like Intercars can very rapidly build extremely custom
applications for a scenario like this very
quickly in PowerApps. Let’s dive in and take
a look at how it works. Now, we like to talk a lot about how powerful PowerApp is and
how quickly you can build. And they’re all a lot of
great ways to get started, you know not even
starting from scratch with great templates and samples
to jump off the bat. But today we are going to
start from scratch from a completely blank canvas to show just how powerful
this platform is. Now as PowerApps loads up here, you’ll notice that what
you’re about to see is not your traditional software
development environment. In fact it looks nothing
like Visual Studio. It looks a lot more like PowerPoint and
that’s no accident. I’ve got screens of
an application that I can add just like I would add
slides in a presentation, and visually they light up for me right on my canvas here. And I can use my Office skills to do very simple things.
I can theme it. I can make it look
like my company by inserting a logo or
an image element. And all of this is very
easy to do with my mouse. Let’s go pop in our logo here from our computer
and upload it. And I have full control over the visual appearance and
look and feel of this app. This isn’t a config thing. I can make this look and position exactly
how I want it to. Now of course I’m not just
pushing pixels around. What I’m also doing
is able to work with a whole rich set of
connected data sources. In fact, right out of
the box PowerApps connects to more than 200
individual applications and services where my company
might already have data. Everything from Adobe, the Zendesk and
everything in between. I can do simple things like connect filtered search of
tweets about my company, more sophisticated
things like access a sequel server running
on prem through a gateway. But of course actually in
this case of Intercars, we don’t need any of that because we have something
even more powerful. We have the Common Data Service. Common Data Service
is the data platform that comes with PowerApps. That as part of
this Spring moment is getting a
radical expansion of its capabilities and for our customers that are
building new applications, comes with rich schema and
logic right out of the box. For customers like
Intercars that already have data in
the Microsoft Cloud, in Office 365, in Dynamics 365, that data just lights
up by default. So we’re going to pull in a list of accounts and a list of products and a list of line
items of those products here, and PowerApps already richly understands the nature of
that data and information. I can put templates
on this type of information and we know
where to put the images. We know where to put the titles. We know what rules to enforce when these
things get updated. And that all is
just coming natively out of the box with
the Common Data Service. Now of course my Office
skills still apply. I can make a title larger, I can go bump up the font size, all these things are
very easy and familiar to do even if I’m not a
traditional software developer. But, this is not PowerPoint. These are not static boxes
and static pieces of text. These are actually bound
to data under the hood, connected to that list of accounts in my business
database, in my platform. And I can change that
binding on the fly. I can say, “Hey, let’s
make this the full name, and over here let’s make
this one the address.” And just like that
my application is updating in real time
as I’m designing it. I’m actually using the app
as I’m building it here to get instant feedback about how my changes
are taking effect. It really helps, the less
traditional software developer make very rapid progress here. And of course I’m not even
limited to a single screen. I can go build navigation
into this application. I can say, “Hey, when
I click any one of these icons go take me back to another screen
and keep building.” Now, all that is
powerful and all that is fast but, I’ll
level with you. This is something I can do in other low code
platforms as well. Here’s the thing. This
is right about where every other low code platform on the planet stops being low code. And when I want to do something a little bit more sophisticated
or a little bit more custom tailored to
my business than just formatting a list and
putting a logo on the top, that’s where I quickly hit a cliff in a lot
of other platforms. But with PowerApps we’re
just getting started. And I want to show
you a few elements about what makes this true, this ability to very quickly scale and sophistication
and amplify what a whole new range of micas can do inside
of this platform. And we’ll start with something
very simple as an example. Now I can add text boxes and images and the whole
nine to this application, and I can you know just
like I could in PowerPoint, type a static piece
of text into this box. But you’ll notice
as I’m doing that, that silently behind
the scenes we’re updating this Excel like formula
in everything that I do. Now, in fact, every single
element and property of every single control
in this application is governed by an Excel
like expression, or by a language that millions and millions of people
already know how to speak. In fact, we honor the entire Excel syntax right
here in PowerApps and we’ve added a few things to it to help you build
applications quickly. It means that I can very
quickly get productive and do sophisticated things
without having to learn an entire
programming language. The Delta to get here
is just much smaller. So let me show you
a really simple example. Let’s say instead of just typing a label into
the top of this page, let’s go grab the thing we selected out of the gallery
on the previous screen. And you’ll notice here that
IntelliSense is actually helping suggest to me
all those same fields, all those things I know
about this account. I can go back and pull through the full name out
of IntelliSense and it’s going to
update right inside of my application
just like that. Now I can build myself
a little bit of a back button, and now we have
an app that’s actually responding to context
across screens, passing the value of the customer that
I’ve selected here. Now that’s a very
simple principle but it applies very powerfully to
the rest of this application. Now, let’s use it. Now remember, we’re trying to prove
the process by which we restock a tool drawer here. So let’s go add a list
of those tool drawers and let’s wire it up to
our list of products. And again let’s pick
our rich template for this particular list. Let’s get something
nice and visual here. Now we don’t want to
show all the products, we just want to
show the last one that this particular
customer backed, so we’re going to pop it
in here and tighten up this particular little gallery to get to this tool drawer. But we want to go
further than that. We want to look inside
the drawer and see what particular sockets and
wrenches we want to restock. But we can do that too. We’ll add another list. We’ll bind this one
to the items that come inside of the tool drawer. Now, we don’t want all of the socket wrenches in
our entire database, we want to filter
it down just to the ones relevant to
this particular product. And again, we can do that with this very simple Excel syntax that we can learn very quickly. I can say, “Hey, let’s filter
this product items list.” And again just like in Excel, PowerApps is going to
walk me through it. It’s going to give me
a nice template to fill out, the IntelliSense is
going to help me. I’m going to say, “Hey, show me all the product items
where the idea of that product item equals the thing that I just selected
on the previous step.” In fact IntelliSense
is smart enough that I’d barely need to type
it all to get this done. So I wrap that up
and then PowerApps is going to go off to
the server grab back from the Common Data Service
just the wrenches in my particular tool drawer. Now of course, I
still don’t want to hunt and peck through a list, I want to see what
this thing is supposed to look like in real life. And it turns out that we’re
laying out tool drawers on a predictable grid
and in PowerApps I can build that with
just a few strokes of my mouse. I can literally recreate exactly what this tool drawer
is supposed to look like. So now my employee rather than walking in
with a big book of spare parts just opens up a drawer and sees what
it’s supposed to look like, sees what’s missing and
can do the difference. Now let’s finish
this scenario out. I want to, when I actually
select what’s missing, go collect that
information and start to build the order of
what I’m restocking. I can say, “Hey, when
somebody presses a button, go collect together
the items that they tap on.” Again, I’m just using my mouse
to collect these things. And I can then do things
with that collection. I can go to the fill property, the color behind
this particular wrench and I can write logic. This is rocket science kind of software development here but
we’re making it so simple. I can just say, hey if this item is in that collection
I just created, again IntelliSense helps me out, let’s make it blue, actually blue violet, beautiful color. Now, as I start to
build that collection, I also obviously want to
see what I’ve collected. So I’m going to
go insert a table. I’m going to drop
it to the bottom. I’m going to bind it
to that collection we just created on the fly
and I’m going to say, hey give me the name
and the let’s say how about the quantity of the thing that
we’ve selected. Tighten that up, and
just like that I’ve built a process that is extremely custom to my business
where I walk in, I pull up in the drawer and
I say, “Oh, that’s missing, and that’s missing,
and that’s missing, and that’s missing and we
need one of those too.” And just like that we’re
building this custom order. There is not another platform on the planet that can go that fast and build this custom
of a process without touching
a single line of code. PowerApp is extremely
powerful in that regard. But of course,
there will still be problems for which we
need to write code. And for example I’ll come
back to this first step. We skipped over a detail here. It turns out it’s
not actually all that useful to give
every single one of my 600 field sellers
the list of every single one of the 10,000
accounts in the database. I don’t want them
to have to hunt for where they need to visit. I want an employee to know exactly where to
go in the morning. Given their geolocation which we know because this is
running on your phone. Given their identity
which we know because you’re logged in
with Azure Active Directory, tell me exactly where to go. Now, that’s not
something I’m going to write in an Excel expression. More power to you if you can. But that’s a great opportunity for a professional developer to create a building block
that comes in and augments this experience
without having to throw out all the goodness that
we’ve got here in PowerApps. And we’ve done
just that. In fact, we’ve started out
this Azure function. It’s going to run
server lists and on demand. This professional developer
didn’t have to worry about infrastructure
or anything. They just write the code
that says, “Hey, given this geolocation
of latitude longitude, where should I send
my person next?” And you’ll see we’ve kind of stubbed out the answers there. And if you do this in Azure, if you do it in Azure functions
or API managements or a number of
other Azure services, we make it really easy for you. We give you this nice export to PowerApps and flow
button right within the professional
developer experience that lets you light this up in a few clicks for a low code developer
working here in PowerApps. And in fact just like that, all these data sources
that we showed earlier, the whole 200 that
come out of the box, we can add to that list with any custom data source,
any service, anything we can, we can put a rest API in front of and
wrap in a swagger file. We can bring here into
PowerApps and allow our local developers to go even further without
hitting that cliff. So I can say, “Hey, don’t just point this at
the list of accounts. Let’s actually go point this at the route mapping function
that we just added, and let’s pass it our location.” I’m using all the same tools
that I just learned before. I’m going to go
past at my latitude, and my location.longitude, and just like that
it’s going to go fire off to that Azure
function and bring me back in a few seconds the list of four stores that
I should visit, not the list of 10,000, that I might want to go
to in the whole database. And that’s how we hit a whole nother level of sophistication in
these applications. Now of course,
that’s still not all. But at the end of the day
it’s not just about this one application or this one screen or
this one tool drawer. It’s also about how these things
work into the fabric of our business processes across
all of our applications. And to give you
a simple example of that, if we continue
building this app out, we’ll cut forward here in a second to a more
finished version. At some point I’m going
to place this order. At some point as a seller, I might want to request
a discount for this order. Now, I may or may
not actually have the authority to approve that discount on the fly and in fact for a distributed
sales team, different sellers have
different levels of ability to approve different discounts when they’re out in the field. Now, still I can automate
that business process and I still don’t have to break into code or expensive customization. In fact, I can build that whole approval process
in Microsoft Flow. Microsoft Flow comes
with the platform and it allows me to visually logically design
business processes like I would draw
them on a whiteboard. It’s connected to
all the same data sources that PowerApps can pull in and I can very quickly build logic just like this. When a new order
hits the system, let’s go grab
everything we know about the user requesting it out
of the Microsoft Graph. And then if
that discount request is over a certain threshold, in this case 25 percent, let’s go kick off
an approval process. And I can write this just like I would compose it as a message. In fact I can pull in
dynamically data from those previous steps what we know about the user from Office, what we know about
the order from the Common Data
Service and I can use it to build
this approval process, Microsoft Flow takes
care of the rest. So let’s see this whole thing
in action end to end. I’m going to pop over
to my mobile phone here. Now, Intercars employees can work in a Bring
Your Own Device culture and Intercars developer can publish this application in an instant. It will run inside of
PowerApps container, on iOS, on Android, it
will run on the Web. All I needed to
do is log in with my company ID at
the front door and I can get a polished application that looks awesome and it’s just
for my business process. This was built using
exactly the same tools that we just saw. So, I’ll get up in the morning, I’ll say, “Hey, where
should I drive first?” The application will suggest
to me exactly where to go, how far away it is, promotion I can offer
that customer when I get there. I can dive in and I can see just a slightly richer stylized
version of this process. I can pull open a door
at the tool chest. I can say, “Hey, we’re
missing that one, and this one and
this one and that one.” And I can build this order
all the way through. In fact, I can request
my discount here. I can even sign it and use all these great touch
device capabilities inside of PowerApps as well. Now, I’ve requested
this discount, it’s over my threshold. You noticed as I did that, this button for submit
an order is actually changing to a request
approval button. And as I request an approval way over my discount here,
and I send it off, it’s not going to immediately commit that into the system,
it’s going to tell me, “Hey, your request is pending, somebody will get
back to you soon.” Now for the kick of this demo, I happen to also
be the approver. And so I can see that that push notification came
right in from Microsoft Flow, right here on the mobile device
of the approver. I know exactly who
requested the discount, how much they requested it for, and I can approve or reject
and add comments right here within the fabric of my experience without
even missing a beat. And Microsoft Flow
handles the rest. Soup to nuts it keeps track of exactly the full approval
history and logs everything, in fact logs
all that information right back in the Common
Data Service for me. So let’s switch back
to the desktop here. And you’ll notice that
I actually also got that approval message
right inside of my e-mail, right inside of
Microsoft Outlook. At the same time that
I got it on my phone, I can richly use it right
inside of the rest of the tools that I’m already using all day long for productivity. And that’s really
powerful as we start to zoom out further
from this experience. Again, it’s not just
about the one application. It’s not just about
the one business process. It’s really about how we
start to use these tools, these PowerApps platform
to richly customize and extend everything that
we get from Office 365, from Dynamics 365, from the intelligence and the action that we can take on top of that. For example, the datas in
the Common Data Service, the model is richly understood. Building business intelligence
on it is a breeze. I can quickly build a dashboard in PowerBI
that says, “Hey, from my back office
exactly what did we sell the stingray
auto repair yesterday? And where were they or how many support incidents
do they have open?” I can even build a
rich custom visual to show me exactly what
this customer ordered. Now, this whole custom
visual on the right, was that developed by
a professional developer as a PowerBI custom visual? No. That’s a PowerApp. I built that in
exactly the same way that I built the
mobile application that my field sellers are using out at every auto shop
all day long. And in fact that same pattern extends across the rest
of my Office experience, here in SharePoint where is
where I’m uploading images of these socket wrenches and logging which position
in the drawer are they. This is not the standard
SharePoint forum that comes out of the box. This is a PowerApp. It’s got a customized button
on top of it. In fact, now every
SharePoint form, every custom form across SharePoint Online has
the same customized button. Guess what happens
when I press it? You’re right, we fire
up PowerApps and you use that exact same design
experience that we saw in building the original
application to build out custom experiences inside of the rest of your apps as well. It’s not just about
the frontline worker scenarios. It’s not just about my field sellers out
there in the field. I’m also using this platform to fundamentally transform
my back office as well, and the rest of our processes
and applications around it. See on the other side
of Intercars business, every time a field seller is out there ordering
more socket wrenches, we have to maintain
a whole network of supplier relationships as well. And we have to know
where we’re going to get those socket wrenches from and how much they’re going to cost, and if we can get them from
a better place tomorrow. Now, we can still manage all of that on
this rich platform. In fact we’re here in the PowerApps
management experience, we can see all of the entities
that we’re managing across our business
right here in one place. All the individual accounts and appointments and addresses
and products and suppliers. In fact, even here we
can richly model and extend that data model that comes out of the box and
add our own entities, our own fields, our own particular rules
about what to track. It’s super easy to do
right in context here. For example, I already have one. If I want to go create a status field and I want to make it of
a particular type. In fact, I could make it a
static text box or a number, I can even make
it a multi-select, an option set, and I can
even create that option set right in line here
of my application. I could say, “Hey,
one status is good and another status is not good.” And very quickly I can customize the surface of this application at
the data layer as well. And then PowerApps gives me the ability to quickly
build on top of that. Now, I can build
the Canvas-based applications that you just saw me create, the very visual PowerPoint like applications where I
started my user experience, but I also now have
another option in PowerApps. I can model these
applications as well. I can start at this data model,
at these relationships, at the rules that are attached to these individual entities. And I can then automatically generate applications
on top of them. Let me show an example
of one of those, then we’ll pull back and
see how it was built. Now this is a supplier
management dashboard for my back office to track all the individual suppliers
that we have relationships with and all of their status
in adding to this system. And in fact, we’re
right in the process of adding a new supplier,
AC Delco here, and I can build a rich
application completely customized, the rich forms and business processes that I need to onboard a new supplier
into my system. In fact, I can even model this rich business process
that shows me step by step, walks me through
as an employee at each stage of the process
of what I need to do. So it really cuts down
on the training time and enforces consistency across
this particular application. I can say, “Hey,
have we received a proposal from the supplier?” Yes. You know, when did we
get it? We got it today. or we completed
our legal review. All these things are
mandatory for me to proceed to the next stage
of the process. I can even then continue
to sign things and it will tell me exactly what
to do as I go. And in fact, you’ll notice
a nice little thing down here, it automatically is calculating for me that the contract
should start 14 days from today from the day that I said that
we should kick it off. Now, how did I create all this? Did I build all of these with individual check marks and lines and arrows and fields like I did for the tool box application? Actually no, I modeled
the application. I modeled the process. I visually designed
the business process and said at each stage of
onboarding a new supplier, here’s exactly what
we need to ask for in the order we
need to ask for it in and here are
the fields that are required to go on
to the next step. And then I brought
all of that data, the entities involved in that and the processes themselves and I brought it
together in a subset of an application module. And then I press publish, and all that great
user experience which by the way is responsive
right off the bat was just automatically
generated for me and I can use it everywhere
that I need it. So extremely powerful
capabilities to both start at a rich user experience for your highly
custom processes, and start at a rich data model
and automatically generate that user experience for your more immersive back office scenarios and application. Now I can even set these automatic
business rules attached to the entities and the data
that run on the server. I can say, hey, for
example that rule that automatically calculated
the contract start date, this is exactly what
it looks like to build. I didn’t have to write
any code for that either. I just said hey, when all of the individual
review steps are complete, if we have a contract
receipt date, let’s go automatically
calculate 14 days from now. That’s when the contract
start date should be. It’s just a couple of
drop downs I can publish it. And because that’s running
on the Common Data Service, because both of
these applications are built on
that same data platform, I can leverage that rules
and those server side logic in my Canvas-based
applications as well. So back here where we
started in PowerApps studio, I’m building out
this sort of tablet or web app for supplier management
and status management. I can come in and leverage
exactly the same logic. I can say, hey yes,
we’ve completed all of our reviews and our receipt data
of that contract is today and I can go update
this thing and just like that the same rule
will run on the server. It’ll go past
that information off to PowerApps and the start date itself has been updated to the exact same date that it was on the model driven
side of the house. An incredibly
powerful set of tools. We really just scratched
the surface today. And in fact in a moment we’ll go back to Charles and talk in a little more detail
about many of the new features that are
coming to the platform. But it’s exactly these tools that customers like
Intercars are using to transform their
business processes from the frontline
to the back office, and everywhere in between. And it’s the same set of
tools that you too can use to bring digital
transformation to your company. Now we’ll go back
to Charles and talk more about all the details of the new goodness
that’s coming to the platform in
the Spring release.>>And now we’re going
to drill down into the new details and new elements of the Spring release
for PowerApps. We’re going to talk about the key capabilities
that are included now. The first and most important is that PowerApps is tightly and natively integrated
with Dynamics 365 as well as Office 365. And for the first time
Dynamics 365 for sales, service and marketing data is natively available inside
the Common Data Service. Another interesting
and powerful element is a new model-driven
UI capabilities. These are in addition
to the existing WYSIWYG, Canvas-based app creation that you know and love
from PowerApps, enable a new set and new type of applications
to be created. The third item is that
the Common Data Service and the Common Data Model have
taken a huge step forward. There’s a bunch of
new capabilities including the data layer
as well as a new and much more clear our Common Data Model that can
be used across applications. And for those situations where the Common Data Service
is not the right choice. We have over 200 connectors, tons of great enterprise
connectivity as well as new data integration
capabilities to bring data into the Common Data Service
when and how it makes sense. And lastly, very rich enterprise governance and
compliance capabilities so that you can go
better your business on the PowerApps platform and
run the most mission critical workloads on top of it and not worry about hamstringing or restricting citizen
developers within your organization
and make sure that you still are being
compliant every day. If we go look at
that integration element, this is a great picture to show what it really looks like. We have Dynamics 365, Office 365 and customer applications all built on
top of this single platform. And this platform spans
things like Microsoft Flow, the Canvas-based UI
creation capabilities, model-driven UI
creation capabilities, all of it on top of a very rich Common Data Model
and Common Data Service. And if we go look
to the bottom of this diagram there’s a few
really important bullet points that we want to make sure
that we hit and make sure you take away from the spring
release of PowerApps. The first is that
all the Dynamics 365 data is now natively integrated inside of the
Common Data Service just like we talked about before it’s available in
place. It’s not a copy. It’s not a data integration. It’s available right inside the Common Data Service
which allows you to build incredibly powerful
applications against your existing business
data with ease. And this is what we
think about and what we talk about when we mention that the Dynamics 365
integration between PowerApps and the Common Data Service is better than ever. And this is really only
made possible because of these new Common Data
Service capabilities and the new Model-driven
UI capabilities. And PowerApps, again, it’s just an incredibly
broad and rich set of capabilities that
make it possible to go build application
experiences that complete that last mile of digital transformation we talked about earlier in
the session today. And to go make that real
if you look at Office 365, we can look at four great
examples of integration. The first is PowerApps embedded inside of a SharePoint lists
as a SharePoint form. PowerApps is the natural
and class successor for form customization
inside of SharePoint and it makes it easy to go take your great skills and
great capabilities that you’ve constructed in the platform
and bring them into the Office apps where your employees are working
each and every day. In addition to that,
Teams is the same way. You can go out of PowerApp or Microsoft Flow associated
with any Team channel. This makes it very
easy for people to go interact with their PowerApp
in the context of Teams where
the conversation is already happening within
your organization or without forcing them to go learn yet another application or another place to go
discover those capabilities. And Microsoft Flow it sits there as well and
enables all kinds of great automation on
top of interacting with chat messages as well as file movement and
things like that. Next, we also have incredibly
powerful Excel integration. We have Microsoft Flow and the Common Data Service natively integrated
inside of Excel so they can very easily
trigger your workflows based on what you
select as well as go import data from
the Common Data Service into Excel and do all the slicing
and dicing that you want and that you’re
used to doing. And this is all brand new
capabilities announced as part of this spring release
for the PowerApps platform. And fourth, and
a very interesting element is also the PowerBI integration
that we have where you actually have PowerApps
embedded inside of PowerBI as well as PowerBI
embedded inside of PowerApps. And what this allows
you to do is when you’re actually looking at
your data to get insights, you’re able to
very clearly embed PowerApps to take actions on those insights and that data. This makes it easy.
You don’t have to go switch again to another context completely in the experience
you’re used to with PowerBI, you can go take action. And a common thing
we’ll hear from customers is you may be looking at say
salesforce performance, higher employees
are actually doing. And if the performance isn’t
good you may want to have a PowerApps form
available right there to go trigger a workflow
or remediation steps to hopefully go improve
that performance. And that type embedding
really helps us transform what
the experience is like for our customers
and your employees when it actually comes to
interacting with your business data and
your business processes. It’s available
wherever they are. If we then turn over to
the new UI capabilities, we have the WYSIWYG, Canvas-based app creation which is super familiar and very commonly used
today for PowerApps which allows you to start from a beautiful PowerPoint like UI, bind your data as needed and actually create
an experience that exactly matches what your business process
and tasks require. Additionally, we have the new
Model-driven capabilities. And those are
available just like the Canvas-based ones
on all types of different devices
out of the gate, whether it be a mobile
device or a tablet. And for those
Model-driven capabilities, those allow you to
start from your data. Instead of using canvas to start from the UI and then
bind to the data, with Model-driven you start by defining your schema,
your relationships, your entities, and then we automatically will
generate UI on top of that. You can go tweak the UI
as you need but it’s very much driven by the data and the relationships of those data. And these again are available
across tablet devices, desktops with a rich app
module creation experience and across all
different form factors. And these two types of
applications allow you to again spend that whole spectrum of app creation without any cliffs, whether it’s very simple basic binding to
data all the way to the most complex UI
that you want to hyper tailor to what your customers
or employees require, you can do both of those on
one platform with PowerApps. Additionally, if we go
change and drill into the WYSIWYG with
a little bit more, it’s very, very easy for you to go manage that experience of what the UI looks like
by screen by screen. And you can do this
to go mash up data across different data sources
as well as actually use templates so you can get
out of the box support for common business
processes that you may have to go interact with. Things like inspection or field services are very common
scenarios for our customers. We have rich templates and
rich UI available out of the box to go enable
those on top of your existing business
application data. If we look at
the data that actually powers the applications
that you construct, we have the Common Data Service and the Common Data Model. And the Common Data Service
as we mentioned earlier, the important element is now all of the Dynamics
365 data is just available natively right inside of CDS without having to
do any data integration, data copying or data movement. And that means if you create a PowerApp it will automatically update in place
the same data that your salespeople would see
in their sales application, or your marketing
people would see in their marketing application, and I say again because it
really is a single data store. We’ve been able to
enable this as part of the platform with complete
backwards compatibility. So that means if you already have customizations
and experience on top of Dynamics 365,
they don’t change at all. You don’t have to
do anything to take advantage of
these new capabilities. They’re just available
out of the box. And if we go look at
the Common Data Model, that’s something that
allows us to find very common business
entities and objects. And this is a very
important thread throughout the entire platform
because it enables tight integration
by our ISVs and partners to go do additions. And if you look at
what Adobe has done, they’re actually going
and doing extensions of the Common Data Model
using their own XDM to create a combined
unified view of business data for
our joint customers. This Common Data Model is a key kernel of the Common Data Service
to go make it possible. If we go look at
custom application development, we would recommend to
start first and foremost by looking at the
Common Data Service as a place that you
store that data. But the reality is you
can’t always do that. Sometimes you have a huge number of systems already in place
within your enterprise. And for that Microsoft very uniquely has over 200 built in connectors that
you can drop into your application without
having to write any code. You can just snap them
in, and this makes it possible for you to
go connect to your data wherever it is without having to worry about
how you bring it into the Common Data Service or do a data
integration project. And these connectors spend
the full spectrum of what your employees would require or what your business
would require. There are things like
file services, SharePoint box, Dropbox, web APIs to
cloud services like AWS, Azure and so on as well as common business
applications like Workday, Marketo, SAP and so on, all available out of the box very easily and very natively integrated with what
you need and it is the same application platform
for UI creation. And these different
data sources are again a really key element that
we make very easy to use. And we do that by what we call mashup or composite
applications. So composite
applications allow you to go to multiple data sources, say Dynamics 365 and SharePoint and bring them together into
a single experience. And this mashup capability
again is something very unique in the industry that you can
do without running any code. And even if we don’t have over one of those 200 connectors
as one that you require, you can go create your own. You can create a custom
connector and drop that in with your developers and
with your code and that will enable it
inside the same system. And to operate on all these
different data sources, there’s a very simple
Excel like language built into PowerApps
and which we saw in the demo
from Ryan earlier, this simple language makes
it easier to do lookups, filters and so on without
going and having to learn a brand new programming
language sentence like Excel and also without having to go drop
in to developer experience to go
code everything up. And again, all out of the box, all on top of those same, Canvas-based and
Model-driven app creation experiences, they were
just talking about. Another core part of the PowerApps platform
is Microsoft Flow. It enables rich workflow
capabilities as well as business processes to actually manage the UI experiences
for end users. Microsoft Flow supports
the same 200 plus connectors as well as the Common Data
Service just like PowerApps. And that makes it
so you can very easily build
automations as well as applications that tie together tightly and build on
top of the same data. And not only can
you actually trigger Microsoft Flow based on changes and data with
events and triggers, you can also trigger based
on a button press or activity taken inside of UI created
inside of PowerApps. And altogether this
makes it very easy to transform repeatable
simple tasks within an organization to
actually automate them away and you can also go
use business processes to completely control
the experience for your end users to make
sure that they complete the necessary steps and
necessary gates as part of say interacting
with the customer or closing a support ticket. All that is possible using the Microsoft Flow
capabilities which is richly and natively integrated
inside of PowerApps. And across both Microsoft
Flow and PowerApps, there’s enterprise grade, admin management and
compliance management. And the way this works
is we actually have a central admin center
which looks across all your Dynamics 365 applications as
well as PowerApps, Microsoft Flow and
Common Data Service to enable a rich set
of capabilities. First, as it’s all managed
inside Azure Active Directory. Your user list, your security policies like two factor
authentication as well as conditional access
so that you can have management around
devices with Windows, Intune or other MDM offerings. Additionally, in this admin
center there’s rich reporting and rich auditing
capabilities so you can see what people are doing with PowerApps and Microsoft Flow
inside your organization and make sure that they’re
behaving according to what you actually want them to do based on a compliance and security perspective. And beyond just reporting, there’s also data loss
prevention policies. These policies
make it so that you can’t go and actually
flow data from a high business impact or a very sensitive environment to a lower sensitivity environment
like say the Internet. So a common example
we may see from our customers is they
don’t want to just say take something from a locked down SharePoint document library and then send an e-mail out to potentially people
outside your company and you can actually enforce that with the data loss
prevention capabilities inside the platform. Altogether, all of
these different capabilities come together to provide an incredibly compliant and
enterprise grade experience to not only manage the applications that
Microsoft builds, that’s our dynamics 365 but also what ISVs build
that also extend the same application platform
as well as what your IT department or individual employees as citizen
developers may build. All of them could
fall under the same centralized unified
admin experience with those rich capabilities for both auditing, reporting
and enforcement. And beyond that, there’s also a very important element of the platform which is AppSource. AppSource is
the one stop shop to go install applications
from ISVs and third parties as well as
partners of Microsoft right inside your Common Data Service or your PowerApps instance. They all interact and play together in an incredibly
powerful and unique way, and they were on top
of that same platform. So all of those rich governance
capabilities that we just talked about would apply to things that you would solve
from third parties as well. In addition to going
outside of your company, there’s also an organization
level AppSource capability. So you can actually construct applications within
your company and publish to your employees and they
can actually go pull them down and make use of them in
an easily discoverable way. And again, all of this is built on top of that
same platform with the same Common Data Service
with the same business data and the same security
all bundled together. And that really
goes back to what we talked about in
the very beginning today. When you go look at
the digital feedback loop, we go bring together from Microsoft Dynamics 365,
the marketing, sales, service, operations,
financials, and talent applications as well as those little pebbles in between which you can get
from ISVs or build yourself. They all play together
and they all integrate together on top of one platform, the Microsoft platform for business applications
which is PowerApps, PowerBI and Microsoft Flow. And with that, thank
you for your time today. And I’ll just ask one call to action of people that
are listening in. Go check out PowerApps. Go to, sign up and in just a few minutes
you can go build these same applications
that you saw today of the demo and on these slides
in the same workflows. And I look forward to
hearing from you as you go and actually
build those. Thank you.

Top 5 BI Tools | Business Intelligence Tools | BI Tools | Intellipaat

Once again welcome back to Intellipaat
friends. And again we are back with another interesting and powerful video
which I’m sure is going to be very helpful for you. So let’s begin. So we all
are aware that today a huge amount of data is being generated everywhere everytime and then this data actually needs to be analyzed to let’s say make crucial
business decisions and for that numerous tools are available in the market to
convert raw data into useful business insights. And then these tools are
actually collectively known as business intelligence tools. So here in this video
we are going to talk about the top 5 business intelligence tools that stand
out from the crowd and are the choice of millions of organizations who are
looking for great business insights. So let’s begin. So now up on 1,we
have got is tableau. So what is it, now Tableau is a powerful business
intelligence tool that is being deployed by the majority of the enterprises. Now
tableau lets you distinguish the complex trend patterns and then convert them
into actionable insights. Now one can simply create Tableau dashboards in
minutes through simple applications of drag and drop of data fields. Let me also
tell you friends that you don’t really need to have any technical knowledge for
exploring and building tableau dashboards. Yes that’s correct
so it’s simply accessible on any device and the results are crystal clear for
anybody to understand and implement at any time. Now Tableau offers five main
projects. The first one is tableau desktop then server tableau online,
reader and finally tableau public. Now let us see some of the important features
of tableau. So in tableau you can simply select the data and switch between
visualizations on the fly, that is to say it is really easy to jump between your
visualizations in tableau. So tableau actually visualizes data from the very
start allowing you to see this significant right way. Now tableau also
gives the users different ways to answer questions as they investigate through
data visualization now tableau also provides
a variety of implementation and consulting services for enterprise level
deployment. It also allows users to create custom formulas that are not
available in most of the tools and finally it offers hundreds of native
connectors to easily pull, cleanse and correlate data from practically any
source without having to create custom code. So using these tabla features you can simply come up with your own
visualization that can actually ring in the cash register for any business
enterprise and hence the opportunities are really huge in this industry. So once
you on the knowledge or tableau you can simply get vast career opportunities
just like business intelligence analyst, business analyst, senior analyst or
senior Operations Analyst and then if I talk about the salary perspective then
a tableau professional can you know on up to around hundred and two thousand
dollars per annum which is so great and then next on the list we have got is
informatica. So informatica is a data integration tool based on ETL
architecture. Now informatica is named as a leader in Gartner Magic Quadrant for
data integration tools for the 11th consecutive years yes.
So it actually gathers data from various sources and then loads it into
distinctive targets then it is also strong enough to handle huge volumes of
structured or unstructured data just like flat files, databases log files etc.
It also provides data integration software and services for various
businesses, industries and government organizations including
telecommunication, healthcare, financial and insurance service and finally it is
high-performing and yet very simple for developing, maintaining, administering and hence considered as more advantages than ETL. Now features of informatica power
center are designed for the use of administrators, developers and
professionals. So informatica ETL products include the first one is
metadata manager, development capabilities a set of
productivity and visual tools and finally metadata driven architecture. So
informatica power center is being deployed by some of the biggest
corporations and hence there’s an insatiable demand for informatica
professionals. So some of the important designations offered for informatica
professionals are BI developer with informatica, informatica specialist
developer, informatica business analyst and so on. And then if I again talk about
salary then informatica developer in the United States can earn up to one hundred
and two thousand dollars per year which is not a bad start certainly.
And then third on the list we have got msbi now what is it? So msbi stands for
Microsoft business intelligence and it is one of the top business intelligence
data and mining tools so it actually helps the organization by creating
interactive dashboards and scoreboards it is also capable of producing the
quick and exact output through search engine despite heavy volumes of data. Now it also consists of tools which assist in
providing optimized solutions for business intelligence and data mining
queries and now msbi uses Visual Studio along with SQL Server which actually
empowers users to gain access to accurate and correct information for a
superior decision. So again MSBI is divided into three categories the first
one is SQL Server integration services so this is a platform for building high
performance data integration and workflow solutions including extraction,
transformation and loading operations for data warehousing. And then we have
got SQL Server analytical services. Now this is the process of converting two
dimensional or rows and columns data into the multi-dimensional data model so
it is mainly used to analyze the large volumes of data and then finally we have
got SQL Server reporting services. Now it is an enterprise reporting platform that
supports both traditional and interactive reports delivered over
the web and again it also supports both dimensional and multi-dimensional data.
So its features, growing popularity and zooming job trends. Microsoft bi are all
set to take on the world of business intelligence and is rightfully so. So
some of the job trends are ETL developer bi developer, technical developer and
msbi developer and then the average salary of an MSBI developer is around
one hundred and seven thousand dollars and then there is a continuous rise in
msbi job postings and job seekers and then we have got next tool on our list
which is Cognos eleven. So it is one of the leading technology platforms in
today’s world and Cognos analytics eleven software is an online based
business intelligence platform that offers a complete array of bi software
to address company goals. Now again it is comprised of over 30 different products
so its abilities include dashboarding, analytics reporting, score carding and
notably data integration. So it provides intuitive and immersive user experiences
mainly focused on analytics and discovery and then here data governance
and business IT collaboration provide the ability to manage its information
knowledge and to answer questions and then it has also got smarter and more
embeddable analytics Now IBM cognos allows organization to
outshine others by providing its unique features just like analytics in which
the key business questions are answered in a fraction of seconds using an AP
techniques and then collective intelligence so this is equipped with
collaboration and social networking that streamline the processes and finally
actually will insight now again it allows business people to respond to the
real-time situations and then there’s a lot of Hotaling coming into the domain
just like Cognos consultant Cognos bi manager each Cognos bi developer dream
of modular and Cognos administrator and then the average salary for IBM Cognos
analytics ranges from approximately $50,000 per year and finally on the list
we have got B I so Microsoft’s power bi is a cloud-based business analytics
service for analyzing and visualizing data so it produces creative and simple
reports and publishes them for a specific organization now using power bi
anyone can simply create personalized dashboards with a unique 360-degree view
of their business so first it will connect with a wide variety of data
sources and then shape the data according to your needs and then it
models the data using relationships calculations measures and hierarchies
also using visual tools and custom gallery you can create stunning reports
for our business all sides and finally once you create reports it publishes the
reports securely and set up an automatic data refresh
you know here are some of the features of RBI soap RBI uses content packs which
has dashboard reports data model and embedded queries not content packs are
now being used by a large number of applications including QuickBooks and
then power bi also provides a unique feature for printing dashboards exactly
which can be handy in board meetings and discussions and finally power bi is a
library of custom visualization so most of the MNCs are actually implementing
power bi which increases the job openings for power bi professionals and
then again a power bi professional can earn somewhere around ninety two
thousand dollars per year in the US and with this we come to the end of this
video so now that you know the top five BI tools that are leading the industry
do take the advantage of your career opportunities that come with the
expertise in these particular tools so upgrade your skills with EMTALA patch
online professional training programs which is one of the best elearning
platforms so you’ll get a 360 degree knowledge about the course designed by
the best of the industry experts so friends thank you so much for watching
this video and giving us your precious time for any inquiries feel free to
contact us I hope the video was informative for you please like the
video and if you have any doubts comment below
we shall respond to it at the earliest don’t forget to subscribe to our channel
for more such informative videos if you look out for other related videos in our
playlist for more detailed information visit our website now have a great day
and career ahead

Microsoft Business Applications Virtual Launch Event | October 2019

>>It’s this dual challenge of how do we help create all these
applications and then bring all the data together that’s
inspiring us to build out Power Platform and Dynamics 365 as the world’s connected
Business Cloud. [MUSIC]>>That’s one of the strengths
Microsoft helps bring to the table. It’s now on Azure and Dynamics 365 that really integrate
well with our vision. But then the knowledge
of how to apply some advanced digital techniques to data and how to utilize those platforms in a
very efficient manner. [MUSIC] We believe that customer
insights can help us get better and we can empower
the employees with that knowledge to be even more
personal perhaps our guests be more pleased. [MUSIC]>>Traditionally, mobile
software development is pricy lengthy and requires a very
specific set of skills, and through discovering
PowerApps and using the editor has helped us feel
more confident in our role, and I think it really clicked
and opened it how much better we could provide customer service to our
internal business areas. [MUSIC]>>That’s why we
selected Dynamics 365 to enable our salespeople
to better sell. After we implemented the Data
Warehouse and Dynamics 365, we had a 30 percent year
over year increase in our season ticket sales with essentially the same
team on the floor. [MUSIC]>>Every company
struggles with training. Products are much more complex. So how do you keep up? We see guides and HoloLens as a great tool to change
how adults learn. There’s video built in, there step-by-step instructions that can overlay holographic images, and so we need to have in-depth
training from a electronic mentor, we believe you’ll be up to speed
and a compressed time frame. [MUSIC]>>Data in one system is helping you optimize the outcome
of anonymous system. That’s what an AI first company does. That’s what an AI first
software product does.>>Thank you very much.
It’s my honor really to stand up today to represent the great work that’s
been done by the team, many of whom are in the audience here to show off in code and through demos with customer scenarios
all the great work that we’ve done for our 2019 release wave 2. Just stunning amounts of innovation, brand new products and services, hundreds of new capabilities. But before we get into the details, I want to just set and set
some context and if you think about our customers and the
value we’re delivering to them, how we’re helping them
transform their business, I think Chevron is a perfect example. One of the things that we’re
going to talk about today is how data is coming together to really fuel transformation all the value that one can
extract from that, and Chevron is one of the world’s largest
integrated energy companies, and data is at the center
of everything they do both in breadth and in depth. If you think about their operations, they’ve got downstream,
midstream, upstream, or they explore, they
produced, they transport, and eventually refine
all of this information. The ability to connect
the dots across the entirety of the business
left or right allows them to optimize their operations by taking one piece of
data from one part of the process and joining
that with a piece further downstream from
a depth perspective. You think about seismic exploration
or weather pattern exploration when you’re laying out
a wind farm is produces terabytes of data in a single day. The ability to harness all of that to reason over it is part and parcel of the business that they’re in and so if you look at the solution
they’ve developed, leveraging Dynamics and the
Power Platform in Azure, they selected Azure
because it provides global planet-scale
exabyte class storage to capture all of this information. But they know it’s part
of a broader platform. The Power Platform allows them
to ring value from that data. So they’ve got 600 PowerApps in
production in less than a year. They’re putting two PowerApps
in production every single day, 10,000 monthly active users
across the organization. I think the most impactful
application that they’ve built is one that takes all of this data and allows them in their exploration
and production operations to go from an 18-month cycle, from exploration to production
on a new drilling operation to six weeks using a PowerApp
that they’ve created. Now, it leverages capabilities
and Azure and it really pulls the whole stack
through, but massive impact. I think even more
impactful than that. The same PowerApp allows them in an active drilling
situation when they encounter something
that was unexpected, they used to have to recalc. It would take 24 hours. People were standing around
waiting for the recalc. They can do it almost
instantaneously now and so huge impact and with Dynamics 365. They’re leveraging Teams,
Dynamic 365 Field Service, Dynamics 365 Remote Assist, and they’ve realized their
dream of having any expert from anywhere in the world
to any other place in the world virtually
in five minutes or less. So if there’s an issue on an oil
rig out in the Gulf of Mexico, they can take someone in Houston
and virtually put them there, or they can be there
with that remote worker, they can mark up the environment
just a game-changer. But it’s not just the world’s
largest multinationals that are benefiting from
these technologies. Majans is a family owned
snack food company. It’s the largest one in
Australia, family-owned. Produce lots of very
tasty treats that I get to sample when I visit my favorite location
Australia and New Zealand. But they have transformed the
way they make snack foods, and there’s no one better to talk about how they’ve
done it then Majans. We’ve got a video. So why don’t
we go ahead and roll that.>>We get out of bed
every day to mix magic. The experience that the
consumer has has to be supreme and you have to
deliver it consistently. Dynamics 365 gives us confidence
that we can make great choices, great decisions in
creating amazing product.>>Is the minute we have
that one off experience of the salt is a little bit low or
spices a bit too high or low, it’s a competitive environment. They’ll just choose another product.>>If there’s too much moisture, can I get a bad experience. If there’s not enough, it’ll go stale and dry out
and just getting it wrong. He’s quite scientific
and amazed to be exact. At Majans, we’ve really tried
to take away the human testing and to buy IT intelligence to do that more consistently
and more accurately. We have a system now that can look
into the product in real time, which helps us control
how big the problem is, or understand where it started. People feel so empowered if I
can fix the problem themselves. Giving them the data
quickly helps them actually fixed before they
became bigger problems. The real benefit of IoT
intelligence is being able to get the best person in your organization to address the
issue that needs to be addressed. If you give good people the right
information at the right time, they can do incredible things. The industry has always been
about efficiency. Time is money. It’s not just about producing
whatever you produce fast out. It’s about how
information flows through your whole business faster that will really give you
competitive advantage.>>We are simple business. We make stuff and sell stuff, but everything in between is
so important to get right.>>A lot of times when
people eat our snack, they tell us that oh, you take us in this little
journey, it’s great, we love it. That’s the topic of emotionally
we want to get with a customer. Dynamics 365 allows you to create that journey
over and over again. [MUSIC]>>Absolutely loved that story. So let’s take that and think about how business applications play a role here and
how they’ve changed. Remote assist putting someone anywhere on the planet
in five minutes or less, connected manufacturing, terabytes of data
changing drilling times. This is not your grandfather’s
business application domain. In fact, it’s probably not
even your older brother’s or sister’s application domain and
things have changed fundamentally. If you look back and you
go back to 1970, 1990, 2010 and look at business
applications over the years, they’ve been fundamentally unchanged. This is a call center. It’s actually a TWA, airline reservation center in 1970. If you were to go stand in
there look at that screen that that reservation
agent was looking at, and pick them up and
move them to 1990, pick them up and move them to 2010, they would see more
difference in hairstyles and clothing than they would
in the applications. In 1970, its green screen or amber running on a
mainframe, in 1990, it’s probably in a fat
client on Windows maybe with a server on the backend, and in 2010, it’s a SaaS
application running in a browser, but it’s forms over data. Glorified record-keeping systems by enlarge across both CRM and ERP. The reality of that class
of application is that they were in fact largely glorified record-keeping
systems and very reactive. You think about a Field Service or customer service environment
where you’ve sold someone an asset that
they’re dependent on, Majan’s for example, using an
asset to make snack goods. It breaks, they need help. They pick up the phone they
call the manufacturer and manufacturer picks up the phone
in a support or service center, they start typing into an application what they hear from the
customer and they can roll in a very reactive way someone
to go help and maintain and get the production line back up
and running, very reactive. But that’s all we’ve ever had. There really was no other way, but something is
fundamentally changing. The fundamental change is that
data’s coming out of everything, and it’s coming first. It’s coming out of every operating
room, retail environment. Every time someone lands
a jet on a runway at Heathrow it uploads information
from the jet engine. Everything is producing data. This data first reality allows us to go from this very reactive model
of business to a proactive model. Literally flips the script. It’s not open an app, type stuff in, report, its collect data, reason over it, predict, proact, complete reversal. In order to do that, you need a completely different
class of business application. Now, if you look across the
business environment functionally, data’s flowing from everything, from your customers,
from your assets, from your people every
time someone updates their LinkedIn profile
has a Teams meeting, every time a customer
comes to your website, uses an application, uses one of your connected
products every time an asset in a manufacturing
facility produces a product. All of these sort of four parts of your business
are producing data. If you can harness that data, rationalize it, harmonize it, reason over it collectively, you’re in a position now to understand your
customers, your products, the performance of
your assets and your being you can use that
point of view to go intelligently engage proactively
through understanding. That of course, produces
even more data that leads to clear understanding and it plays out across the
entirety of the business. We call this a digital feedback
loop and it represents this opportunity in
a very compact way, data flowing from
everything capture at harmonized reason intelligently act. This vision on this emergent reality that data’s coming
out of it if they had driven everything that we’ve built. So let’s look at what’s required in order to go take advantage
of this opportunity. I never ever talk about Dynamics 365 or the Power Platform in a vacuum. It’s always part of a
larger Microsoft story because that’s what
really sets us apart. You think about the story we
told with Majan’s or Chevron. It starts with data. The ability to capture information. To harmonize it. To reason over it collectively is at the base of
everything that we’re doing. Exabyte class storage capability and the world’s largest public Cloud, more regions in Azure than
Google and AWS combined. So this footprint that
we’ve created planet-scale allows us to bring all
of the signal together. Then of course you’ve
got a reason over it. Decades of primary research in MSR, hardened at scale
across Bing, Xbox Live, Office 365, MSN creates an intelligence layer
that allows us to take that data and
turn it into insights. The application
platform in Azure takes that intelligence turns it into
intelligent action on top of that. We’ve built the Power Platform. The world doesn’t have
as many programmers and data scientists and
technologists that we all need. So the Power Platform allows even non-professional technologists
to connect with data, build applications, automate
business processes on top of that. We build Office 365, Dynamics 365. Sister services, families that integrate
with one another and provide the industries
only comprehensive left to right collection
of business applications both unstructured and
structured communicate, collaborate, create with Office, marketing sales service operations finance and talent automation
with Dynamics 365, but built to work together. Then on top of that, tens of thousands of ISVs
have built applications for specific industries or geographies available in App source
built on this platform. Now, the important thing is all of this stuff was built
to work together. When you start with Dynamics 365, it stores your data in a place and in a form that Azure understands, that the Power Platform understands, that Office 365 understands. This organic creation of a unified holistic
platform centered on data, powered by intelligence
is what we’ve provided. So with that context, we’re going to spend the next
hour and 15 minutes or so talking about all the innovation
that we’ve delivered yet again. We’re doing this every six months. In the last six months, we’ve created over 400 new
capabilities in Dynamics 365, we’ve introduced multiple
new products and services, and we’re just continuing
to turn the crank and to innovate guided
by this vision that we just talked about enabled through this collection of assets
that we think is unique to Microsoft and is really made
an impact for our customers. So the first area we’re going to look at is our
Customer Data Platform, CDP. So this is an area that I would argue is perhaps the most
important data of all, truly understanding your customer
from every point of view how they’re using your products and services, harmonizing
that information. To show you in more detail, I’m going to have Satish
and Lydia come up talk about these capabilities and
to demo the product. Satish.>>Thank you, James. So today, what I wanted to talk about was
today customer data is coming from a lot of places and
from a myriad of sources. Typically, once a product is sold, how those products and services are used is not very well
known by the company. Now, imagine a world where you can
actually bring together all of this customer data including
real-time product usage data, be able to harmonize it, do AI, derive Intelligent Insights
on top of it for you to be able to deliver exceptional
personalized experiences. That’s exactly what we’ve set out to build and make real
for our customers. So today, I’m super-excited
share more about Microsoft’s customer data
platform and the product and services that make up
and help you build that 360 view of the customer
like no other company can. Now at the tip of the sphere is Dynamics 365 Customer Insights
and Product Insights. Together. These products
are designed to give you a holistic understanding of
your individual customers, how your customers are interacting
with your products and services so that you can derive intelligent segments on
top then drive action. Now, all of this is very differentiated because
of the fact that it’s built on top of Microsoft’s
depth of data processing, breadth of data connectors
that allow you to bring in all of that
data unified at scale, enriched with Microsoft
proprietary signals and provides the ingredients for
you to be able to go deliver those personalized experiences and transform your products be it in Dynamics 365 to the Power Platform or any other third party
application that your business uses that may be using. So with that, I want to actually
show you an example of how this comes to life in terms of a data first comprehensive
view of your customer. In this point, I want to
talk about three things. The first thing is
as you can see here, it shows the customer information that was previously
in siloed sources. In addition to that, we also enrich that
customer profile at an aggregated level with specific information from
the Microsoft Graph. So that includes things
like brand affinity and interests about that customer
and people like that customer. Now, this specifically this part is only possible by one or two
companies on planet Earth. On top of that, we’re
also able to show you how the customer interacts
with your product and services, and together, this gives you the most
comprehensive view of the customer with which you can go move your business for
bead to drive up-sell, reduce churn, or drive loyalty up. So everything that I showed
you here is possible when your customer is an
individual, but that’s not all. As part of this release, we’re also enabling
our B2B scenarios, which allows you to do
exactly the same and more if your customer is a business. Now, to show you that
in action in a customer that’s actually using
that functionality today, let’s roll the video for
American Electric Power.>>Our AEP energy is energy
solutions company that we have over 400,000 customer accounts
stretching everywhere from residential to small business
to commercial industrial.>>As our suite of services expands, we don’t really have the tools
in place right now to match emerging technologies to
emerging customer segments. We’ve got a lot of customers,
we’ve got a lot of data, and we’ve got a lot of
data about our customers.>>We not only have that data from accounts,
opportunities, contacts, but we also have legacy ERP information that we want
to utilize and so that can be anything from contract information
to pre CRM information as well. Life before Customer Insights we had a lot of manual processes and so a salesperson would have to have multiple systems piece them together to actually get the
full picture of a customer. Using Customer Insights,
we can actually migrate that big group of data into
our Dynamics 365 platform and see that we went from
having all these duplicate accounts to now we have one
profile for each specific account. If we’re competing
with another supplier, we have information that can
help us actually provide maybe a better or similar product or service that might just give us the edge for what
that customer needs.>>If you boil energy down to its simplest form, we’re
selling electrons. So it’s more about
how do we engage with customers around that
sale of electrons.>>The Microsoft platform as a whole can actually
help us make sure that those salespeople that need to make split-second decisions have the right information
at their fingertips.>>Customer Insights
will help us both with our customers we have today and satisfying them better
and our metrics and objectives around
the customer experience, but also help us identify gaps in our products and services or segments that we haven’t
been able to serve.>>For our customer service team, when somebody calls in, we can provide them with
the information they need or if there are
potential new customer, we could provide that concentrative
service or we can ask them the right questions and then provide them with a better product.>>The promise of customer
insights is that it can make from the very front end to the back-end
more efficient, more focused.>>It will help us
get more customers, keep the customers we have
and have them more satisfied.>>Great. Cool. So with that, I’m actually going to show
you exactly what AEP was able to do in the demo
right in the product. Perfect. So what
you’re seeing here is Dynamics 365 Customer Insights and I’m going to walk
through three key personas. The first one is the data analyst at AEP that basically brings
in all of this data, unifies it and then the business
analyst who’s able to take that unified profiles segment on top of the discover create
new segments and finally, the business user who’s
able to take this data, consume it in their business process. So in this scenario, as we saw there, the piece was to bring together data from a bunch
of myriad of sources. In this case, they had
data sitting in Dynamics. A custom system that contained enrollment less opportunities
and survey data. So business always growing. So it’s not just the data
that they already brought in. You can actually bring
in new data and this is where the the rich set
of connectors come in. So you’ll notice that we have
connectors for obviously from various databases,
Salesforce, SAP, etc. So the whole goal is you can bring customer data together from wherever it might be sitting and that is key. The next thing obviously is once you’ve brought
in all of the data, how do you basically unify the data? So the first thing that comes to
mind is how do you map the data? So this is where you’re able
to basically bring all of that previously siloed data
and we’re able to detect automatically what type of
data is contained in there. So things like name, address,
firstName, lastName. So this is a lot of
Microsoft research work that we’ve productized right here. So this used to be a very
time-consuming activity before and in this case, usually you can just
default your way through. The next thing that happens is
obviously the matching capability. So this is where, it’s all about creating keys
where keys don’t exist. It’s coming from various system. So here we give you an
ability to basically, with a configuration type experience, you can tie together and guide
the system in terms of “Hey, how do I map the telephones? Do you want an exact match or do you want a medium precision match?” So the goal here is
depending on your use case, be it finance or marketing, you might choose to go to different sides of the
precision scale here. Again, a very
configurable experience. No need for system integrator
and a lot of custom jobs. It is just very configuring
and out of the box here. The next thing is obviously the merge pieces which I
won’t go into detail here. But essentially, every time
your data changes, it comes in, the unification runs and
it makes it available in an Azure Data Lake which
is there securely where you can actually access it
through our connectors or through our Power Platform
connectors and APIs as well. So now, I’m actually
going to walk into, assume that we’ve got all
of this data now unified, I’m able to segment all of this data. So what this means is on top of
that, previously siloed data, I’m able to build a
segment and basically detect who are the customers
that I have today, from all these various sources, that have a high propensity to buy these green services as
you saw in the video? So in this case, I’m building
a segment of customers that might be interested and not
currently using PeakAdvisory, PowerPerks, Demand
Management customized, and personalized energy segments. So what you’re able to
do is you able to take that segment and bring
it out into PowerBI. So this is where I never
talk about Customer Insights or Product Insights without the
Power Platform integration. So here, what you’re looking at is how AP was able to take everything in Customer Insights and build a powerful PowerBI report on top of it so that
they can analyze it, slice and dice it, figure out what the key influences are and more
important in this scenario, detect which are the
customers that have highest propensity to
buy the green services. So here you can see, you have the lifetime
value churn score. I’m able to figure out who my top potential customers for
this service and then finally, I’m going to switch into
a salesperson scenario. So this is that individual
that actually goes into a company which is typically the customer prospect and basically tries to sell this to them or at least proposed it to
them and this is where you you’ll notice that they’ve
done this with a PowerApp. So in this case, Microsoft
Store is actually a business customer for AP. But more importantly,
that salesperson is able to see a full 360 view of the customer in this PowerApp that was built on top of that
Customer Insights’ data. So you’ve got the address here. You’ve got that activity
that’s coming in from various sources,not just one sources, all tied together by
Customer Insights. You can see some KPIs
and more importantly, you can see some AI that was done
on top of that unified view. So this is the next best action
that is being recommended to the salesperson as they’re interacting with that customer
at the customer site. So with all of that, you
are able to see how are you able to bring in customer
data from all your sources, unify it, do segmentation
on top of it, and take that segment output to be able to drive business processes, be it through the Power Platform, PowerBI for deep analysis, PowerApps for building
custom applications even Microsoft Flow for building
Customer Journey Orchestration. So with that, I’m going to
hand off to Lydia to talk about the second key piece of
this Customer Data Platform which is Product Insights and how you can enrich this customer profile with how you customers are
interacting with your products and services. Take it away Lydia>>Historically, whenever
customers purchase a product, the interaction with
the company they buy from ends the moment
they walk out the door. We don’t understand why
or how they using it and oftentimes the only interaction comes when something has gone wrong. As James mentioned, today, we’re able to capture data from
these millions of devices. However, the sheer quantity
of the data is too large for humans to
be able to analyze, meaning we cannot deliver personalized actionable
insights for our customers. At Microsoft, we’re transforming that experience using
Product Insights. For the first time ever, we are able to be with
our customers where they are actually using the products. We can understand
who the customer is, how they are specifically using
the products by consuming product usage data and
we can then unlock this data and produce
those actionable insights. Product Insights is the
commercialization of something we’ve built and been using
in Microsoft for years. It’s a high scale system
that’s very mature, 25 million peak
transactions per second, analyzing the use of over two
billion connected devices. This is an upscale service that’s allowed Microsoft to understand how our customers are
using our products and services across XBox Live, Office 365, Bing, Dynamics 365 and we’re now offering
this to our customers. Let’s look at this from
the perspective of Ecolab. Ecolab are a global
organization who produce a vast quantity of water hygiene and energy
products for businesses. Ecolab wants to be
the world leader in eco-friendly devices
and a key elements of this is an excellent
customer experience. Product Insights is taking data from thousands of products
that customers are using in the field for example large
quantities of dishwashers in commercial restaurants and
turning it into actionable insights. As a Product Manager for Ecolab, I start to interact with Product
Insights. Let’s take a look.>>The sheer quantity of
data available means I don’t know which area of
the business to focus on. Product Insights is consumed product usage data for all
of the devices and is now directing me to the anomalies
that fall outside of how we expect our products to
be used by the customers. We can see on screen here
that Smart Advisor has highlighted that for some
reason, you see here over here, when our business customers are using the normal dishwasher cycle
in commercial restaurants, they’re actually using more
water than the heavy cycle. This pattern makes no sense, and I want to understand why. For the first time, I’m being provided with
the unlocked insights I need to understand
who my customer is. Before using Product Insights, we would only know who
had purchased the device. But now these analytics
can show me where my customers are based
as well as giving me a complete 360 view
of the products they’re using and crucially how
they’re using them. For this anomaly, I want
to dive in one level further and get to the specific
feature we’re focusing on, water usage and drainage. An anomaly occurring doesn’t necessarily mean there’s a
problem with the product. It might be related to the way
our customers are using it. Here, we can see an aggregated
view of all of my customers, but I want to go deeper and identify real customers experiencing this. Product Insights has
intelligently identified the particular customer
who has faced this issue. I’m able to see detailed metrics. We can see who the customer is, when they’re using the dishwasher, and when the issues are occurring. In our first scenario, the issue is being
caused due to the way the customer is using the dishwasher. Equipped with this knowledge, our team can now proactively
notify the customer of this challenge and educate them about how they can
improve their usage. For the commercial customers,
we have an Ecolab. This is crucial to enable
them to continue to work effectively day in and day out. As a customer, they’re receiving a proactive personalized service that results in an improved
experience with our washer, will enable them to continue to
run their washes effectively, save money on excess water usage, and avoid future problems. In the second scenario, this anomaly could be
related to a fault with the dishwasher that over time will result with a fault with the machine. Historically, we would behave very reactively and we wouldn’t
know about this problem until the customer has actually
faced some pain and has to call us to tell has of an issue
and request a repair visit. Using Product Insights,
we’re able to change this experience and start
to behave proactively. Product Insights work seamlessly with Dynamics 365 Field Service and automatically produces a
case for our engineers. Real-time customer-specific
insights are presented to the engineers directly
within Field Service, and the engineers can
then use this information to determine a proactive
best path of action. Our engineers are
able to successfully deliver a highly
personalized experience for our customer as well as avoiding any problems
with the dishwasher, driving increased
loyalty to our products. Furthermore, when we’re out
doing the Field Service cool, based on a clear understanding
of their usage and the ability to compare it to how
similar customers are using our products and services, they can now suggest
additional products that the customer could benefit from. So what’s the end result for Ecolab? Because they now have
this deep insight into the actual usage of their
products and services, as well as a deep understanding
of their customers, they can move from
selling dishwashers to selling clear dishes as a service. They can pivot their
entire business model. Today, we’ve seen how
using Product Insights. For the first time, we’ve been able to proactively
detect an anomaly, and then work to resolve this challenge before it
affects the customer, transforming their experience
with our products. What’s crucial to
highlight is that it’s the combination of customer
insights and Product Insights together that gives businesses a deeper understanding of who
their customer is and exactly how they’re using the devices
enabling them to transform the experience the customer has from the day they purchased
one of their products. Thanks very much. I’ll
now hand over to Linda.>>Thank you, Lydia. Brands are currently faced with the challenge. We as consumers have an expectation from companies
that they know who we are and they know how to interact with us and when to interact with us. Over a third of customers who have
interacted with a brand and had a bad experience will never do business with that
company ever again, which is why it’s more important than ever for companies to get this right. Consumers will do their
research on products, they will get offers
on those products, buy them, and then expect
exceptional customer service. Dynamics 365 is able
to help this problem with a common data
service at the heart of all of our customer
engagement applications. So across marketing, sales,
and customer service, we’re able to give a
consistent view of that customer because it’s
all on the same platform. I’m going to walk you through what we would call the
customer journey today. So from when a customer
is engaging with the marketing campaign
or when they buy that product and then they
expect that customer service, we’re able to take
the data and create proactive next best actions so that you can serve your
customer the best that you can. We worked closely with
customers on building out the right capabilities to
build rich content in e-mails, and also being able to
test that content to make sure that you’re
getting the right message across to your customer. ACTUM Digital is a customer that
we worked very closely with. ACTUM Digital helps their customers go through their digital
transformation journey. Many companies who go through digital transformation
do it in stages. Thanks to Dynamics 365 marketing, ACTUM Digital was able to increase their customer interactions with engagements through
events and automation. So let’s take a look at Dynamics
365 Marketing in more detail. Before I go into
Dynamics 365 Marketing, I do want to show you that we are in Customer Insights and we already have built some segments on what those customers are that we
want to invite to an event. You can see that I
have a retail digital transformation summit
segment already created. Now, if I go over to
Dynamics 365 Marketing, here it is, I can
show you that this is the same exact segment that we
had built in Customer Insights. We can take a look at all
of those customers that got fed over into Dynamics 365 Marketing. Back in this journey, we can see that there was
an e-mail that was created. We can take a look at this
e-mail in more detail. Here, we have a rich content
editor where I can edit in-line. We also have slugs for pulling in the information from the customer. You can also see that
there’s something over here with “Version
A” and “Version B”. This is AB testing, and it gives me the ability to test out different versions
of the subject. So you can see that maybe
one subject will be more powerful in helping
our customers want to click on that e-mail and open it. Taking a closer look at
how that would work is whichever I have set up here, whichever message reaches
10 percent threshold first will take over
for that campaign, and that will be the winner that goes through the rest
of the e-mail sent. Another important thing that
I’d like to point out is that we can use sales
as a channel as well. So let’s say that our customers
did not open the e-mail. We can send a person to go and talk to that
customer and reach out. So we can treat sales as if they’re an additional channel for
reaching out to customers. Speaking of sales, let’s take
a look at the next step in our customer journey where we are actually engaging with
customers face to face. So when we think about the Wave 2, and what’s really important in
the sales application is that we are bringing guided selling
to the application. So listening to the signals
that are coming from that data, we’re able to bring guided
intelligent selling to the Sales Rep. This is all done with
our assistant Studio. Even better, we can bring
that to our mobile device, which I will show you, that the Rep can take on the go. So they’re always prepared
with the next best insights. We worked closely with Sandvik who is a high-tech global
engineering organization that builds manufacturing tools. Sandvik has Sales
Reps who are visiting their customers face to
face on a regular basis. Sandvik and Microsoft Dynamics
built an app that helps their Sales Rep on the go be able to talk to their customers
with relevant content. So let’s go over to my mobile device and I’ll show you
what this looks like. So here I am in my Mobile App and at the beginning of
the day I like to see what meetings that I have, and who I should be talking to. We can see that here are all of
the meetings being pulled through, but we also have some
really great content here with the account from Dynamics
linked into this meeting. I have my account VanArsdel and I also have my contact Nancy Anderson. If I drill into this meeting, what’s really powerful here is I have all of the relevant information
right at my fingertips. I can see who this customer is. Then also at the bottom
we have related insights. So I know that this
opportunity is at risk, and the close date is coming up. So when I meet with this customer, I know that this is
important information. We also can bubble up other insights which you can see on
the Homepage here, to really help that seller be the most effective that
they can be that day. Another great feature that
we have in this release, is the ability to scan and note. When I was meeting with my customer, I took some notes on paper. I love paper, and I like to take
my notes with pen and paper. Often I don’t have that
tied to my application. So I lose the contexts the next
time I’m meeting with my customer. Now with the next release, we’re able to scan notes
from the mobile device, and now it’s processing through Azure Cognitive Services
recognizing the text. This will be available
in multiple languages, and it recognizes all
of the information and processes it as an OCR, and allows me to upload this note to the meeting which then I can use. As you can see, it did it perfectly. I can suggest these updates
if I wanted to edit. So this is a really great feature, but what I want to show you is
how these insights were created. So going over to the desktop, I want to talk a little bit
about the Assistant Studio. The Assistant Studio is a
really powerful tool that Sales Operations users
can use to create cards for these insights
to appear not only on Web, but also as you saw on Mobile. Here we can see as I
mouse over these cards, I get a preview of exactly how the Sales Rep is
going to see this card. If I click on this, it gives
me the ability to configure the card and also I can set it up. So only certain Sales
Reps can see the card. So I’ve got multiple teams. I can configure this at
a very granular level. The other really great thing is we built all of this on top of Flow. So you get the power of Flow. I can drill into this card and see all of the ways and why
it appeared when it did. Since Dynamics 365
is really helping in that next step in the
customer journey for sales, but once you do sell that product, you want to make sure they
get a great experience with Customer Service. So let’s talk a little
bit about what’s coming in the wave two
for Customer Service. Customer Service Agents are
sitting in a Call Center with many different ways of
customers reaching out to them. So in this release,
we’re bringing you this great capability and balancing many different channels
of incoming texts and phone calls through our
capability called Omni-Channel. We worked closely with a
customer, BYU Pathway. BYU Pathway is a global
education online company that serves over 70,000
members worldwide. BYU Pathway wanted
to be able to bring the best possible service
to their customer, which is actually a student. So in this case, I’m going to
walk you through a demo of how a student would reach out and
interact with BYU Pathway. So here I am in my Dashboard, so I as a Customer Service
Agent have a lot going on. There’s a lot of work
that I need to do today, and it gives me everything at a quick glance of what
I need to focus on, what my activities are, and what my active cases are. Now BYU Pathway has a website that
has a Chatbot enabled on here. So there’s live chat support. Let’s say that I’m a student and I want to know what
my tuition is due. I’m interacting right now
with an automated Bot, and it’s telling me some really great information
about when my tuition is due. It’s giving me a link to
more information from a FAQ. Yes this is helpful, and it wants to know if I
need any of their help. I missed the deadline for fall
semester and I need some help. What’s happening now is, it’s telling me that an agent
will be with me in a moment. You can see that the chat
request is coming in. I can accept this as an agent, and what’s happening right now is, it recognized who this customer was. It loaded up Mae Gibbs. It knew that I was the
student Mae Gibbs, and it also loaded the chat that
already happened with that Bot. Instead of having to
read all of that, we also give you a
nice issue summary. So it’s summarized the
entire conversation, told me the sentiment of the
student that slightly positive. I can also respond
with quick responses. Now when I’m chatting
with the student, I can also chat with
them in other ways. If I go over to Facebook, I also can interact the same exact way that
I did from the Website. So I can interact and say, “Hello”. Here we can see it would pop up as
another Channel and here it is. I can accept that Channel and start interacting with that
student as well. Now what is most important
to point out here is that, this is a multi-channel session. So I can have many chats
going on at the same time, as well as phone calls. So if someone is calling
me on their phone, this would also pop up
as an incoming request, and I can accept that, and have a phone call and multiple chats going
on at the same time. We are very excited
to bring this to you, and our Wave 2 release. With that, I’m going to
hand it over to Philippe. Now who’s going to talk about
Virtual Agents and how this will help that Virtual Chat
work even better. Thanks.>>Thank you very much, Linda
for that great transition. So today I’m going to talk
about our exciting new release of our Dynamics 365 Azure
Agent for Customer Service. So in that concept, we are bringing three
principles to bear. Number one, simplicity. We want to make it easy
for Customer Service, Business Analyst to
build chop up quickly. We do that by using
a No Code Approach. Number 2, we want to bring
personalization and speed. So with that, we can offer
personalized experience to your customer and
making sure you have the right solution at the right time. The third is about extensibility, and that we’re basically going
beyond conversational search. Beyond the simple answer. We want to be able for
your Virtual Agent to act on behalf of your customer. With those principles in mind, we’ve been working with TruGreen, one of our great partners
today to help them change their business and get into a
different experience with the brand. Three things we’re looking
at improving with TruGreen. Number 1 is, reducing call handling time by operating with Virtual Agent and offering a way for
customers to directly engage with their solution at the
right time, at the right moment. Second is, about improving
customer satisfaction due to an accurate and fast
response to their question. Lastly, to improve employee
satisfaction overall by offering the Virtual Agent
the ability to deal with the routine task while the Customer Service
Representative can spend more time with tougher
conversation with the customer. Help them where were
more complex task. So let’s look at the video. I’m going to show you two
scenarios in that video. Number one, I’m going to show you the customer experience when you
go onto the TruGreen website, and how is it easy for me
to actually interact with that Virtual Agent and get
things done in a quick manner. Second, we’re going to look at the Customer Service Business
Analysts experience. Where you see how easy it
is for me using No Code just a very friendly UI to change and engage my customer
with the different dialogue, and think about what
matters most for me. Which is the content and the
experience. So let’s do that. So now, as you can see on my website and here I have my virtual
agents nicely tucked in. I’m going to look at one thing. So I’m Rose and I’m looking to get some information about my account. So looking at my accounts, I want to know my balance. It’s been a while and I just want to make sure my
finance are in order. Now, the bot understand
that I want to manage my account and offer me with different options for me
to look into very quickly. So let’s look at the account balance. Now, I’m going to have another
level of confirmation. For the sake of demonstration, let’s use that phone number
to make it easy for me. Now, what the virtual
agent does is actually retrieving my formation
in the back-end system, in the ERP system of record, and retrieve that information
and serve this to me, Rose, so I can know that at the moment, my current balance is $44. Now with that, I can offer the
next level of information. Typically, when customers in
TruGreen ask for their balance, they also are curious about
when is the next service. So as you can see now, the bot can actually
give me that option. I can select what is the
next day self-service. Now, I have another
level of information, which is your service
was going to be lawn, will actually be done
next week at 10:00 AM. On top of that, I can
have additional articles, additional information I want to feed my customer or
share with my customer. Personally, I like to know
what happen on my lawn. When they say just do a service on my lawn.
What kind of chemicals? What kind of operation
are you doing on my lawn? This is where actually you can give that additional
information to your customer. Now, I’m happy customer, so I’m going to answer yes to that question and then you
improve the overall Seasat. So that was the customer experience. Now, let’s look at the customer service business
analyst point of view. As you can see, we have a very
fairly your high here where I can look into different dialogues. Now, in that specific scenario, I am a customer service
business analyst and I’m troubleshooting one
of the dialogue or solution I would like
to put on my bot. So let’s look at this one. So please remember that I just
toggle that trigger here tracing. So they will give me the ability
to actually see in real time what my bot is actually answering me in the
context of the dialogue. So as you can see in green, all the things we
actually hit already and you can see what kind of
bugs that you’re looking for. So here, I’m going to talk
about the Chinch bug. I want a bit more
information about that. Here, I’m going to have to look at the answer that is
given to me about the bug. So the bot actually
retrieve information from TruGreen knowledge
base back-end system and hand it over to me as a customer. Now I have the full information. But what’s important for me
as a customer is that to know about this bug or is
actually to take care of it. So this is where as a
customer service specialist, I can change my dialogue. Here, I’m offered
another option which is now I’m open up to schedule
an appointment for you. Again, the back-end system will offer you the next
appointment available, where technician is
going to be Peter B, and it’s going to be next couple
of weeks from now, 2:00 PM. Does that work for you?
Yes, I would like that. So now, the virtual agent booked the appointment
for me, confirmed for me, get an e-mail confirmation
to my mailbox, and now I’m fully empowered as
a customer to check on bugs, get the appointment
that works for me. As a customer service
business analyst, I can actually change those
dialogue very easily, publish them, and change
the perception of my brain on the quickly
basis few minutes only. So as you can see here, very easy concept to bring to bear. Bringing all the complexity of back-end system integration
into one motion. The extension piece here that
would be interesting for us to see here is how do we make this work? How do we make the
extensibility work? The back-end here relies upon our
integration with Microsoft Flow. So we’re able now to connect
to all your back-end system, all your system of record, to bring that information
and truly make the virtual agent working
for your customer. So I have one question
before I leave you. What kind of virtual agent
are you going to build today? Now, I’ll hand it over to Muhammad, who is going to show
you some great new apps in the operational world. Thank you.>>Thank you Philippe. Thank you Linda. It’s some really amazing innovation coming out of our
customer engagement apps and we’ve got an equally
amazing setup innovation coming in our operations apps. A little bit even more amazing
but in full transparency, I could be a little biased
given my role at Microsoft. But just to remind you, in the operations space,
in the operations app, we actually cover a
very diverse set of operational processes that
you can run on Dynamics. All the way from being able to
run complex supply chain and manufacturing operations
to retail operations, to project service
organizations and operations, to your horizontal and
core operational processes like finance and human
resources as well. We also have an app called
Business Central that allows SMB’s to run their operations
as well on Dynamics 365. Now, unfortunately, we’re not
going to be able to look at all the capabilities in all the operationals app in
the few minutes that I have. We’re also not going to be
able to look at some of the capabilities in all the
operational apps we have. So what we’re only
going to do is just look at some of the capabilities in some of the operational apps in the next few minutes that we have. But I would highly
encourage you to look at the Release Plan
document that actually, in fairly excruciating detail, lays out the innovation
that we’ve got backed into all the operations apps
for our Wave 2 2019. We’re going to start our trek
through the Operations app in Dynamics 365 Supply
Chain Management, which up until about 10 days ago alongside Dynamics 365 for Finance, was also affectionately known as Dynamics 365 for Finance
and Operations or F&O. So Supply Chain Management
and Finance is what was 10 days ago known as
Finance and Operations as well. But let’s look at Supply
Chain Management. In Supply Chain Management, we allow our customers to run end-to-end supply chain
operations on Dynamics 365. All the way from product
information management, to planning, to
inventory, and logistics, to running complex discreet process or lean manufacturing operations, to now Asset Management
as well in Dynamics 365. So we truly provide that end-to-end supply chain management
core operational processes, and we’re pleased to
announce that we’re actually innovating across all of those supply chain pillars in
our Wave 2 Application Release. So let’s quickly take a run through what we’re doing in
Supply Chain Management. We’re pleased to announce
that with Wave 2, we’re putting our planning
optimization service in preview. This essentially takes a
process that historically is a multi-hour overnight
process that customers run, essentially in any ERP
but also in Dynamics 365, to figure out what is
the plans or supply plan you’re going to need to go over, how much orders to ship, where and to what warehouse
and to what locations? We’re pleased to announce
that with Wave 2, we have now an in-memory service that allows you to run your plans, essentially in minutes,
if not seconds, whenever you want to run
it throughout the day. For one of our customers in Sweden, they used to run their
plans overnight and that allowed them to ship orders once a day to where they
needed to send it. But with now the new
planning servers, they actually run the
plans multiple times a day and ship the orders
multiple times a day. That allows them to
be able to fulfill customer orders as much more
quickly than they used to, which was once a day,
as well as reduce their inventory carrying costs
in different locations as well, which they otherwise had to stock to make sure they can meet
that customer demand. So it gives them holistic
set of benefits with the planning optimization
servers that we now have in preview
for customers to try. On the trade and logistics side, we’ve made significant improvements
on the inventory side. But the thing we’re
excited about is we’ve completed the integration
of the IP that we acquired last year from one of our most popular ISV solutions in a warehouse management and
transportation management. We brought that advanced
set of capabilities now for warehouse management and
transportation management natively in our supply chain
management application that allows our customers to now run fairly sophisticated and
complex warehouse and logistics processes in Dynamics
365 Supply Chain Management Moving on to manufacturing. This is really where,
if you go back to what James was talking about at
the beginning of the session, we’re really fundamentally
changing processes, where we’re taking processes
that have historically been very reactive to now being proactive. So with sensors planted
on shop floor equipment, you get real-time signals coming into Dynamics through Azure IoT Hub, that allows you now to
take significant amount of proactive actions on processes. Historically, were fairly
reactive processes like being able to manage quality and
a fairly proactive basis, being able to predict
downtown when machine health on what’s producing and what’s
going through your shop floor, and as well as driving
automation in just data capture across your manufacturing
process if you will. That services now in preview as
well for our customers to try. The thing we’re excited about
with IoT intelligence is not that you’ve got the sensor and the signal coming through
IoT Hub to Dynamics 365, but the fact that we’ve allowed you to set up and consume
this experience in a highly configurable way that allows you to just get up and
running in literally five minutes, if you’ve got the sensor
hooked up to IoT Hub, and we’ll actually going
to show you that in a few minutes and how that works. Again, in supply chain coming
back to asset management, asset management has been one of the top three most
requested capability from our customers and Dynamics 365, and we’re super pleased to announce
that with our October wave, we are now putting our asset
management capability, making that generally
available for our customers to try and use with Dynamic
365 for supply chain. So to show the innovation we’ve got backed into Dynamics
365 for supply chain, I’m going to have Kevin
come in here and walk you through the behind
the scenes part of the video you saw when
James was presenting about Majan’s who’s really building
some really tasty snacks, but how does IoT
intelligence really deliver significant amount of value on
top of their processes? Kevin.>>Thank you. Majan’s,
who we saw earlier, take great pride in using the finest cooking techniques and they’ve applied that mindset to their production where
they’ve taken IoT data, and they’ve made it
a proactive tool in conjunction with our new IoT
intelligence capabilities, and they span a host of different scenarios
from production delays, the quality of the chips
that they’re cooking, fruits who hasn’t machine
fundamentally broken down, and in each case, we have a very simplified process of a wizard that helps connect
those IoT notifications, directly through to
production business process. So in my case, I’ve got a wizard
here that I can click through the individual steps
connecting to the processes. I can even enable an ability of time for a local machine operator
to perhaps fix a machine, clear machine, before we
need to escalate further. If we do need to escalate further, the trigger for that
really is going to be from a perspective of the
machine operator’s view, and they’re already going to
be monitoring the machine, they’re going to get a
host time-series data. Visually, we’re
immediately giving them that clue that something is
wrong with the red background, that they need to go
and fix something. So in my case, the chip
mixer stop producing. So as a machine operator,
I’ve got a period of time. I can go and fix the
machine, if I can’t, I can dismiss it and
that’ll get escalated up. They’ll form an escalation
in the factors perhaps via an automated
business notification, through to perhaps new asset
management capability, where a maintenance
request has been created. Now, that maintenance
request is also the trigger to really send a technician to
that machine and get it fixed. But asset management
goes beyond that. It’s a way of helping our
customers, like Majan’s, manage and really improve the efficiency of their
production facilities. We can start help drive
additional insights as well. So when I’m looking at just,
say, the maintenance requests, I’ve got PowerBI embedded
directly within, and within this, I can start to look at it from my
perspective of insights of data. That will be here.
Switch to a backup. Now, the insights of data
is looking across all of my assets in terms of the data that’s going
to appear in and just looking at all
individual asset machines, through to the individual machinery, and would have driven through
an additional insight, that’s just catching up
with us this very moment. On the bottom right-hand
corner, we can see, if I’m looking at it from
a mechanical perspective, mechanics is the issue
that’s across everywhere. But if I was to them focus
back in on the chip Mixer, then electricians is the
insight that it’s driving through to us that we can
perhaps focusing further. All of this comes together to help
companies like Majan’s continue to deliver the chips
and the magic that’s in those chips. Thank you.>>Thank you, Kevin. A great
example again on how we’re fundamentally changing
business processes from being what used to be
reactive and proactive again, within the context of the
end user as opposed to something that really requires
a significant amount of development effort or
data scientists really going to get the value out from
an organization standpoint. While we’re adding
significant capability in the application and the thing
that we’re also hyper-focused on from a Microsoft
perspective is really listening to the end users of our applications and what’s
the feedback that they’re providing us from a productivity
and efficiency perspective, and I’m really pleased to announce three capabilities that we’re
adding in Wave 2 you that really is focused on increasing
the delight factor for our end users and
the productivity and the efficiency and how they
interact with our applications. The first one being saved views of folks who are
familiar with using ERP, you’re typically faced with forms that are pretty darn
complex and have a lot of fields because it tries to address a lot of different industries
and it becomes super complicated for end users to either click through multiple fields
to figure out where is it, that they actually need to
interact with the application. I’m pleased to announce we’ve had some fairly robust
personalization capabilities, but in Wave 2, we’re releasing
what we call Saved Views, where users can really save, take a very complicated form, save it down to exactly
just what they need, and use that to really drive and increase their productivity
and efficiency across the breadth of the operations
app landscape, if you will. Users can do that on their own. Users can share that as well as
organizations can do that for their users and share that at
scale to all of their users. The second capability
again in the same theme of productivity and
efficiency that we’re bringing in is enhanced grids, which allows you to really sort and reorder the columns to what
again what you would like and allows you to see some
grouping real time in the columns that you have as well as it gives you an infinite
scrolling experience, if you’re interacting with large datasets with a lot
of our large customers do. So instead of if what
you’re used to typically on a web browser if you’re looking
at longer lists on screens, a little bit of lag as you go down to refreshes and brings back
the next set of record. We now have what we call essentially infinite
scrolling that allows you to interact with that dataset in
a highly performing fashion. Then finally, Kevin touched on it a little bit in his session
but we’re continuing to enhance the Analytical
Workspaces that are available across our operations app, that allow you to interact and explore the data as well as
using the gestures capability, allow you to go back to the
specific form, the filtered form, or the form where you need
to take action upon the data based on what you’re seeing in your Analytical workspaces as well. So a lot of focus again, directly listening to feedback
that our end users provide through our in-app survey that comes up every so frequently
for our end users. We literally go through and span and read every single one of them, prioritize the themes,
and then put that into the product to make it better
for our end users as well. The thing though, I’m personally
super excited about it and this is thing number 2 out of three that our customers have really requested and asked
off us over time is seamless integration between our customer engagement
and operations apps. We’re really pleased to
announce with Wave 2, we’re releasing what we call
dual right capabilities, that actually allows you seamless out of the box
connected process experience across the set of your
customer engagement apps that you saw Linda and
Philippe talk about. Two year operations
after really enable that cross process experienced
that otherwise historically, took some amount of
integration effort or implementation effort
from our customers and our partners and this
really takes all of that away to provide truly an
out-of-the-box experience. Because if you look at the whole of what we have from a
Microsoft standpoint, there’s really the breadth of
application and the depth of the application stands out on
its own from that standpoint. So to look at this capability from the lens of one of our largest
customers in New Zealand Farmlands, let’s walk through
how they’re using it.>>Thank you. So Farmlands
had the problem of two disconnected systems and
litigious connected systems impacted their buyers and their sales
associates across the whole company. They’ve taken and used rights, which has now extended data model. They’ve applied it from the
end-to-end cycle of their business. So for instance, as
a sales associate, I can start that motion of creating
a new customer record within Dynamics 365 sales and here I’ve got an example of a customer on the right-hand side here
called Grain Farms, and I’ve identified them, but I can also get that little
bit further here as well because as a sales associate, I don’t want to really be managing
multiple copies of my data. So I can actually take advantage of a feature where I can look into say, the global address book that’s in my back office finance system and do a check to see is the postcode or zip code as an example
is valid and in my case, I’ve actually put in
a a short version of one that I know is incorrect, and that’s popped up that
message to the sales associate to tell them that they’ve actually
not finished typing it in. By finishing and typing it in
I’m now going to be able to save this new customer
and as a sales associate. Great. I now know that I can
go and pass information across to perhaps my credit control team and find that particular customer, and that customer is
available to me in my back Office Dynamics 365 Finance, which means I could be
going through the motion of applying a credit limit to that
customer or importantly perhaps, associating a loyalty card to that customer equal for the
sales to continue in the store. But equally in tangent to all this, the buyers are continuously adding new products to the
product catalog and the product catalog will continue to evolve and at some points they’ll release it to the rest
of the sales force. A price in here. Now as soon as I click “Save”
here for some agricultural oil, that product is then going to
be saved in my backoffice. I can continue releasing
the information. But at the same time, it’s going to then start to become available when it’s appropriate for our sales force who are taking orders all the
time from our customers. So here, I could be
starting to think about the same customer that we
identified against a moment ago. I added Grain Farms, they’re
available for me directly. So I’ve gone from my backoffice
to my sales associates directly. I can now start it at the products
that I’ve started to create. So I created a particular
product earlier, I can start to go off and find my agricultural oil and
it’ll appear for me. I can add my oil to
my sales order and continue that sales cycle
that is occurring here. So this brings together that dual right capability and helps companies like Farmlands really benefit
from their data. Thank you.>>Thank you, Kevin. So let’s
switch gears a little bit and talk about Dynamics 365 Fraud Protection
or otherwise known as DFP, perhaps one of our most exciting
and innovative apps that we’ve released in our Dynamics 365
portfolio of applications. With this app, our customers tell us that we’ve been able to
increase their revenue by somewhere between
400-800 basis points plus compared to anything else that they have either
in-house or off the shelf. That’s a pretty bold statement. We know this firsthand because we
actually use this internally at Microsoft and that’s
what we’re bringing to the market for our customers
to now benefit from. The reason why we can feel so confident about making
this claim and saying, “Hey, we actually can
improve your topline,” and who doesn’t really want
their topline improved, is because in DFP we’ve got world-class AI models that have
been trained upon billions and billions of transactions
that we’ve done as Microsoft over the course of our e-commerce business which in and of itself is one of the largest e-commerce
business that’s out there, they’re tens of billions of dollars. atop a set of signals
that we get from these transactions such as a
unique device fingerprinting that has allowed us
alongside relationships we have with some of
the major banks and card networks to create
this consortium of data that is just in and of itself huge and highly differentiating and DFP running adopt this
consortium of data. With DFB running adopt
the consortium of data, we feel so confident that we can
really improve your top-line by allowing you to
reduce any wrongful rejects as the transactions happen. We can reduce your cost by
rejecting the ones that you should and taking the process overhead down as well because there’s a
lot of automation you get, but frankly and probably
more importantly, improve the experience of your customers and have them
the good customers go through a frictionless experience
and not get wrongfully denied if they’re trying to do a legitimate transaction
on your website. So what I would highly recommend
if you’re not familiar with DFB is looking at Dynamics
365 Fraud Protection. Literally, every single one of our customers so far has
come back and told us, who have been able to have the
evidence to show that we’ve increased their revenue by at least 400-800 plus basis points with the use of Dynamics
365 Fraud Protection. Switching gears,
Dynamics 365 for Talent, the Core HR part that allows
you to run HR operations. We’ve had this app now in
the market for about a year, a year and a half to two years. We have a set of
capabilities that’s in use with many customers
around the world globally and we’re pleased to announce
as part of our Wave 2 that we’ve entered into definitive
IP rights acquisition agreement with our top ISVs that brings a set of capabilities
that were either missing or needed some advanced capabilities
in our HR operations now to our Dynamics 365 for Talent
Core HR application. The three core things that we’ve
heard our customers tell us over and over again is
enhance leave and absence, time and attendance,
as well as advanced benefit management as
well for the US market. We’ve acquired and we’ve entered
into definitive agreement with our top ISVs in the
space to really make those capabilities natively available for you in our service,and we’ll be releasing that in our
service over the course of the next 6-12 months. Okay. So we’ve already
covered a lot of ground. We talked about SCM,
Supply Chain Management. We’ve talked about user
experience improvements. We talked about the cross
process integration across operations and our
customer engagement app. We talked about Dynamics 365
for Fraud Protection and HR. We haven’t talked about
Dynamics 365 Finance. We haven’t talked about our
projects service application. We haven’t talked about our Business Central Application and we’re not going
to talk about them. But you should go read
the release notes, the release plan document
as well because it has all the details about those
applications as well. But we will take a few minutes
and actually now deep dive into one particular app
in our operations app portfolio and that’s our retail
app and really how we are committed to really re-imagining
retail for our customers and helping them digitally transform themselves in a space that
frankly is probably one of the most highly disrupted and
highly competitive landscape in today’s world if you will. In retail, we’ve been in
retail for a long time. We have an application today that’s called Dynamics 365 for Retail, that has been in market
counting its predecessor, AX 2012 version as well for many, many years now that has thousands and thousands of global
retailers that are running their in-store operations that are Call Center Operations
and their back office retail operations on
Dynamics 365 for Retail, retailers such as UPS, Columbia Sportswear, Dr. Martin’s, Canada Goose, and many, many others are actually
running their stores’ call center and retail operations
on Dynamics 365 for retail. What we’re announcing or
what we announced literally last week was us now getting into the e-commerce space for in the retail space, if you will. This was, and I talked
about the two things that our customers have often requested from us which was asset management, the second one being the
seamless integration. This probably is the number
one most requested capability from our customers is when is
Microsoft getting into e-commerce? We’re super pleased to
announce that we’ve taken the tack and the platform that today runs Microsoft’s multi-billion
dollar e-commerce business globally across our
various storefronts product design and brought that in a seamlessly integrated way as a Dynamics 365 application
for our customers. With e-commerce now in
Dynamics 365 alongside our point of sale capabilities
for physical stores, our call center capabilities, we now have a complete
end-to-end omni-channel solution that really differentiates
what we have just in Dynamics 365 commerce and we’re going to call it
Commerce going forward because now we’ve got everything packaged
up in our Commerce application. We’ve also brought not
just the DAG but the AI that we use internally at
Microsoft across our storefronts such as intelligent
product recommendations that you see on our dotcom as well as our Xbox app and our Windows app stores
for the benefit of our customers as part of
Dynamics 365 commerce. As if that wasn’t enough, if you take all of that, put it on top of Dynamics 365 supply chain that allows
you to now not just run your retail omni-channel
operations but your fulfillment operations in
a seamlessly integrated way, which otherwise customer
spend months if not years integrating to make sure they’ve
got a seamless experience, that runs natively atop Dynamics
365 Supply Chain Management. Adopt now integrated with
Customer Insights that you saw. So these talk about fraud protection that we just covered
a little bit ago, omni-channel customer
engagement that Linda covered, and marketing, we’ve got a
whole solution here that truly is we believe in a category
of one just by itself. All of that again proving technology, the physical in-store operations in the call center was
already part of Dynamics 365. The e-commerce is what we run at
Microsoft as customer number one. Highly scalable
because we’re probably one of the largest retailers
with tens of billions of dollars that we transact through our e-commerce
platform on an annual basis, built an Azure, highly scalable, secure, and compliant, and
available around the world. So while we’re using it, and we’ve got a really
compelling offering as well, we’ve also been working with some of the early customers who
are actually now using Dynamics 365 Commerce in production soon as we announced preview
of our e-commerce offering. One such customer is Chateau Ste. Michelle here in Washington. Let’s look at their story
on how they’re using Dynamics 365 as part of the video
that we recorded with them. Can we roll the video please?>>Thank you. As if
that wasn’t enough, I want to introduce Lorraine onto the stage and she will talk
about the innovations we’re driving in the retail space and how retailers are really changing
the way they interact in the physical environment and their stores with their
customers. Lorraine.>>Thanks, Muhammad. So the
shopping experience has changed immensely and it
continues to change immensely. It’s reasonable to expect
now you can get anything you want from any place at
anytime from any location, and that expanded customer
expectation it’s way up here, and it’s not going to go down again. What this means for
retailers is they have to be prepared to digitally transform their operations so that they can provide the same
experience across online, mobile, through a rich
commerce solution like Muhammad was talking about, but also through their
physical stores. Now, physical stores present
this unique challenge and also an opportunity to deliver customer experience in a way you
can’t deliver anywhere else. So to help with that,
we’ve introduced recently a new product called Dynamics
365 Connected Store. We introduce this to convert some of those challenges into opportunities. Connected Store brings
data sources from across the store, from sensors, from IoT devices, from
computer vision cameras, it analyzes those interactions, and then it looks at
anonymous shopper behavior, and it takes all that
data together to provide real-time and aggregated actionable insights to the
retailer who can then make better operational decisions
to improve customer service. So as always, the best
way to really understand the benefit to a real retailer
is to talk to a real retailer. So I want to share a
little bit about one of our first customers
of Connected Store, Marks & Spencer,
who’s a UK retailer, and they’re going to
share their story in the video that I’d
like to roll now. [MUSIC]>>Modern retail runs
on modern technology. Intelligent data use is the new
normal for running a business, but data isn’t limited
to clicks and screens. Data is all around us if
we know where to look. Observational data, the data we generate as we move
through the world can be harnessed and analyzed to
inform better business decisions. Announcing Dynamics
365 Connected Store, a new application built
to help retailers maximize the potential of
their observational data. Using video cameras and IoT sensors, Connected Store
empowers employees with tools to be more
proactive and efficient. One of our early customers,
Marks & Spencer, is excited to leverage
Connected Store to optimize their retail
operations in the UK. Recently, Connected Store was deployed at a location
in the heart of London.>>We at Marks & Spencer, our ambition is to be a
digital fast retailer, and our partnership with Microsoft is really helping us
achieve that ambition.>>Being a digital
first retailer isn’t just about having access
to great technology, it’s about transforming our
culture to be data-driven. The Dynamics 365
Platform is equipping our colleagues with
the tools they need to better serve our customers.>>Connected Store gives
us real-time understanding of what’s happening in our store, that makes a lot more
efficient and a lot more targeted in the areas
that we are working. I can use that data
that is sent to me to put my colleagues in at the
right moments at the right time.>>The biggest impact has been on
our cultural change and how we deliver technology into our stores and into the hands of our colleagues. By coupling Marks & Spencer’s 134-year retail history alongside Microsoft’s
cutting edge technology, we’re able to give our colleagues real-time insight into how
our store is operating, and really focus on
excellent customer service.>>We’re looking to use
technology to enhance our operation and to
generate more revenue, and we’re really excited to
be working with Microsoft so we can take advantage of
this amazing opportunity. [MUSIC]>>So how does Connected Store
help UK retailer Marks & Spencer and other retailers improve customer
experience in the store. Well, it’s by creating enduring operational
improvements that are only available because of those unique data sources
in those physical stores. So you can see a few
examples of those here. Being able to provide benefits like scheduling optimization
in store for for staff based on footfall prediction that’s data you can only get in
the store or being able to prevent loss based on
understanding where products are at anytime and movement
through zones. Those types of benefits are only available through physical store data and it can incredibly help retailers improve that customer
experience in the store. So let’s take a look now at how Connected Store actually
functions really quickly. Connected sources bringing those
data sources in from sensors IoT devices and computer vision
cameras and then it provides intelligent AI at the edge so that it can provide
real time alerts to an in-store employee about
where customers might need more help or to improve a
long queue at the register. But it also provides aggregated data and reports
to store managers who can review that information later and make better decisions
about the next day, the next week and start to
forecast shopper behavior. So let’s take a look at
for Marks & Spencer. How does that data start
to add up and accumulate incredible rich value over time
and enable them to predict. Well, in one day alone, as we heard from them
since they deployed, they already started to
understand their busy periods of the day and then in a
week’s worth of data, they start to understand
differences between weekdays and weekend behavior and
they want to assort different products for
different days of the week. Then a month’s worth
of data guess what, they start to understand
what happens on Tuesdays because there are
certain things that happen in that neighborhood on
Tuesdays that they want to prepare for and then once they have a year’s worth of data of
course you’re starting to see incredibly rich
seasonality information. Then over time as it start to
accumulate more and more data about physical store operations and
customer shopper behavior, they can start to pull
in other data sources. Data sources from
the Microsoft Graph, understanding calendar,
understanding local events, understanding weather and
that’s going to enable them through using
Connected Store to really transform digitizer
operations and deliver that customer experience in-store to match their incredible
online shopping experience. So I’d like to remind everyone
that this is possible because of this rich Power Platform
that Connected Store is built on and with and to go
deeper into the power platform. I’d like to welcome on
stage Charles Lamanna.>>Thank you, Lorraine. For this next section
we’re going to be talking about the Microsoft Power Platform. The Microsoft Power Platform has three core products
included inside of it. There is PowerBI which
makes it easy to go analyze and get intelligence from
your existing business data. It’s PowerApps which makes it
straightforward to create web and mobile applications without having to write any code and Microsoft Flow. Makes it very easy to go automate
tasks without having to add any code or actually sign up for
developer to go take any actions. Altogether, the Power Platform
is a single low code experience. So everybody from the user and the
business all the way to IT and pro devs can build and develop much more quickly
inside of their business. Supporting all of these products, is the Common Data Service. Is the center of all
your business data and makes it very easy and
very straight forward. So you can actually securely
access all your information with the right security and with the right connections to
the rest of your business. It also includes AI Builder, which with just simple
configuration and no data science, you can go provide AI to your
business processes just a natural integrated fashion
and lastly the data connectors. Which make it possible to connect
to all of your data across your entire enterprise without expensive integration or complex ETL. All of this Power Platform together, has just outstanding momentum
right now in the market. We have over three million
monthly active developers on the Power Platform. We’ve increased 700 percent for production PowerApps
in the last year. The 300 percent growth in the
PowerApps monthly active users. We have over 25 million data
models for PowerBI with over 95 percent of the Fortune
500 using it to analyze your data and get more from
it and lastly Flow has over 25 billion automated steps
running each and every day and all of this momentum
is just enabled by the connected and
cohesive capabilities of the Power Platform to deliver transformation as easy and as
quickly as you can configure any other SaaS application and to go continue to
innovate in this space, we have several very important
and very large announcements for PowerApps today. AI Builders now generally available. So you can easily understand
forums, classify text, make predictions on the
Common Data Service and detect objects and images
off of mobile devices, all without having to write any code. Additionally, we have PowerApps
Portals which now makes it easy for end users
outside of your company. So your customers and your partners
to access the same data and same application experiences that
you’re used to from PowerApps. It was the number one
requested feature on our community website and lastly, we have a whole host of new component capabilities which work across all application types. Whether it’s Canvas or model-driven, you can build reusable
components with no code or a professional
developer code very easily. Similarly, for Microsoft Flow we have announced AI Builder
as tightly integrated. So you can go understand
those forums and do data classification and leverage AI in your business
processes and automations. We also have hundreds of new Flow Checker rules to make it easier than ever to understand how to build the best possible
automation to explain complex concepts like loops as well as potential errors
or default values. Lastly, a bunch of new editions to Flow in
the authoring experience. Things like geofencing
as well as improved co-authoring or business process
creation on mobile devices. All of it is enabled
with the October Wave 2 release and available for
you to try out today. A core part of all of these updates is making it
accessible for developers. So we talk about the
Power platform to make it easy for business users
or citizen developers, but also professional developers
play an important role. In the case of PowerApps
component framework, it’s now possible to use JavaScript or Typescript and Visual
Studio or VS Code to go create custom web
experiences that work across those web and mobile
applications you know in PowerApps. We already have over a
thousand controls visible on our community site that
had been published and posted by professional developers. Additionally, with the PowerApps
Command Line Interface or CLI, which make it possible
to use source control to develop your application
and solution, to use continuous integration, continuous deployment to go deploy
your updates to production. So you can run the
most mission critical enterprise-grade
applications on top of PowerApps and all of this is part of a much bigger story
for Power Platform. It’s not just about the low code tools like Power
BI, PowerApps and Flow. It’s also about Azure and Visual Studio and VS Code in Azure
DevOps supporting it. Whether it be things like
Azure API management or all the rich Azure
AI capabilities, you can go dock into that
right from the Power Platform without having to leave the confines
of that low code environment. Your data is already stored
in Azure and Azure Data Lake, SQL Data Warehouse or
Azure SQL or Cosmos DB. It’s all available right
at your fingertips inside the application
development environment. This story of having no cliffs and no limits to start with no code, all the way to being
code first is one of the most unique aspects
of the Power Platform. It’s one of the biggest
updates that you’ll see in the October or Wave 2 release and one of the best ways to go show these capabilities and action
is with a customer demo. So in the case of Team Rubicon, they are volunteer-based
organization which worked with first responders
and veterans to go respond to natural disasters or
other issues and what’s amazing is they have a public
website where anyone can go and actually say, read up on the process and they
use this website to grow from eight volunteers just 10 years ago to over 100,000 volunteers today, and one of the big problems
for these volunteers is actually tracking what they
know, what their skills are. How can they best help in the event
of a disaster and to do that, they actually built this website. I can go see. I have a profile
registered on Team Rubicon. I can go say skills and experience, click through and see what
I’ve actually signed up or certify that I know
how to do in the past and they can use this to
respond to an issue to deploy the right people at the right time and say I want to go
create a new skill. I can go just say click through here, you get the standard form but
that’s not super interesting. One of the great things that they
did is they actually made it possible so I can
upload a certificate, say from FEMA and we
have a form right here. I can upload this certificate
and associate with one on my skills and this will automatically be understood by the backend
and registered in their system. Instead of having to go type
in all that information and also go submit proof that I
actually have that capability. So this is all wired up naturally
and if you look at this, you may think this has
to be a process that has professional developers
involved. But it doesn’t. It actually was able
to be built entirely with the Power Platform and one of the core components of that is that PowerApps Portals which is
now generally available. We can see we have a nice
visual designer in the studio which is just what everybody already knows from
the Power Platform. We can see I have a whole
bunch of components available to me to go out to
the page with drag and drop. In this case, I want
to just add a list. What a list is is
just a collection of data I already have in
the Common Data Service. I can go connect to all the
same entities and views, I already have configured in my Dynamics instance or my
PowerApps and CDS instance. In this case, I’ve chosen the skill entity in the
act of skills view. I can toggle whether or
not I want to allow people to create new records on that screen. I can also go toggle a whole bunch of other capabilities and
what that does is, on this profile page, I’m
going to go drill down. I can actually now see the
information right here. I can see the skills
I’ve registered in the past right while I see
my individual profile. So less clicks an easier process. But one of the more impressive things is how do they actually
convert one of these certificates to the data inside the Common Data
Service and for that, they use AI Builder. We have AI Builder capability called forms processing where
all you have to do with just upload a small
number of documents and will automatically
generate an AI model for you that will understand and
take the values extracted out of that document and
it’s much more than OCR. It actually uses advanced
technology from Bing to really understand the text instead
of just extracting the text. As an example I’ve already
uploaded five FEMA documents. This is an AI Builder
tutorial experience. I just say click next and what
happens is I actually get a view like this where we can see
the AI is already identified. It’s Jeff. Hey that’s the
name and a certificate. Here’s the actual certification
that was created. Here’s the date and so on
and all of this is just extract it in a structured
form without a human and without a data
scientist and this type of AI capabilities starts
to really transform business processes
particularly if you can drop it in without having
to write code or get a data scientist and the way
you act on this AI because AI in the abstract isn’t very
valuable is with Microsoft Flow. So what they’ve configured is a Microsoft Flow that whenever
a certificate is uploaded, if there’s a actual
file attached to it, they’ll run through these
steps to use AI Builder to go understand that file
to use that model that I just configured by uploading
files or lookup information like what are the skill details from the Common Data Service as well as go validate against the name on the certificate versus the
profile already stored with Team Rubicon and what this allows me to do is automatically validate or approve these skills
without having to get a human involved
or invalidate them. If this certificate
doesn’t match the user. All of these capabilities
together are just wired up in a single platform with a single
security model and without having to write any code
and Team Rubicon of course is very cares a lot about giving
back to the non-profit community. So what they actually
did is they took their solution and they
worked with Microsoft. They partnered with us to go create the non-profit accelerator
for the common data model. This accelerator is
available for free with no additional charge to all
of our customers to go help them get moving faster on the Power Platform without having to pay any
additional cost and to get the expertise that they
already have for managing all these different volunteers
over a 100,000 on their system. For this part, we
talked about PowerApps, AI Builder, Microsoft Flow, and Common Data Service. But there’s one other
key component of the Power platform
and that’s PowerBI. So for that section, I’m going to turn it
over to Arun who will go dive deep on the new
updates that we have.>>Thanks so much Charles.
So the final product we’re going to talk
about today is PowerBI. As we know in today’s world, data’s coming from
pretty much everywhere. Not just transactional
systems of record, but systems of observation. Product elementary IoT
devices human interactions. Our goal on PowerBI is to help every customer harness the
power of all of that data and private data culture
where every employee in the organization is making
better decisions based on data. What we’ve done in the 2019
wave 2 is delivered at ton of innovative new
capabilities that help our customers do just that. I’m going to talk about four
of those capabilities today. First is a brand new
service experience for end-users that make
it even easier for them to get insights from data and bring all of the analytics content
into a single location. The second is a new experience
for creators in PowerBI desktop that takes a lot of the concepts
from PowerPoint and Office, so it makes it very
easy for them to learn. The third is a set
of capabilities for IT Administrators that
help them certify data and track the lineage of all
the assets in PowerBI so they know that everybody
in the organization using the single source of truth. Finally, a significantly revamped experience for Q and A so that end users can interact with PowerBI just using the English language and
get insights delivered to them. One of the customers that we’ve
been working very closely with is Veolia UK and Ireland. Veolia is a leader in
environmental solutions. They provide their
customers with water, waste, and energy
management solutions. They help their customers
reduce their carbon footprint. They have over 150,000 employees
from around the world. We’ve been working with them to
help over 100,000 businesses, and millions of residential customers reduce their carbon footprint. So let me show you how
Veolia uses PowerBI. So to get started as Veolia user, I started with my Power
BI home experience. You can see that this
is where they get all of their analytical
content brought to them. So you can see some of the
KPIs I’m interested in, you can see some of my frequently
used reports and dashboards, as well as my favorites. In 2019 wave 2, we’ve made it easy for
Veolia to be able to tailor their experience in PowerBI so
that it takes on their branding, it takes on their colors, and so their end users
feel right at home. For this demo, I’m going to go into their Commercial Analytics Reports. What you’re going to see here is the analytics for a single
customer in the UK, and it helps track how they’re doing from a waste
management perspective. The three areas that I’m really
interested in is one is, what’s the diversion rate by month? So this shows you in
what percentage of their waste is diverted to
recycling facilities etc. It’s going up and
that’s a good thing. The second is the recycling
percentage by month. It’s generally been going up, it’s a good thing they had
a drop in September. Lastly, the total weight of their wastage that they’re actually sending out from
their different sites, and generally see that
this is tracking down, which is also a good thing. One thing I wanted
to show you is that there’s a significant drop in September in terms of the
total wastage going down. One of the capabilities that
they provide in PowerBI, is the ability for the customer
to simply go in and say, analyze this data for me, and
explain what drove the decrease. When you do that, you can see that PowerBI analyzes the data model, it looks for insights using
sophisticated AI algorithms, and it actually produces insights
on what drove the decrease. So you can see here that the
decrease was pretty much driven by non-hazardous
industrial waste, which is a good thing
because this waste would have otherwise
gone to a landfill. What you’ve done in the
semester is not just made it easy for them to get to their
reports and dashboards, but bring a lot of their
analytics content from around the organization
into that report. For example, Veolia can include
their documentation right here, which is a Word document that tells the end users how to use this analytical and
reporting application. It’s just integrated into
their PowerBI experience. Customers often have
quarterly reviews or monthly reviews of
their business process. You can bring that content
directly into PowerBI, and you can have the end-users understand exactly
about the business was, and you can see a
PowerPoint presentation on their last business review again, integrated into analytics experience. You can also get feedback from the end users with Microsoft
forms or Forms Pro where they can tell Veolia how they can improve
the state of their analytics. Lastly, you can even take
tutorials for PowerBI. So end users new to PowerBI, you can get a YouTube video just embedded in so somebody
who’s not familiar with PowerBI can actually end up
learning how to use the product. So you can see how we’ve
made experiences really simple for users to get
the insights they need, but bring a lot of the
analytics content together. Now, I’m going to go a little
bit underneath the hood and show you of the capabilities that we provided for creators and
IT Administrators that make it easy for them to build
these great reports and dashboards. In order to be able to do that, I’m going to step into this view that is available
for IT Administrators. So what you see here
is we’ve provided comprehensive lineage
where an IT Administrator can come into PowerBI, and they can see all the
different data sources. They’re getting data
from SQL Servers, text CSV files, or data sources. You can see which
datasets these feed into, which reports, and which dashboards. By clicking on any
one of these tiles, you can see the comprehensive
lineage for that particular asset. You can see where
the data comes from, you can see where the
data goes through. So it really helps end-users
and IT Administrators understand how people are using
the single source of truth. If I scroll up, you
will notice that one of these datasets has a little
badge right next to it. This is because it’s
a certified dataset. This is a capability
that we’ve provided for IT Administrators to be able to certify the single
source of truth and ensure that it’s used consistently
across the enterprise. I can click into this
certified dataset, and I can see it’s linear it. So I can say, hey where did this data come from and how it
was put together? So now that Veolia has all the
data in exactly the right shape, let me show you some of the
new experiences we have in PowerBI desktop that improved
the authoring experience. So here, I’m going to go
into PowerBI desktop, and I’m working on a report here. You’ll notice that we have
a fresh new experience in PowerBI desktop that borrows from a lot of the
themes that users are already familiar with in Office. Let me just show you
some small examples. For example, if I take this
visual and move it around, you’ll notice that these
little red grid lines appear, which is something that we
picked up from PowerPoint. We’re really trying to
make PowerBI desktop the PowerPoint for
data so that everybody who’s familiar with PowerPoint is instantly productive within PowerBI. Another concept that we
bought from PowerPoint is the ability to group
objects together. So if I go in and I
select these two visuals, I can just right click, and
just like I do in PowerPoint, I can group them together. Once they’re grouped together, they move together, they
can be resized together. So it makes it very easy for end-users to be
able to work with that. One of the things I wanted
to draw your attention to is the new ribbon experience. So for those who are
familiar with Office, this new ribbon experience looks exactly like what they
used to with Office. The reason it looks so familiar is because it’s exactly the same ribbon. The reason we’ve done that is to
make it easy for end-users to be able to borrow again for the concept that they’re
familiar with in PowerPoint. So I can quickly go ahead and
change the themes for example, and you can see just like
it does in PowerPoint, they can change the theme
for this whole report. The last thing I wanted to show you is some of the new experiences that we’re releasing next
week with Q and A, the ability for end-users to
simply ask questions in English. What you see here is
we’ve added a new visual, it’s the Q and A visual, and I can bring it directly
on to the PowerBI canvas. When I do that, you can
see that it shows me a bunch of suggested questions right off the bar that Power
BI automatically generated by analyzing the
report on the data model. For example, if I click on this one, the end-user can say, what’s the average wait to
final destination? It’s right there. I can also
type questions in free form. So when I type a new question, PowerBI analyses the
question and goes ahead and tries to give me the answer
that I’m looking for. So if we’re looking at the
diversion rates, by site, you can quickly see
that PowerBI created a graph that showed me the diversion rates for
the different sites. If I click on each of
these diversion rates, PowerBI cross filters the rest of the data and the report so I can see how they’re doing from a
wastage management perspective. Let me try another question. So I’m going to try
another question here. If I try to understand
the total spent by place, you’ll notice that Power
BI actually did not understand place because it
marked it with a red arrow. The reason it did that is because it didn’t really understand what
the end-user meant by place, it’s not something that’s
in the data model. However, it did interpret
the question correctly. It said most likely
the user’s trying to understand what the
total spend is by site. The reason we have been able
to do that is because we have integrated the Office
Thesaurus so that everything that is in
the Office Thesaurus is already naturally
understood by PowerBI. Another example I
wanted to show you is the ability for Power
BI to be able to understand adjectives that it may not have an existing definition for. So I started off by saying, hey, show me the recycling
rate for critical sites. Now, PowerBI understood that
critical is an objective. However, it does not understand
what critical means. It’s undefined in the data model, and there’s no real synonym that it can use to be able to decipher it. So here, I can go ahead
and just simply use the tooling to go ahead and teach
Q and A what critical means. So if I go here, you
can see that critical is not understood, I hit “Submit”. Now it tells me to teach
PowerBI what critical means. So I’m going to go ahead
and describe critical, which is sites that
have a lot of wastage. When I hit “Enter”, you will see
that this particular definition, waste weight that’s greater
than 20,000 pounds, is applied and you
can see that results. So when I hit “Save”
and I hit “Okay”, you will see that this
particular definition is now applied to the data model, and now PowerBI understands
the definition of critical, it’s no longer marked in red. So that’s what I had to show
you for the 2019 wave 2: Amazing new capabilities
for end-users that bring all of the
analytics content together, new experiences for creators
and IT Administrators, and a brand new Q and A experience. So with that, let me bring
James right back. Thank you>>Thank you, Arun and thanks
everyone for joining us today. Believe it or not, we covered less than 15 percent
of the new capabilities in this release wave even though
we went 15 minutes long. So if you haven’t checked
out the release notes, please go do that. It’s comprehensive, lots and
lots of good stuff in here. Until next time. Thanks
again for joining us, and we’ll see you in April. [MUSIC]

Multideur’s migration to Microsoft Dynamics 365 Business Central

Worldwide millions of doors open and close each day. Multideur ensures that vital organisations
like the Ministry of Defense… …and fire departments have no worries about
their accessibility by using technology. Basically I always say nobody notices a door… …until it doesn’t work anymore. Because then you will find out that the processes
inside a factory can not continue anymore. Fire departments, the Ministry of Defense
or police departments… …you can imagine what will happen if such
a service can not be delivered… …because a door is malfunctioning. Since we are focusing more and more on the service delivery… …we see a big challenge in the speed of
information throughout our processes. In the past we had a very physical process here. With lots of piles of papers and mechanics going
to clients with physical worksheets. But also we had some various systems and
various versions of Navision… …so when a client called with a breakdown or malfunctioning door, we
had to look at different places to find the right information. So the speed and accessibility of information became a big issue. And this is something we wanted to solve with a new system. We chose for the Microsoft Dynamics 365 Business Central
solution with the Field Service app. Basically it gives us the most easy way to find information. We also ensure that the information is the same at every place. And its accessible for everybody everywhere
because it is in the cloud. So for example a mechanic can now focus on
his job, which is to maintain or service the door… …and less on paperwork and all
kinds of administration instead. Our work used to be a lot of paperwork, a lot of e-mails… …no that was not a nice situation. Now we have more time with the system to
help the customer and work on the project. That makes life easier. We made a big choice to put our system into the cloud. So we do not use local servers anymore. But also no local support. We have a partner which is Prodware. They helped us with defining the system. They helped us find
the best solution for Multideur in our demands and our processes. And today they support us in having the system online
everyday. And help us improve everyday. We are now also working on implementing the business intelligence
app Power BI… …which gives us a lot of management information… …on what we are doing so we can provide
the SLA information to our customers proactively. And also steer ourselfs on our main KPI’s and
the service delivery that we have in the field. In the end we want to deliver our promise. Which is
to deliver the best service to our customers. So basically we already know when a breakdown can happen… …or when specific predictive maintainance needs
to be done before the client even notices. And this is what we are looking into. By use of IOT
which is also supported by the Field Service solution.

Dynamics 365 Business Central | Business Applications Spring 2018 Release

>>Hi, my name is Marko Perisic. And I’m the General Manager for Dynamics 365, Business Central. I’m extremely excited
to be here today to introduce to this great
new product relaunching. It is a modern solution
for modern businesses. As we’re launching this product, I was first like to take
a look at the markets, and typical requirements of
the businesses in the market. What we see today is that
businesses quickly outgrow their basic accounting system
and legacy ERP systems. As they do that,
they have siloed systems that are not very
well connected together. They have duplicate data, they have manual processes, and insufficient reporting across the different solutions. All this drives inconsistent
operations of the business, which ultimately in
some situations results even in non-secure processes for how they operate their business. Let’s take a typical example. A business will acquire
a financial management solution, and quickly they,re
realize they need a solution to run a sales
and service organization, a typical CRM system. As the move forward,
they quickly realize the processes that
need to manage a supply chain management
require another system. Then they will
realize they also have a project management
solution that need to integrate
with their systems, and operations
management solution. As I look at different silos, the reporting analytics
are insufficient for them to run
a successful business. Because of that, we
introduced to you an all-in-one business management solution
from Microsoft, Dynamics 365 Business Central. Dynamics 365 Business Central enables businesses to
connect their businesses. Make smarter decisions faster, and start very
quickly and easily, and then grow from there as
their business needs evolve. Let’s talk a little bit
about connecting your business as
businesses operate, they have multiple different
processes that integrate across the organization to drive the top and
bottom line of the business. Financial management,
sales & service management, project management,
supply chain management, operations management are
all processes that have different workflows
to integrate with each other for the success
of the business. Without having clear insights across these
different processes, and be able to drive
consistent reporting, and predictive
analytics, companies cannot make the right decision
in the right time. Dynamics 365 Business
Central enables organizations across
these processes to drive these
predictive insights, consistent reporting, and
make smart decisions faster. I’d like to now invite Jannick to show us the first demo of Dynamic 365 Business
Central and how customers can run the processes unified with this product.>>Thank you Marko. Let me take over here, and actually demonstrate
Business Central. And first thing you
see here is the new, modern, fresh
UI for Business Central. When you wake up in
the morning here, you get your business insights
directly on the screen. You get intelligence
about your company. In this case, it
says that I’ve closed six more deals than in
the same period last year. So everyday, Business Centrall
will go through the data, find what’s interesting
for you to know, and you can then wake up, can’t wait to get into the system and see
what’s news today. And what we’ve concentrated
building here is actually the key functionality that you need within
your roles in that. In this roles, and I am
the Business Manager, so we concentrated on functionality that a business
manager would like to see. First of all, we start
on the top of the screen, we have all the functionality that this role would
normally access. In this case, I have the finance functionality,
I could omit, and I could go further into the system with I want
to see: my journals, my sales budgets,
purchase budgets, and so on. I could go to cash management where I basically
manage my payment, my cash, and so on, and continue finding that place
I want to look at. But before I do that, first of all, I want
to scroll through, see if there’s
any important actions or anything I should look into. I can see that today, we have overdue sales invoices. And I can drill into what we call the emphasized queues here, and see directly what
are these invoices. And once I’ve looked that, maybe take taken action sending
out finance memo charges, and so on, I can go back and continue on my role center here, to see that there
are some sales quotes I looked at them yesterday, so I’m not going to
look at them today, but if we scroll down
a little bit here, we can see that there’re
incoming documents for me. So, if I look at
the incoming documents, this is where I get
electronic invoices in, and I can see that there are two documents for me
to take action on. The first one has already
been processed in the, what we call optical
character recognition. You can see it says,
OCR STATUS, Success. This means, that the document
has basically been translated into
machine-readable format. So, if I go into the document, everything that before
was just a PDF file. You can see that here, has then been extracted, and now we know who the Vendor
voice, the document date, and so on, the currency code, all that is taking
from this document. So, I don’t need to wake up and start entering
a lot of information. I can basically just with a few clicks buttons
here do my daily work. In this case, I will go and create the
journal lines for it, once that is done, I can open the record, and now it will basically
show my journal. I could continue, and when one of the things that’s really strong in Business Central
are the unlimited dimension. So, in this case, I could
put a Department Code, and I could say that
this is a large customer, so whatever these are
defined by companies. So the company has to find that these are the Department
Code they use, or Customer Code to use, you could define unlimited over this for further analysis later. Once I’ve entered this
information, I can go ahead, and either post it directly
into my finance transactions, or I can go and
say edit in Excel. So let me try that, and when it opens my Excel here, and now I have
a journal in Excel, and I can continue to work
within Excel on my journal. I could change the name here. So, we give you
the option basically to have a choice of whether you want to work within
Business Central, or maybe you’re more familiar, or have uses that are
more familiar with Excel, and they can now continue
the work within Excel, and do the changes there. And once that is done, they can go ahead and publish those changes back
to Business Central. Now, we will
recorded the entries. Let’s jump back, and
continue from here. So. I’ll go back to
my Role Center again. I’ll basically just look
for further information. I can see here, it’s been
updated with life data, when I’ve changed
something in the system. My top five customers
are now updated. I can see whether there
are any approvals for me, but I can also see the Trial Balance directly
from within my Role Center, then see if there’s anything I need to pay attention to today. And further down here, you can see we
embedded Power BI reports. So, with embedded
Power BI reports, I can of course do
further analysis, and I can even directly from Business Central
expand the report, which then opens up Power BI, and I can now work
with the data, analyze it even further
from within Power BI. So now, you can
see the same data that I just had in
Business Central. You can see it
here on the screen, and you can further analyze
it from within Power BI. So, I can basically
just hear it go back, and continue my work. I can also print
my report, either to a PDF, or maybe I want to print it to Excel because some people like to maybe do some editing
to the reports, coloring, column
layouts, and so on. And hence, I can go and say, “Excel Reports” here
on my Role Center, and basically take
my Trial Balance. And now that it’s done. You can see here, it’s open
my Trial Balance in Excel, and again, I can do
further editing here. I can also, if somebody
post something, I can refresh and get again
life data from within Excel. So this concludes
my first demo here, which is really
about what you can do from within the
Business Central roles, and how we optimize it
to a fresh and modern UI, and made available
also integration to other Microsoft products. In this case, I’ve
demonstrated both Power BI, and also Microsoft Excel. So this next demo, will actually start
from within Outlook. Some users, they are used
to work within Outlook. They read their emails,
they want to take actions, from directly from
within their emails. So instead of them
switching out for example, this case to Business Central. We have enabled it,
so that you could work with Business Central
from within Outlook. In this case here I
have got an email, somebody asking for a quote for two desks and
16 chairs in this case. And I could now
start typing that in. But as again, you
saw before we want to limit the number of times
you have to enter data, but instead, focus
on productivity. So, I can actually click a little “Business
Central” icon here. And the first thing
I want to do, is actually look into
this customer and get some information
about this contract. What will happen now is Business Central will
actually connect, and bring up the information
for this customer. So now on the screen, I can see some key information
about this customer. This is Coho Winery, I can see that there
are some past invoices that they haven’t paid, I can also see that there
are some opportunities for them from
my Dynamics 365 for Sales, I can also see
there are some cases from customer service, so I could open those cases, just look into it and see are there anything I
should be aware of. That’s not really here,
so going back here, I want to start working on this quote of this request
for quote here. I can click on “Create
the new document” icon. So I will go and open
up a sales quote. The user here wants to get access directly to
the sales quote. So by doing this, I can now see that
the system has used intelligence to read
through the email, and actually identify
that there are some names that looks
like the products we sell. We can actually see
here on the screen, it’s added to the
corresponding item numbers and it’s Athens and
Paris guest chair here, and even the
quantities are put in. So these are suggested lines,
I could go ahead, and I could edit, but I’m fine, because everything
is perfect here. So as a user, we build it so
that they would accept this, and the rest is now created. I could just basically
send this right away, or in this case, I now remember that I spoke to this customer about a discount. And I can go down, and work with the quote like I would do
it within Business Center, and add the discount
directly here on the screen. I can now take the next step
in the process, and send this by email. So we’re basically giving
the tools to the end user, directly in the product that
they prefer to work with. In this case, it’s Outlook. And now you can see
the emails generated, it’s created as a beautiful
looking PDF as well, I could actually open that
PDF right here in the screen using one of the templates that comes within
Business Central. So here you can
see it’s created, and now I can basically
just go ahead and send it. So in this case, we
now send the quote, let’s just assume
the process will go on, and it will be an order,
and we’ll create an invoice, and hopefully that’s all. But sometimes,
the customer who then maybe called there’s
some service to be carried out. This is exactly what
happened in this case, they called and needed a leg fixed on one of the chairs here. So within business central, we now also have
the service order capability. So you can see here, I
opened that screen directly, and I’ve now created
a new service order. Let’s just drill into it. So with the Service Auto
Management functionality, in this case you
can see it’s about fixing the broken leg
on that Paris chair, I can key in the repair items, I can even start
planning the dispatch, and other things with
Service Auto Management within Dynamics 365. So, this is the full
functionality in terms of Service Auto Management
that is now available here. So we just saw a demo
starting from within Outlook because we want to enable the user to work
within the system. They are working, and
prefer it’s working. Some users also start the day
in Dynamic 365 for Sales. So we’ve done the same thing
here with Business Central. We’ll make sure that there’s
a very strong integration. In this case, I have Dynamics
365 for Sales on my screen. I want to go and see the orders. So I open the sales orders
created here. And, let me just go to
the last one created, because I know that’s
for Coho Winery, and that’s the one
created for one of the customers that we
have in Business Central. So this user opens,
and uses sales. And now as part of the process, they’ve already submitted
the sales order, I can see this in
the status here, and that means that it’s been
sent to Business Central. So let’s actually
go and see if we can find this order is called
sales as order three, let’s see if we can find the
same on Business Central. So I’ll jump back
to my role center, and now I need to jump in, and look at sales orders, so I can very quickly go here, and just open sales orders, and we can see that there is a sales order for Coho Winery,
sales order three. And if I open it,
you can now see that the information
on the sales order is exactly the same as the one we had in
Dynamics 365 for Sales. So we make sure that we
synchronize the customers, the contacts, the price list, unit of measure,
everything you need to have a strong integration between
the Business Central part, and Dynamics 365 for Sales. So this illustrates
the strong integration between the several
Dynamics 365 products, so let me now switch
to a different demo. So now let’s have a look at
actually how I procure items, because we looked at
how we sell the items, and all the great tools that can help
us improve that part. But let’s also look at the end-to-end process
as proper job to pay. And we start with the items, and you can do this from
many places within the system. But if we start from
the items and open that, first of all what we get here on the screen are the
embedded Power BI reports. And I get some key information
about my items. In this case I’ve opened
the Athens Desk here, and it give some information about items available and so on. What we also added on the screen if I scroll
down a little bit here, is we added the sales forecast, the inventory forecast here. And we are actually using
AI to calculate this. We look at past transactions, we look at what happened basically
within the system here, how much we sold and so
on, in which periods, and then we predict what will the inventory
be in the future. So in this case, I can see that I need
to take action because my inventory is
going minus here, so again we try to enable the user to take the actions
from where they are, and this case I basically
can go here as a user, just create a purchase order
directly from the screen. So when I do this, it comes up with
the purchase order, and I can now send it. But, we also added
intelligence in the system in terms of giving
notifications to the user. What if we tell them
right here on the screen, that there is also more items that are
running out of stock. And that’s what we can do here, we can basically add
them to this document because this supplier normally
also sell us other items, that are running out of stock. So again we’re showing how
we improve the productivity, in this case in
the procurement process. So procuring items is one thing. Of course also
Business Central now comes with manufacturing
functionality. So we enabled the full suite of manufacturing functionality, for example,
my production forecast. So let me go, and just switch
to my production forecast. And as you can see here,
our key production forecast for this one Seoul guest chair. And I’ve done it on a day view, I could change that day view
to do it per month, per week, per quarter and so on. And that production
forecast is then used to calculate what
I need to purchase. I’m now in the requisition
work sheet and this is where I can go now and
calculate my plan. What is it I need to produce? What is it I need to buy? So, I will in this case
here use my forecast, and the forecast I keyed in
before was called sales 2018. So when I carry out this, it will basically then have calculated what is
this I need to produce, to fulfill demand here. This basically shows
the process of also producing items that is now available within
Business Central. Now we’ve seen how we procure
items, how we sell items, but of course the end of
the process here is that at some point of time
we’ve paid the invoices, we’ve got also invoices
paid from the customers, and then we need to
reconcile our bank payments. And in this case, we would be able to
import bank transactions, and we’ll now need to reconcile with the entries we have
within Business Central. Again, we’re using
intelligence here, because we have added what
we call apply automatically, and it will basically go in, read through all the
transactions within the system, and in this case we can see here six payment lines
of six are applied. So, here you can see even with the match confidence
whether it’s medium, or low. So that means whether it’s
matched on the amount, whether the text also
matched, and so on. So even intelligence
in this part where we do the
bank reconciliation.>>Thank you Eric. Let’s talk now more about making smart business decisions faster. All these data across different processes within a system, is not of use to
a customer unless they can make smart business
decisions faster. With Dynamics 365
Business Central, We bring all this data
to the customer, and use advanced predictive
analytics techniques. To bring them insights
into the business, to empower them to make
smarter decisions faster. I would not like
to invite Claus, to give us a demo of that.>>Thank you Michael. So let’s have a look
at how we bring the intelligent cloud
into Business Central. And I’m in my
accountant role center, and I want to point
your attention to the chart called
Cash Flow Forecast, where we use
Cortana Intelligence, and Azure Intelligence
to look at historical data in your company, and predict the future cash flow
of that same company. You’ll see the red part
here in the chart, it’s actually
a future prediction on how your cash flow is going
to evolve as time goes by. I’m in the business
manager role center, and here I want to show you what Business Central could give
you in terms of analytics, and allowing you to look at the data that
you have in your system. Here, I have access
to Power BI reports, that are made available to me as a user of Business Central. I can switch between the reports
that I have available, right here, so that instead
of looking at financial data, I’m looking at sales data. If I want to take
a deeper look at the data, I can expand the report
to full screen. And in here, I have access to various tabs in
my Power BI report, I can switch to my dashboard, that allows me to take a look at my items sold by quantity, and if I want to filter on a specific item I can do
that by clicking the item, and it will filter everything
in my dashboard for me. Moving on to items, let’s take a look again at where we bring the intelligent cloud
into Business Central. As you’ll see here at
the bottom of the screen, I have item
availability forecast available to me as
I look at my items. This is also
a Kutana Intelligence, that we’ve allowed to take a look at
historical data to try to predict the future
availability of my item. This will filter as I browse
through the list of items, and show me contextual data based on the item
that I am looking at. Going to the top of
the screen, I again, have access to Power BI reports, based on the specific item
that I’ve marked on my screen. I’m in my customer list, and I’ve been contacted by a customer that wants
to buy some furniture. So, I want to take
a look at Trey Research, and create a sales order
based on what they asked me. As I open Trey Research and
try to create a sales order, I get a notification at
the top of the screen, saying that this
particular customer has an overdue balance. If I click “Show details”, I can get a closer
view of the data available to me from
Business Central on this specific customer. I can look at
the outstanding balance, and I can even take action, and send a finance
charge memo to them right here while I’m
creating my sales order. If I choose to go on, and create the sales
order, which I will, and they asked me
for some chairs, and I know that they
wanted 16 chairs. As I enter, that number into
my Business Central screen, I get another notification
telling me that’s the stock of this
particular chair is low. If I click “Show details”, I’ll get a notification
that my inventory is short, and I can create
a purchase invoice for this item right here while
creating my sales order. As I do that, I’m notified that this vendor that I
usually buy this chair from, also sells me other items
that are also low on stock. And I’m asked whether
or not I want to add them to the document
that I’m creating. If I click this, it will also fill the lines with what I need, based on the inventory forecast
that we saw previously. So, I know that I am
going to need 50 chairs. I go and fill that out, and I consent my purchase order
to this vendor. Thank you, Clause.
For modern businesses, it’s extremely
important that they can start quickly with
their solution. It is also important that it can grow as their business
needs grow. With Dynamics 365
Business Central, we allow customers to tailor their businesses to
the specific needs, get started quickly with a new modern refreshed
user experience, and as the business
needs evolved, adapt that experience to the specific needs of the different roles,
and their business. I would now like
to invite Jasper to show us a demo of that.>>So, let me start by talking to you about personalization. How you can tailor
this essential to your particular
personal work style and your particular needs? So, in front of me, we
have the Role Center. Now, the Role Center is already optimized for your role
in your organization. And as you can see, we have tiles and we have numbers that are already helping you
to do your everyday work. But we can take it even further. And you can personalize the Role Center from
ride in Business Central. If you go to “Settings”, you’ll see that we have
a menu called “Personalize”. In Personalization mode,
I can now drag and drop sections of
the Role Center to fit my particular need
and how I would like things to look when
I do my everyday work. Again, for instance, let’s
go into the items list, and do some changes there. Here, I can decide where I want my “Freeze
Pane” to be placed. I can also add more fields
by going to “More”, and then, adding fields to my list by dragging and dropping
them into the list. And when I’m done, I just
press the “Done” button, and now my Business
Central experience has been optimized to my
particularly work style in my particular needs. Now, let me talk to you
about the in app designer. The in app designer gets
media opportunity to not only create personalization
for my personal need, but to create customizations for everyone across my organization. You’ll find the in app designer of the same place you find the personalization in
the “Settings” menu, that will take me into
the in app designer mode. And from there, I can do many of the things I just showed
you with personalization. I can drag around fields, and I can rename
areas and so forth. But when I’m done
doing my changes, things are a little
bit different. Because when I press
the “Stop designing” button, that’s when
Business Central will take the changes I just created. And convert them
in to an extension. You can even take an extension
and do code changes, and integration work
with the extension. And this takes me to
the last part I would like to talk to about AppSource. In AppSource, you can find extensions that
are professionally created by thousands
of partners, and those extensions can be integrated to
the Microsoft Power Suite, such as Power Apps for creating business applications
across devices, or Microsoft Power BI for
doing business intelligence, and smart decision making, and Flow for creating workflows, and integration across
different systems. Since it’s possible to extend the solution with apps
from Microsoft AppSource, our customers can choose to
work with our global network of partners that have deep industry knowledge
and expertise, and help customers customize the solution for
individual organizational needs.>>Thank you, Jasper. We are extremely excited about
Dynamic 365 Business Central. We believe it offers
a collection of unprecedented
capabilities to customers to run their modern
businesses successful. We suggest you contact your local partners
who can give you a deeper information about
Dynamics 365 Business Central. We’re extremely
excited about this, and we’re looking forward to your success stories
with Business Central.

E-DAB 00: Introduction to Excel Data Analysis & Business Intelligence Class: E-DAB YouTube Class!

[MUSIC PLAYING] You get lots of data, and you
need to– with a little magic– create your report? Then you came to
the right class. This is Data Analysis and
Business Intelligence Made Easy with Excel Power Tools, also
known as Excel Data Analysis Basics E-DAB. Now why Excel? Excel is the most used data
analysis program in the world. It contains straight
Excel, pivot tables, the amazing and
transformative Power Query, Big Data PowerPivot
and Power BI Desktop. My name is Mike Girvin, and
I’ll be your instructor. I teach at Highline College. I’ve been an Excel
MVP since 2013, and the creator and mastermind
behind ExcelIsFun YouTube channel, with over 3,000
videos and 100 playlists. These are the 10 videos
that will teach you how to convert that raw data
into useful information. All right, we’ll see you
in the YouTube classroom. [MUSIC PLAYING]

Working with dates (1-3d)

If you have date columns in your data, you can apply different transformations to help extract particular bits of information from that. For example, I’ve got date column here, but I might want to pull out the day of the week or the quarter that that date fell in. It’s easy to do that with the Power BI Query Editor. On the Transform ribbon, you’ll see a Date option over here, and I’ve got a few different dropdowns that show me the different pieces that I can extract. So, for example, the day of the week or the day of the year or just to extract the year piece or the first date of the year, the last date of the year, etc., etc. Now, when I’m working in the
Transform tab of the ribbon here, that means that I’m changing this column and I’m going to replace it with the piece that I choose. So I’ve replaced that date with just the year. If instead I wanted to add a new column with that information, I can choose this Add Column tab from the ribbon. And you’ll see I have the same options. So let’s just extract the year piece, and
you’ll see it adds a separate column into my query. So, for example, I might want to do the day of the week, so I get a zero based index naught to six for which day it is, or I could choose the quarter. So sure enough, all of these dates in January are in the first quarter of the year. So there is a whole range of different
options that you get here to extract certain information from your date/time fields. If I had time in here, I could do the same sort of thing for pulling out hours or minutes or seconds, and my duration one where I have options to combine things from minutes to
hours or into seconds, etc., etc. A few different options for working with dates and times.

E-DAB 01: What is Data Analysis & Business Intelligence?

[MUSIC PLAYING] Welcome to the first video in
this new class, Data Analysis and Business Intelligence Made
Easy with Excel Power Tools. Now this class really should
be called Excel Data Analysis Basics or E-DAB,
because if you’ve never done data analysis
before and you want to learn the
basics of data analysis, you came to the right place. Now why Excel? Because Excel is the
most used data analysis tool in the world. We have straight Excel features. We can build pivot tables,
use Power Query, the new Power Pivot and even Power BI Desktop. Yes, indeed we’ll
learn all these tools, so you can take all
that data you have and convert it into insight. Now this is video number
1, an introduction so we have to go over
who the instructor is, what is the scope of the
class, what version of Excel you should be using. We’re going to define
data analysis and business intelligence, talk about
the goals of the class. We’ll talk about the videos
that will be presented in this class, the amazing
files you can download and use to follow along,
and what you will gain after taking this class. My name is Mike Girvin. I’m a Highline College
instructor, a Microsoft Excel MVP since 2013. And I created the
excelisfun YouTube channel, been posting videos since
2008 with over 3,000 videos and over 100
playlists and classes. Now the scope of
this class, this is an introduction
to data analysis. It is for people with no
experience with data analysis. Although, if you like
watching Fun with Excel and you know a little
bit about data analysis, doesn’t hurt to watch this. So with no
experience, you’ll get to learn how to turn data into
useful information and insight. And this is a prerequisite
for the advanced data analysis class here at the excelisfun
channel, called MSPTDA. And we will
definitely have a link to that playlist and that
class at the end of this video and also at the
end of the class. Now what version of Excel are
we going to use for this class? Excel Office 365. Now really, you may have
all sorts of other versions like Excel 2016, Excel 2019. Those will work for almost
everything in this class. But Office 365
has the advantage. It’s the only version that
gets updates with new features every month. And in fact, moving
forward in Excel history, it’s the only version to have. Now you may not
have it right now and some of the other
versions will work. But get it as soon as you can. Now we’ll also be
using Power BI Desktop. That’s a free download
from Microsoft. And we’ll download it during the
last two videos of this class. Now we need to define
data analysis and business intelligence. Now data analysis
the definition, to convert data into useful
information for decision makers. Now business intelligence is
exactly the same definition, except for in a
business context. A simple example–
and simple examples are always awesome
when you’re learning something for the first time. Here’s raw data. We have two columns– sales rep and sales. The first row or
record show sales rep Ty had sales of 7,500. The third record shows Abdi
sales rep sales of 11,500. Now that’s the raw data. But if our goal is to determine
whose sales were biggest, well the raw data alone is not
going to give us the answer. We have to convert that raw
data into useful information. Notice, we first create a
unique list of sales rep names. And then we do our adding. We’re adding the sales
for each sales rep. Boom, we have our
useful information. Now we can answer our question. The answer, Gigi. Now business intelligence, we’ll
define this as convert data into useful, actionable,
refreshable information for decision makers in
a business situation. Right, we have a
business situation. But now instead of just
useful, it says actionable. All that means is from
the useful information, we can act to make a decision. Now refreshable, that’s
the amazing part. That’s the part that Excel and
the power tools can do so well. That just means when
we get new data, we want our useful
information to update. Now why is it called
business intelligence? Well because the
business is intelligent because it’s making
decisions based on data. Now both data analysis
and business intelligence will help to see
trends and patterns, ask questions, and gain insight. Short and sweet definition
for both, here it is. We’re simply taking data and
converting it into information. Now the goal of data analysis
and business intelligence, well, we need to create
useful updateable, actionable information
for decision makers in the form of reports,
visualizations, and dashboards. Here’s an example
of a report we need where it shows the total
revenue by company and product. But look at this. We’re given data in the
form of various text files. And we have some data
inside an Excel spreadsheet. Now the cool thing
is inside of Excel, we’ll get to use Power
Query to take all this data, convert it to the
right form, and then we’ll use a pivot table
to create our report. As a second example,
over in Power BI Desktop, we’ll have to create
this visualization from various Excel files. Well, we’ll use Power Query
to go and get the data, transform it, and load
it into Power BI Desktop. And then we’ll use the various
visualizations to plot sales revenue on a map and sales
by product in a bar chart and then sales by city and
sales rep in a second bar chart. Now, next we want to talk
about some of the goals for this class, some of the
achievements you should expect. Now we’re going to get an
introduction to these Excel power categories, Excel
spreadsheet formulas and features, the standard
pivot table, Power Query in both Excel
and Power BI Desktop, data model pivot tables
using Excel Power Pivot, and data model visualizations
using Power BI Desktop. More specifically,
goals, we want to get an introduction to the
specific data analysis power tools in Office 365. We get to learn about the Sort
feature, Filter, Excel table features for dynamic data,
spreadsheet functions like SUMIFS, COUNTIFS,
AVERAGEIFS, the amazing Office 365 dynamic arrays, standard
pivot table and slicers, charts and visualizations, Power
Query, the VLOOKUP function, the relationship feature,
Power Pivot data model, DAX functions which are
the functions inside Power Pivot and Power BI Desktop
of course Power BI Desktop. We’ll also have an introduction
to data analysis terms and processes, such as data,
proper data set, delimiter, relationship, ETL, data model,
columnar database, dashboard, and much more. We also, as goals
of the class, need to learn how to perform
these data analysis steps. Import the data, then
clean and transform it. Build the data model. Build reports, visualizations,
and dashboards that deliver that useful information. Then when the new
data arrives, we’re going to have to make sure
we’ve built the solution so we can refresh that information. Then we have to assess the
usefulness of that information and repeat steps as necessary. Now actually, there
are a few steps before importing the data. For example you might
have to determine what questions need to be asked,
what sort of reports you need. You might have to search
throughout the particular entity, find out
what people need, find out where the data is. But we’re going to
start at importing data. As a preview of the
videos we will have– well, number 1, you’re
watching that one right now. Number 2, we’ll define
data, proper data sets, Excel table, sorting, filtering,
and the ever important logical tests– ubiquitous in data analysis. Number 3, we’ll make summary
reports with Excel spreadsheet formulas. Then in number 4, we’ll
make summary reports with standard pivot
tables and slicers. Then we’ll talk about
visualizations, tables, charts, conditional formatting,
and dashboards. Then 6, we get our
first introduction to Power Query, where we get to
learn how to clean, transform, and import the data. We’ll talk about VLOOKUP which
sometimes is good in the Excel spreadsheet, the
relationship feature to create Power
Pivot data models. We’ll talk about Power
Query and Power Pivot together for big data, and
then Power BI desktop and Excel in Power BI Desktop together. Now the downloadable files
and practice problems. That means every
video that you watch, you can download all the files,
the Excel files, Power BI, and the source
data files, so you could follow along with exactly
what you see in the video. There’ll be practice
problems after each video and some PDF notes
summarizing each class video. Now what will you gain
after taking this class? You will have experience with
all the power tools in Excel used for data analysis. You’ll be able to
take your own data, convert it to refreshable
reports, visualizations, and dashboards that you can use
for your own decision making. And finally, you’ll have
introductory level skills in data analysis, So you can
move on to more advanced data analysis and business
intelligence classes for free here at YouTube. And in fact, you can go on
after this 11 video class and study Excel Basics. Now Excel Basics covers the
same data analysis topics that we cover in our class. But if you like formulas,
that’s an awesome video. If you like advance formulas,
the Highline College Advanced Excel class is for you. And most of you
will probably want to move on to the Highline
College BI348, Microsoft Power Tools for Data Analysis. That’s the MSPTDA class. And if you like
what you see when we learn about the new
Office 365 dynamic arrays, there’s a whole playlist of
videos just on that topic. All right, if you
like that video, be sure to click that thumbs up,
leave a comment, and subscribe, cause there’s 10 more videos
coming in there’s E-DAB class. All right, I’ll
see you next video. [MUSIC PLAYING]

Tailor your business solutions with PowerApps and the Power Platform

>>Hi. This is David Yack, and in this module we’re
going to talk about tailoring the Power Platform through
your specific business requirements. This is the second module in
a three-part video series. In the first module,
we did an overview of the Power Platform and the components
that make up the platform. If you’re just joining us now, you might want to consider
going back and reviewing the overview video before
continuing on to this module, and then after
this module join us for the third and final module
on extending. This is where we dive
deeper into some of the traditional
development waves that you can extend the Power Platform and
unblock complex requirements. Before we get too far into
the content of this module, I want to take a second
to overview what I plan to cover as
part of this module. We’re going to start by
talking about solutions. Solutions is the fundamental concept
to understand with the Power Platform
because it allows you to track all the customizations
that you make. The apps you create,
the flows you create, and be able to transport those
from Dev Test to production. So it’s a fundamental key part of the application lifecycle
management of the platform. The next topic we’ll
cover is data modeling. In this topic we will
look at how you can use the Common Data Service to
store application data. We’ll look at how to take
real-world concepts; things like people, places, other things that you track
in your application and model those with data relationships
in the CDS database. Next, we’ll cover
building applications. This is probably one of the more exciting topics that we’ll cover in this module because it really
brings things to life for the user. This is what they interact
with on a day-to-day basis. We’ll cover the types of
applications you can build. We’ll look at some
of the app features. In fact I’ll go build
a couple apps and show you how you can go about
doing that and also we’ll finish the topic discussing a little bit of what’s on
the roadmap for PowerApps. In the next topic, after
we cover building apps, we’ll move on to automating
things and we’ll dive deeper into using Microsoft Flow to automate
things in your solution. Our final topic we’ll cover
in this module is around application lifecycle
management or ALM. We’ll come back where we
started at the beginning of this module talking
about solutions and we’ll build on that discussion with a little bit more look at how
we move things from Dev Test to production including
how we can use Azure DevOps to automate
some of that process. Let’s go ahead and jump in and
get started with our topics. Before we dive in and
talk about solutions, there’s one other topic I wanted to make sure to cover first to give you some fundamental understanding of how the Power Platform works in
an Azure Active Directory tenant. So when you sign up for
a Power Platform license, any of these cues, that all exist in an Azure Active
Directory tenant. So that is the bounding
box that you can see in my diagram the Contoso has. Within that you have
one or more environments. Every organization has
a default environment. Think about this default
environment as being where you build things for
personal productivity. So if you build a flow, you build a canvas app, and you’re just going
to use it yourself, that’s where you will put it
as in the default environment. If you’re going to build something
that’s more production oriented or something used by
everybody in the company, you might want to consider having a little bit more of
a lifecycle around that. You might have multiple environments. In that example, you might have a development environment that essentially tracks where
you build the application; a test one that you do go
about testing the application, and production one where users
actually run the application from. Now environments are
simply containers that administrators can use to
manage the apps, the flows, the connections, and other
assets that you build along with giving permissions to users
to use those resources. If you have Common Data Service
involved in your solution, each environment can have a single Common Data Service
associated with that environment. So if you had three environments, you would have three Common
Data Service instances if that was how you want to configure things and each would have their own metadata
associated with that. As we talk about solutions, solutions will be created in the context of an
environment and will be used to be a container to reference
a particular set of resources, apps, flows, and so
forth that make up your solution that will move from
one environment to the next. So with that understanding
of environments, let’s talk about how solutions define a container to basically track
the customizations you make. So when you go and
create an app or flow, you have the option of creating that within the context of a solution. One of the things I do when
I start a new project, let’s say I was going to go ahead and track permits that we issue for changes that people want to make to a building and we want to
do inspections on that. That’s the scenario I’ll
use in some of the demos that I’ll do as we go
through this module. Now when I start with that project, what I would probably
do is go and create a new environment that would
be my dev environment. I would then create a solution
that I would track all the apps, flows, CDS customizations
that I make. So if I create an entity
to track permits, I would create that in the context
of the solution and that would be what I use to basically move that from one
environment to the next. So in addition to my
development environment, when I got ready to release this, I would create a test environment
or production environment that would allow users to go
in and test what I built, not contaminate it with any of the other development
things I might have in progress and that once
that test was successful, then that same solution would
be deployed to production. Now to support that,
solutions support the concept of importing
and exporting. So from my development environment, I would export the solution. I would then import that into my test environment to
be able to do that. Now it’s important to know it’s not just the applications that you build that can be installed
through solutions. This is also how Microsoft
installs any of the Dynamics 365 apps that you license
into your environments. These are just solutions
that get installed. In fact, some of
the applications can have multiple solutions that
make up the complete app. As we get a little
further in the module, I’ll explain how
multiple solutions can be installed in one
environment to make up the overall application suite that the user interacts with
on a regular basis. The same is true if you
go to AppSource and install any of the third-party apps built by independent
software vendors, ISVs, these are also
installed using solutions. Solutions allow you to install an
environment and also uninstall. That makes it perfect for trying out an application in an environment. There are two types of solutions,
unmanaged and managed. When you create a new solution
it starts out as unmanaged. Unmanaged solutions are
used during development. They are modifiable directly so you can make changes
to it; add components, remove components and
this is what you export if you want to move it to
another development environment. Solutions can become managed
when you export them from environment that has
the unmanaged solution. When you are ready to
move your application from Dev to Test to production, that is when you would export
the solution and choose the managed option when
you export the solution. That gives you a solution
file that you can import into the test environment or the production environment and it’s
no longer directly changeable. It’s meant for distribution to
the non-development environments. In an environment, you can
install multiple solutions. Every environment
starts with the CDM, Common Data Model System entities already pre-installed
in that environment. You can go ahead and
install other solutions in and they can all
co-exist together and in fact the applications that you build can build on each
other using layering of solutions and what the user sees is the combination of
all those solutions. So let’s take a healthcare example where I have installed
in the environment some Common Data Model
healthcare extensions that were put out as
an accelerator by Microsoft. That would have things
like patient care team, other common health care
entities that might exist. Contoso who’s the
organizations that’s building the solution might have some other
things that they want to add. They may want to add some attributes
to the patient entity or add other custom entities
that are part of their common solutions that multiple applications
might take advantage. Those could be packaged up in a solution and imported
into an environment. Now what the user sees or if you
build apps in this environment is the combination of all of these solutions that
have been pre-installed. So if I was going to build
a device inventory app or a kudos app for my employees do; say thank people for good care
that they gave to patients, those would see all
the entities and attributes combined together that any of
the solutions in that environment. So from Contoso common to
health care extension, as well as what comes out of the box
with the CDM system entities. Most things built on the Power
Platform don’t get built once deployed and they’re
never changed again. Probably one of the most
productive ways that you can take advantage of
the Power Platform is to take advantage of its iterative
ability to build solutions, not have to boil
the ocean all at once. By that, we might get our application to what might be considered
the first minimum viable product that
we could release to users to actually give
some feedback on. They might use that for
a little bit of time, give us some feedback, Tell us about some problems. We might go through make some updates and then
we deploy that again. The solution framework supports this type of incremental
development by making it easy to import new versions and do upgrades as you make
changes going forward. So a common cycle might
look something like this. You make the changes, you
build your applications, your flows and CDS changes, you export as manage, you install that into tests and
ultimately into production. The users give you some feedback. They tell you that
there was a small bug. Rather than shipping
the whole solution again, you create a patch. A patch contains just one attribute, one component within the solution
that you want to fix. You then export
that patch and install that patch into test and
then into production. Now you may have
four or five patches that you create before you build
the next version. Once you are ready to
build the next version, you can roll those patches up into the version two of
the solution that you’re going to make further changes to and then you repeat this cycle
over and over again. That’s how solutions help support an incremental building
of an application. Now let’s go ahead and jump into a quick demo where I’m going
to go ahead and create an environment and create
a solution that we’ll use to track the changes
that we build. Okay, I’ve logged into the Maker portal and I’m
looking at my environments. I currently have the default
environment, one other one. What I’m going to do is
go ahead and create one that I’m going to use
for my development work. So I’m going to go to,
click new environment. I’m going to call this permit Dev and we’re going to go
ahead and create this as a production environment
in the United States. Once the environment is created
it’s going to ask me if I want to have a common data
service database in there. I’m going to go ahead and say yes. I’m going to choose United States
dollar for the currency and I’m going to choose English for the language and let it
go ahead and create. Now that it’s created, am I go back to the Maker portal, I’m going to change
my environment to the permit dev. It may take a minute for
it to show up for you. Now that I’ve created my environment, I can go ahead and create a solution. You’ll notice that I
have a default solution and a Common Data Service
default solution. The default solution gives you a good way to show everything but you really don’t want to use
it for making any changes. If you go to create data
and create an entity, it’ll end up in the Common
Data Service default solution. Right now this is an empty solution. But what I want to do
because I’m going to create a permit
management application. It’s going to have some CDS assets. It’s going to have a canvas app,
a model-driven App. I want to go ahead and create a new solution that I
want to add this into. Now once I’ve clicked Create, I’m a go ahead and give it a name. I’m going to create a Publisher. Now, the Publisher is
used to put a prefix on the entity and track things
altogether that you create. So we’re going to call this Contoso. You may already have one
created in your environment, but the first time you create
it in a new environment, you do have to establish it. So here, I’m setting the prefix as well as the options
set value prefix. So if we create some options sets, we’ll see that number used
there and I’ll go ahead, and say “Save” and “Close”. We’ll go ahead and
pick that publisher, we’ll give a version
number for our solution, we’re going to start out at version one and we’re going to
go ahead and “Create”. Now essentially, we’ve
created a solution that we can track all our customizations
and from within here, you’ll notice that right now it
doesn’t have any components, but I can go create new components, I can create apps, I can create dashboards, entities, flows, reports, and
a whole bunch of other stuff. I can also add existing assets. So if I already had
some things in there or if I wanted to maybe use
the “Contact” entity, so for example, maybe
I’m going to use the Contact to represent who’s
going to request changes, I would just simply add that
in and I could choose it, maybe I wanted to modify
some of the existing fields, I could go in and select the different fields or
relationships, or forms. What I would do is, I would
add in the things that I was going to modify it
to be able to do that. For right now, I’m not going to
go ahead and select anything, but I will go ahead
and add that in so we have something in
our solution that we can see. So as we go through the rest
of this module and we build out the solution as
we do the data modeling, I’ll add the entities in. As we do some of
the other things like building the applications
and building the flows, we’ll do all that in the context of that solutions and
we’ll see this list grow as we work on the rest of our assets throughout
the rest of this module. Let’s move on and talk about the Common Data Service
and implementing a data model for our solution
in the Common Data Service. If you recall, I’m using a permitting
application for buildings. So you want to make a change, you need to get a permit, you need to have inspections, and that’s what I’m
going to model in this. If you listened to the overview, you will remember I talked about
how CDS is a hybrid database where it essentially abstracts the underlying technology
that’s implementing. So there’s relational, there’s
document, there’s file storage, all under the covers of CDS and that is abstracted into the concept
of entities with fields, with relationships
between the entities, and that’s how you model real-world business problems
into the Common Data Service. As part of data modeling, you’ll identify the entities, the fields, the relationships
that you need to create. As you create those relationships, they can be many to one, one to many, as well as many to many. So for example, in my
permit application, I’ve got permit that has inspections. Now, one of the things
that you’ll see me do when we go into the demo is I’ll create that so that
if the permit is deleted, the behavior on
that relationship will cause all the inspections to go away. I’ll use the parental
relationship behavior on there to effectively
remove the need for me as an application to automate the delete of the
inspections if you delete the permit because
the inspections no longer makes sense to stay around
if I delete the permit, because they only make sense
in the context of that permit. So relationships behavior give you that first level of automation
at the data layer for being able to automate how you
want to handle things when actions happen across
the relationship to a parent record. As many businesses these days
work in a global environment, they may encounter
the need for dealing with multiple currencies as well as multiple languages
in their scenarios, and that’s one of the things that Common Data Service has
out-of-the-box support for. So when you create a currency field, it actually adds two fields to the entity that you’re
creating that field on. One that tracks
the transactional currency that you did that in and one that tracks the base currency that
the organization is configured for. This allows you to have records that have their own individual
currency selection, as well as track the exchange rate between when the
transaction was recorded, giving you that out-of-the-box
support for multiple currencies. Same thing with around languages, one of the things that
the platform does is track all the metadata for
labels and descriptions, and all of those can be
exported and you can translate those into the different languages
that you want to support, that allows you to build your
applications that have the labels in the native UI language that the user is comfortable
interacting with. One of the things that’s easily overlooked is some of
the automatic assets that get created when you create a entity in CDS and I’ll contrast
this to for example, if you go create a SQL database
and you create a table in there, you really don’t get as much of a robust application set
of assets that you’d get with the Common
Data Service and that’s the value that the
abstraction layer provides, on top of the underlying
technologies that is abstracted by the concept
of a CDS entity. So in this example, when I create my new entity Building, I get several things in
here, security model, forms, views, automation,
developer API. Let’s start with security models. So effectively, one of
the things you have to often build for an application
is the security model, and CDS implements
a role-based security model. This has the concept
of a security role. A user can have one or more
security roles that combine together to give that user their entitlements to what
they can do with the data. You can also define
the entity ownership. So records in CDS My Building
can either be organization owned where everybody has
access to it or they don’t, or it can get more granular
down to where users can be assigned as owners or teams can be assigned as owners of the record, and security can follow that model
as you’re granting access. You also have the ability to get
down to the field level security. So on Building for example, if I had a field that
was more sensitive data that I didn’t want
other users to have access to, I could turn on field
level security for that and then grant that to only the users
that need to be able to read it, or update or modify that data. When you create the entity, a default set of forms and views are created for use in applications. This makes it easy to
later than compose applications that leverage
those same views and form. You can go in and modify these, and these definitions
can be role tailored so that individual applications
or individual users, have access to just what they need and just the fields
that they need. When you define an application, you’ll actually compose it from
the overall set of forms and views that you’ve defined
associated with that entity. From a process automation standpoint, there’s an event pipeline that’s
built that allows triggering of process automation
after records are created, updated or deleted in the platform. So that means that if I have
a flow that I want to run, it can be automatically triggered, I can get down to what specific
fields that I want to run. Using developer technologies, as we get into the developer
module later on, we’ll talk about how there’s an event pipeline that
developers can hook in before and after that operation
happens in the platform, and that is all built-in
and you don’t have to do anything that
set up that plumbing, you just have to register
your custom logic or your flows to receive those particular events that have been triggered
by the platform. Another common line item
on the budget for a typical project built with low-level developer technologies
is building an API that abstracts you from
the underlying technologies. So for example, if we were
creating this in SQL, we would write something that would
do the calls to SQL but would provide a layer that we’d actually
build our application on. Effectively, that’s what
you get when you use the connectors through flow
or through a Canvas app, you’re talking through the API
that the platform creates. Essentially, the
difference between using this and using the SQL API
directly for example, is the developer API that you get
with the Common Data Service, implements all the
security as well as the business rules that are
implemented at the data layer, as well as any process automation, are all respected by
the developer API when you make calls to
create or read records. That developer API that’s created for the entity is what is
interacted with when you use the Common Data Service Connector through Canvas apps or flows. It leverages that API that’s built for the entity
when you create it, so you don’t have to build any additional API logic
to be able to do that. Now, let’s jump into the portal
and in our solution, let’s add a few entities
so we can see how these all work together and some of the things that we’ve
been talking about. Now, I’m back into the solution
that we created in the prior demo, and I’m going to go ahead
and create our data model or at least part of it as we watch. I’m going to go ahead
and create an entity. Now, the first entity I’m
going to create is going to be the Building entity. You’ll notice I can
pick a primary name, I can decide if I want to have notes, you can do some other settings
like set the ownership and some of the other things that you can explore
on your own time. I’ll go ahead and
create that right now, I’m going to go ahead
and add one other field, this is going to be
simply the Street. We could add other address fields
on it for the location, but I’m going to leave
those for you to imagine that they were on
there in the essence of time. Go ahead and save the entity. I’m going to go ahead
and add another entity, this is going to be my Permit entity. On this one, I’m going to go
ahead and enable attachments. This includes notes and files. This will allow us to attach
some comments to the permit. So as we maybe interact
with the customer, we can go ahead and track
some of those notes. Now, because I’ve turned on notes and it’s not able
to be turned back off, it’s just making sure
that I’m okay with that. I’m going to go ahead
and add a field. We want to charge for
getting the permit. We’ll just call this fee, and I’m going to go ahead and look at the different
data types here. You’ll see there’s a whole bunch
of different data types, several texts with
some formatting, whole numbers, and you can do time zone, duration, language, date, time,
or just date only. We’re going to use
the “Currency” field. We’ll look at some of the other ones as we get a little further along, and we’ll go ahead and add that, and we also are going
to add another field. Notice we can add
multiple fields at once, quickly creating the data model
we have on there. Sometimes, we have to waive the fee. So we’re going to
create a fee waiver, and this is going to
be a two-option field. So a Boolean yes or no, come down to “Two
Option”, then close. We’ll actually do
a business rule on that in a little bit so that if
the fee waiver is there, we won’t require the fee to be on. Go ahead and save the entity, and finally, I’m going to
add one other entity so that we have enough to
build an application with. This one’s going to be
the inspection request. You’ll notice in the background, I didn’t have to actually
hit “Save” there, but my entity had been
provisioned successfully. So it did that in the background. Now, what I want to do is
I want to go ahead and add a relationship on here. So I want to add a relationship from the inspection to the permit
that it’s related to. So I’m going to go ahead and
add a many-to-one relationship, and that is going to
be with the permit. So I’m going to scroll
down and find the permit, and go ahead and add that
in, save the entity, and I’m going to do the same thing on the building because it’s ultimately the building can have
many permits issued against it. So I’m going to create a one-to-many
from the building and we’ll associate that with
the permit as well. So essentially, we’re building up the relationships all
around our entity on here. Now, one quick change I want
to make just to show you how easy it is to go back and
change things on the model, I want to make so that that
relationship between inspection and the permit is a parental relationship so that if we delete the permit, we want to essentially remove the inspections
that are related to it. We left that option as the default. So if I go double-click
on this again, go into “Advanced options”, we’ll see the type of
behavior set to referential. I can change that to parental, and what’s going to
happen now if I delete a permit once I’ve made this change, it will delete all the inspection. So that’s how you can automate
some of the management of the records across
the relationships. Now that we have
our basic entities created, I want to go ahead and
add a business rule. The rule I want to do is I want
to do this on the permit entity, and basically if the fee
waiver is turned on, I don’t want the fee to be required. So I’m going to come over
here to “Business rules”, I’m going to go add a business rule, I’m going to go into my “Condition”, and I’m going to say, “Check if fee waived.” We’re going to check if the fee waiver field is equal to yes and then click
“Apply”, and if it is, then we’re going to “Set business
required”, set not required, and we’re going to set this
as “Not business required”, and we’re going to set
that on the “Fee” field, and then if it is required, we’re going to drag this over here, and we’re going to say on here, then we’re going to
say “Set required”, and this is also going to
be on the “Fee” field. We’re going to make this business
required this time, and we’re going to go ahead
and give our rule a name, “Set required if not waived.” We’ll go ahead and save
this rule and activate it. Now, at this point, this rule becomes active. So when somebody uses the fields, it becomes a required field
if the fee waiver is not set, and we’ll see that come
to life when we go build a application that
uses some of the data. Now, you’ll notice
if I come back over to the portal and
look at the solution, we’ve got a few more things in here. We’ve got a business rule
that’s now showing up set required if not waived. One last thing I want to
be able to do is I want to jump over to the Form Designer. Now, in the Form Designer, you can add all sorts
of things on here. So you can add the different layouts, you can add the
sections, the columns. What I’m going to do is I’m
going to keep this real simple. I’m just going to go
ahead and drag on the “Building” so that we can add the building that
this permit is related to. We’re going to add the fee, and then I’m also going to
add the fee waiver on there. You notice how quickly I can go
ahead and put together this form, go ahead and publish this, and the final thing I want
to do is I want to come back and I want to use one
of the other designers. I’m going to go into “Views”, and if I open up my active permits, you’ll notice that it’s
built a default view for us. When you look at
a list of the permits, this is what you’re going to see,
and so what I want to do is, I want to add on to this that
we have the building in there, and that we have the fee that
they paid for that permit. We’ll make that a little bit bigger, and we’ll go ahead and save, and that’s how we
customize the views. You can build multiple views.
There’s criteria. So down here, I can come
in and edit the filters, and this allows me to build
all types of criteria. So I can say where the status, where the building, created
by is in the last six months, all kinds of criteria
so that your view filters the data the way
the users want to see it. So that’s a quick look at building a data model and building some
of the other assets around it. We also built the forms
and the views, and later on we’ll actually build an application that uses
some of these assets. In the introduction module, we introduced you to
PowerApps is the ways that you build applications
on the power platform. We talked about how if you’re doing
any Office 365 customizations, you use PowerApps, if you’re
modifying a Dynamics 365 application, you’re modifying a PowerApp, and if you’re building
a custom application for either your own internal
use or as an ISV, PowerApps is the way that you build the applications on the platform. Designer or Canvas Studio, you compose the application
and you leverage the connectors to work
with data and services. When you start creating a PowerApp, you’re going to make a decision
of how you want to start, whether you want to start with a
Canvas app or a model-driven app. How you make that decision depends on how you’re going
to want to control the user experience as well as the data that you’re working
with in the application. If you want complete control over the user experience,
in other words, you want to start with
a blank slate and define what the user
experience looks like, then the Canvas apps gives you that complete control over
that user experience. If you’re going to start with data
from the Common Data Service, then a model-driven app
gives you a quick way to get an application up
and running that has lists of data, forms of data. Essentially, data-editing
type applications can be really quickly built using
the model-driven style. Now, if your data doesn’t
come from CDS or it comes from CDS and
some other data sources, the Canvas apps through the
connectors allow you to [inaudible] that data together on
the design surface. It’s important to remember that you’re only choosing where to start. You can always combine, for example, a Canvas app inside a model-driven
app as one of the components, and we’ll talk more about that as
we continue through the modules. If I were to generalize
the PowerApps app architecture, it would look something like this, where you have an app that’s
composed of one or more pages, screens that you combine together, and on those pages and screens, you group things together
either through tabs, sections, or groups, and in those groups,
you have components. The components could be as simple as a very basic control
like a text input box, or it could be a more complex
control that is more of something built by
a custom developer or a Canvas reusable component
that could be built using similar constructs that you
will build the Canvas apps with, and we’ll look at that as we jump in and go through a demo
of building of apps. Now, I mentioned that starting from a model-driven application if
you’re working with CDS data can be very beneficial because
it’s really quick to get an application up and running
that has a list of data, forms for editing the data, but it also comes with a number
of other features that are just, they’re out of the box without
you having to build things. For example, things
like personal views allowing users to define
views that they want to have, maybe records created
in the last six months, records that have been inactive, and it also provides controls, things like timeline
activity views that allow it to see all the
interactions a record has. So for example, if you’re tracking appointments, e-mails, phone calls, all sorts of interactions
against a record, the timeline view gives
you a very easy way to see what’s been
happening on that record. From a user productivity
point of view, some tools like Excel Integration or Document Templates are built-in, allowing you to quickly create
Word documents for example, from some of the data that’s in the list as well as other
productivity things for the user, like recently viewed,
recently pinned. You don’t have to go build
those into your application. Earlier, I talked about
the ability to do localization of the metadata
for entities in the field, just changing the labels
and having them display in the local language. That all happens automatically. So if you have the language
configured on your environment, the user can choose
that as their language, so if I wanted French or German, and then the user experience
would be adapted to use the labels that you’ve done the
localization on for that language. If you didn’t provide
one for the language, it would fall back to the default
one for that solution. Now, let’s actually jump over
and build a couple of apps. We’re going to build, first, an application that will be used by the back office team that
will manage the permits. This will be a model-driven
application that will allow the user to
basically input the permit, schedule the inspection,
and then we’ll build a Canvas app that will be
used by the inspectors. These are the people that
go out into the field. They’ll be using their mobile device, so we’ll give them
a very tailored application that can just do the inspections. Let’s go ahead and take a look at building both of these applications. Now, I’m back in the solution. We’ve got our data model
that we created, and I’m now going to go ahead
and add an application. I’m going to create
a model-driven application for the back office to be able
to manage the permit. Call this Permit Manager, and we’re going to go
ahead and pretty much take the default options here. You could provide
your own app image and some other settings there if
you want, a welcome page, which is a splash screen, but I’m going to go
ahead and click “Done”. I come to the App Designer, and I basically see that I don’t currently have
any entities configured, any dashboards or processes, and my Site Map is asking
for me to configure it. The Site Map controls the
navigation of the application, and this is where we
start composing things. So what I’m going to
do is go into that, and I’m going to go ahead, and in here I’m going to change
the area to be permit management. The group called as Issue Permits, and then in the area, I want to go ahead and start
putting some of my entities in. So I’m going to go to “Entity”. I’m going to go ahead
and put this to Permit, and that will cause the Permit
to be in the navigation. I’m also, just for
my own convenience, going to go ahead and
add in another sub-area. I could do this from there
or I could come drag it from components like we did
with the business rules. I’m going to go ahead and on here, I’m going to put “Entity” in again. Now, you’ll notice that you
can put some other things: the Dashboards, Web Resources. You can even point to a URL, so maybe you have
an external site that you want to bring into
the app navigation. You can do that as well. I’m going to bring this in and
this is going to be the Buildings. We’ll go ahead, and “Save”
this, and we’ll “Publish”. Now, at this point, we’ve successfully configured
the site map for our application, and we can go ahead, and save, and close this, and get
back to the designer. Now, notice what’s happened. Because we’ve added
those entities to our navigation, we’ve now got those
referenced by the app. They show up in the list. We can actually work
things from here. So we can actually
click on these items. This lets you control
what forms would be available. You can actually have
multiple forms for an entity, multiple views, and from here, you can actually
de-select and configure specifically for this
application what forms, views, charts, dashboards are available to users
of that application. We’re going to take it, just
leave it as all for right now, and I’m going to go ahead and “Save”, and I’m going to go
ahead and “Publish”. I’m going go ahead and
run our application. That’s how quickly it is to build a very basic model-driven
application. So essentially, at this point, we’ve got ability to
do some data entry. So I’m going to go ahead
and create a new building. We’ll call this
Microsoft headquarters, one redmond way, “Save and Close”. Then, I’m going to go to “Permits” and I’m going to go
create a new Permit. This is going to be a Room Addition and we’re
going to pick the Building. Now, notice because this is a relationship between
the Permit and the Building, I now have what’s referred
to as a lookup field. It’ll give you a quick shortcut that it records you’ve used recently. You can create new ones from here. You can search. This would actually launched a search process where
you can change the views. You can search for the records. I’m going to go ahead and
pick Microsoft Headquarters. Now, notice that my fee is required, but watch what happened, and I can tell that because there’s a little red asterisk next to it. Now, if I change this to
“Yes” that the fee is waived, notice that it’s no longer there. That’s the business rule that we created that it’s
implementing that rule on the fee field allowing me to
make it required or not required. I could also use that to set values and all other types
of things on there. So we’re going to go ahead
and leave that not waived, and go ahead and set
it to fee at $500, and go ahead and save the record. Now, you notice over
here on the right, that’s the Timeline control. We had that because
we had notes enabled. So Establish Permit for Bill Gates, and I could, will pay later, and I could go ahead and add notes. I could attach things to it. I could also add
other activities to it. So things like if I wanted to
have tasks and phone calls track, those could all show
up in the timeline, so you could see all of
the interactions that happen there. You can also go to “Related” and
this is where you’re going to see other related records
to this entity. So I have “Inspections”. So if we had some inspections, we could see what those inspections, and that’s how quickly you can build a basic model-driven application. Now, let’s go ahead,
and switch gears, and look at building
our Canvas application for our inspectors
that are going to go out into the field and
do the inspection of that room addition once
it’s ready for inspection. Now, I’m back in our solution, and notice that we’ve got our
Permit Manager showing up in here, our model-driven app, and
also a client extension, that’s our sitemap
for the navigation. Now, what I’m going to do is go ahead and create our Inspector application. So I’m going go ahead
and create an app. But this time, I’m going
to choose “Canvas”. I’m going to use the
“Phone Form Factor” because they’re going to use
it on their mobile app device. Once the studio starts, you find ourselves in the application with a blank slate that we
can do whatever we want. Now, notice we don’t
have any application, navigation, or anything,
that’s all up to us to build. So the first thing I’m going
to do is I’m going to go ahead and connect to one
of our data sources. So I’m going to go to
view “Data Sources”, and I’m going to go ahead
and add a Data Source. This is where you
can get all kinds of different data from SharePoint
to Adobe Creative Cloud, Adobe Sign, any data or service
that is available to connect, you can do from here. So I’m going to use the
Common Data Service. So I’m going to say,
Common Data Service, and I’m going to go
ahead and choose that, and I’m going to “Create”. It’s going to have me choose
the entity I want to work with. Now, I want to work with
inspections right now. So I’m going to go ahead
and choose “Inspections”, and now that’s associated
with my application. Now, what I want to do is I want
to go ahead and give a quick list of inspections that this inspector
has available to them. So I’m going to come in and I’m going to do an insert of a gallery. I’m going to make
this a “Vertical” gallery. We’ll leave this blank for right
now because I’m going to go ahead and customize the format of it. Now, I’m going to go
ahead and add into this gallery a label that will
be the name of the inspection. So we haven’t connected
this to any item yet. Right now, it’s just set to
this customer default galleries. So notice what’s
happening up here is I clicked on this gallery and
control that I’ve added. It has different properties
that you can work with. This is the items’ property that says what data is connected to it. I’m going to change
that to be Inspections. Now, notice what happens
when I start typing, I get the IntelliSense hints
that makes it easy for me to find the data that
I want to connect to. You’ll notice that I’ve
now got this populated with some data it’s pulled
in the created on day, but what I really want to
have is I want to have that be the name of the inspection, which will tell me a little bit about what type of inspection
I’m doing on there. Now, you’ll notice that I get
real-time as I make these changes. I’m able to see this happen on here, and I’m able to real-time
make adjustments, and see the results of that. In fact, I’m going
to go ahead and add the street address of the building. So I’m going to come in here and
I’m going to add another label. Then, this second field, what I want to do is I know
this is related to the permit. So I’m going to be able to
just simply say.permit, and that uses the relationship, and that gives me access to
all the fields on the permit. So I wanted to just show the name of the permit that
I’m putting on there. That way, we can see that
it’s a room addition and it’s add a restroom. Now, if I want to size
this up a little bit more, you’ll notice I can pull this up. If I wanted to each item
to be a little smaller, I could go ahead and do that. Now, there’s all kinds of
things that you can do on here. So we could have forms. So like if I needed
to add an inspection, I might have them use
a “Edit” Form to go ahead, and fill out the results
of the inspection, and do update some fields on it. I could do a “Display” form, which is more of a read-only. You’ve got “Media” controls. So let’s actually go ahead and
just add some navigation on here. Let’s first of all, we’ve got our first screen. You’ll notice from here, I
can do all kinds of things, like I can rename this
and call this MainScreen, and I can go ahead and if I want, I can add a new screen. This gives you some ideas of layouts. Do you want it scrollable? Do you want it to be a list? I’m just going to go
ahead and choose blank, and then I’m going to
call this the Inspection. On here, what I’m going to do is maybe they want to actually go
use one of the media controls. So I can upload an image, I could use some of the device
things like scan bar codes, I can also use the camera. Now, what we’re going to do is go ahead on here and just
for a simplicity, we’re going to use the display form, will display some information
about the selected permit. So what I’m going to do is
I’m going to go ahead and set the data source on this display form
to the inspections, and I’m going to go ahead
and set the item none. Notice how I’m working with
these properties to buying them to the other control some will
say this is gallery1.selected. That’s the item that we have
selected in the other control, and I’m going to go ahead
and edit the fields. Now, what I’m doing here is I’m essentially taking from
the fields that are available. So I’m going to go
ahead and bring on the created on-field, the name field, we’ll just keep it as
a couple of those may be modified on just so we can
see if it’s been changed, and we’ll go ahead and drop those on. This gives us a display only view, you can actually set some of
the properties depending on the field type you can choose
how it’s going to display. Now, what I want do is go ahead
and set up some navigation. So we’re going to just
so we can do this, I’m going to drag this
down a little bit, I’m going to go add an icon, and we’re going to add a back button. We’re not trying for
the prettiest thing on here. Notice the OnSelect that’s
a behavior property. This lets me do a formula. Formula is how you
cause things to happen. So I wanted to do and navigate
back to that prior page, I could use the navigate and
specify the actual page, but what I’m going
to do is simply use the back function to tell it to go back to whatever navigated to it. Now, to get to this page, I’m going to go back
to the main screen, edit the control that we
have on here this item, and I’m going to go ahead
and add an item icon on here so we can use
it to drill down. Go ahead and click that, we’ll drag that over, and on this one on the select, we’re going to navigate to
our inspections screen, and now we can actually
run our applications. So far we’ve been just previewing it, and I could hold down the ALT key
and it would let me do the navigation from without
launching the application, but what I can also do
is quickly jump into the player by a pit and the play
up here and run the application, and you can see the list
of inspections. I can go ahead and go back, and forth between it. So we can see how you can very easily craft and compose
your own application, but a very different from what we saw with the model-driven application where we just basically said what entities want to navigate
and everything was build, everything we want to have in the Canvas app gives
us a lot of control. It’s a blank slate, but we have to build that out. So things like we might want to have a little bit
of a header controls. So what I might do is I
might come down here, I might want to have
a header control on here. So I might bring this up here, make this a little bit prettier, and you can do all things
to make this personalized, so that we can say this
is the inspector app, this is our name, and we could even go and do
some formatting of that. So we could choose the color or
maybe we want it to be white, and all of this is done visually
through the application, and you can see how
you can incrementally build this as you
work through things. Now, one other thing
I wanted to call out you’ll notice if I come in here on this and I actually change
this permit named to Dave, you’ll notice I get
the little error up here, but also on the right-hand side
this app checker, the little stethoscope up here, it’s highlighting that, I’ve got
a problem in one of my formulas, and it tells me where that
is and if I click on it, it will take me to their. That’s a quick way to know how to resolve errors and if
you have any problems. So app checker is there to give you that real-time until
a sense of what’s going on. That’s a quick look at building both a model-driven app
and a canvas app. Now, that you’ve seen
a couple of apps built using each of the styles
model-driven in Canvas, I wanted to come back and give you a little insight into the road
map of where things are headed. Now, obviously the end goal is
to not have necessarily some of the two different ways that
you build applications as much as the applications are productive
and that you build them today, you’re going to see over time over
the next 12 to 18 months them come together into a single
app designer where you’ll be able to mix and match the application types even more
seamlessly than you can do today using some of the embedded capabilities of
putting Canvas insight model. Now, the first part of
that journey is introducing responsive custom pages into
the Canvas applications, and so that will be coming
as a first enhancement allow you to have a page that not only will be
responsive as you size it, but it will have the
ability to have groupings. So where you can put the components and lay it out very
similar to what you might think of when we laid
out the model-driven app form, and we have the concept
of tabs in the sections. By introducing that Canvas page that will be available for
Canvas apps initially to use. So you could just add that as
another asset to your application. Not long after that, you’ll be able to add that Canvas
page also to a model-driven app giving you an additional
way to leverage Canvas inside a model-driven app. The final step in the convergence of the application types
is being able to use a single studio and
a single user experience for running the applications. When you’re in the studio, you choose the type of
page, form, or view, or dashboard that you want to add
to the navigation of the app and the components can be shared between the different types of
pages whether it’s forms, views, without having
regard to what type of application is whether it’s
model-driven or canvas. The most important thing to
understand about the convergence of the app types is as you
make applications today, they will not be impacted
by the conversion, and the only thing that
will happen as you get down the road and you’re able
to have the apps that are combined is you’ll be able to do
more with the application all within a single studio without leaving to go to different designers. Let’s move on from applications
to talk about Microsoft Flow. In the overview module, we talked about what
a flow looks like. We talked about how
a flow has a trigger that causes the flow
to start execution, and then it has one or
more actions that provide the actual logic that you want to
have happen when the flow runs. Now, as you start to build your flow, the first thing you’re
going to do is configure the trigger that you’re going
to use to start the flow. There are different types of triggers that you can use to trigger the flow, and they have different
characteristics. The first are instant flows. Instant flows are ones that trigger when the user
takes some action. An example of those is the Flow
button in the mobile applications. So when the user clicks it, the flow runs instantly
right after that. If from Excel, you can have it
on a selected row in the Excel passing in the context of that
or from Common Data Service. So from a model-driven
application maybe I’m on the permit row and I want to run a particular flow against that permit that was issued
or against the building, I can have the trigger B when a record is selected and
that will cause it to show in the list in the user experience and
allow the user to click it. Now, with each of the instant flows you can
pass some parameters to them. So on the permit maybe I want
to apply a fee because it was late or the inspection failed and they have
to do a re-inspection, so I could run a flow and as
part of running that flow, I can be prompted for
the $50 extra charge for the additional trip charge for
doing the secondary inspection. The next type of flow
is a scheduled flow. Scheduled flows allow you to run
them on a reoccurring basis. So you might say that I wanted
to start today at 10:00 AM, and I wanted to repeat every minute, every hour, at once a week, these are perfect for
things that you need to run on a reoccurring basis. The next type is
the Power Apps trigger. This allows you to from a canvas
application have a button or other action control on there
that triggers the flow to run. Take a scenario where we have an inspector that’s out in the
field they’re getting ready to go to their next location for inspection and they want
to advise the people that they’re on their way if
the customer had to ask for 15 minute notification
before they arrive. So literally by just simply clicking on a button that could
cause it to invoke a flow, that flow could then do
the check on the record to see if the customer
requested a notification, if it did requests notification
and has a cell phone number, it could use one of
the SMS connectors to send an SMS saying that the inspector
is 15 minutes out, and all that can happen
in the background just by the inspector pushing the button
in the Power Apps canvas app. The final category of
trigger types is Automated Flows. Examples of these are things like new file is added to
a Dropbox folder, new item is added to
a SharePoint list, or the Common Data Service where a new record is created,
updated or deleted, and you can even get
down on for example, on the Common Data Service ones, you can provide scoping as
well as filtering attributes. So maybe I only want to know when the contacts first name and
Last name have changed, any other change to that contact, I don’t want to run the flow. To build the flows, you’ll use
the flow designer which is a visual designer you’ll assembly search for the trigger
that you want to use, you’ll configure any options, you’ll then add the additional steps, and then we’ve got an example of
one here that’s a little bit more robust than the one I showed you
at the beginning of this section. On this one we’re triggering
based on a new e-mail that’s arrived in the e-mail
box of the user. They’re using the Get
my Profile action to find out who their information is. So that would return David Yak
and my e-mail address, but what I’m really interested
in is my manager here. So it’s doing a get on my manager that allows us to get
the e-mail from the manager and allows us to do
a condition check to say is the new e-mail that
arrive from My manager, and if it is then posted to a Slack channel with that particular
information to highlight it. So this is just a simple
self productivity example. We’ll go and build another flow
when we get into the demo on this, but from building this you could also use some of
the tools like Flow Checker. Flow Checker allows you to
highlight if there’s any errors, it’ll highlight what errors exist, similar to App checker was for
the Power Apps Canvas apps. It also has built-in testing
to allow you to test the flow, and I’ll talk a little bit
more about that in a second. Both the built-in checker and the testing capabilities
are designed to make it easier to build flows and resolve problems that
you might run into. This highlights what
Flow Checker looks like. So you can see that I’ve got
three errors that I need to resolve. One of them needs an entity name specified and the other needs
the file name and the file content. So I can click on those, it’ll take me right to where
I need to in the flow, as your flows get a little bit
more complex that helps you find the things that you
need to fix a lot quicker. The testing capability helps a lot when you incrementally build a flow. It allows you along
the way as you’re building it out to test it periodically
to see the results, and then go make additional
changes and do it again. Now, what you have the ability to do with the testing is when you click on “Test the Flow” the first time you have to perform
the trigger action. So if it was when
a record is selected, you go to the application, you’d run it against a record, and then it would run
your flow interactively. You’d see it go through
the steps and you’ll be able to see the outcomes from
each of the steps. You’d be able to click
“Edit” make any changes. Now, after that first time, you would then be
able to use data from a previous run because
you’ve already run it once, and it would allow you to pick from the last few recently runs
of that flow, you pick the record,
you save and test, and it’s going to rerun it again, and you can then repeat that process
going through the test, edit, test, edit until you get the results that
you’re looking for. Let’s go ahead and jump into
the flow designer and build a flow. Okay. We’re back in our solution. What I want to do is go
ahead and create a flow that runs when a new inspection is created and sends an e-mail
to the inspector to let them know they’ve been
assigned an inspection. So what I’m going to do is come
in here and do a new flow, that will launch the Flow Designer. Now the first thing
I’m going to do is I’m going to be prompted
to select a trigger. So I’m going to use the “Search” and I’m going to look
for the Common Data Service. I’m going to choose
the current environment one because building in a solution that selects the environment that
I’m currently in. I’m going to select
the “When a record is created, updated, or deleted.” We’re going to configure that to
run when a record is created. You’ll notice though,
that you can choose to have combinations of
these of it makes sense, but we’re going to go
ahead and stick with that. We want to run this when
the inspections are created. We want to run on any records that are created regardless
of who the owner is, so we’re going to show that on there. Some of the controls
have additional options. You always want to take
a look to see what you have. Now that we’ve triggered, that tells us we have a new record. What I want to do is I want to get the user information
associated with that. So I’m going to go ahead
and do a new step. This time, I’m going to do a Common Data Service
again because I’m going to retrieve the user record that is
the owner of that inspection. You’ll notice that
when I click on this, there are several different
actions I can now take. I can create a record,
I can delete a record, get a record list, update. You can also use
the AI Builder to run the prediction’s off one
of your AI builder models. But what we’re going to do is, we’re going to do a Get record. We’re going to have it
look up the user record. So we’re going to pick users. Now I need to pick
an item identifier. This is the ID of the records.
So I’m going to click on this. You’ll notice what happens
when I click in the field, that it shows this dynamic
content panel over here. This allows me to see data
from the prior steps. What I want to do is, I basically want to go
down and I want to take Owner and I want to take
the value of that owner ID. I’m going to use that
to look up the record. I’m going to go ahead and
change the name of this. You’ll notice on each of these cards, if you click on the dot-dot-dot, you could get settings, you can rename them. I’m going to call this GetUser, and that’s important because
it allows you to easily reference things and know what it is when you’re referencing later on. To keep this simple, I’m going to go ahead
and send an e-mail, where we’re going to use
the Office 365 connectors. So notice now, we’re using
another connector as part of this. So we’re going to go
ahead and send an e-mail. We’re going to specify
who it’s going to. We’re going to do that by using
the e-mail from the other user. We’re going to use
the primary e-mail. Notice that this “GetUser” shows up, so it’ll makes it easy
to find that on there. We’re going to say that
you assign new inspection. Just for simplicity six and
the body of the e-mail, we’re going to go
down and bind that to some data from the first
when a record is created. We’re going to bind that
to the name field of the inspection that
they were assigned. Now at this point, we could actually drag things
around and move things around. We want to give this an actual name, so we’ll call this Notify Inspector. We’ll go ahead and save our flow. Now that we’ve created our flow, what we want to do is
run a quick test on it. Notice that just like app checker, there’s also Flow Checker. I don’t have any errors. If I had some, that would show
up here and I can resolve them. Just like we did in the Canvas app, with the app checker, we can resolve them there. I’m going to go ahead
and click “Test”. Now, you get two options. Remember, we talked about this. I’m going to do the
perform the action, we’ll hit the “Test”. Now at this point, my flow is sitting here, waiting for me to create a records. So I’m going to come over to
my model-driven application, and I’m going to go ahead and
add an inspection record. See if done yet, when save and close. I’ll come back over to my flow. As it picks up that record, we’ll see that start processing. Once a flow is processed, you can look at the results of it. So you can click on
each of the items. You can see what some of the values are and what
the data that was returned. You can see that it’s
sent the e-mail. Okay. That’s an example
of being able to do that. So if we came back to our solution
now and click down on this, you’ll notice that we now
have a complete solution. So we have our entities, we have our model-driven app, we have our canvas app, we have our business rule
that we created. We also have our notify
inspector application flows, showing up on there. All these are combined
in one solution. Now, if we wanted to
move this to test, we would simply come over here, do an export, and we would
basically export it as managed. That would give us a file
that we would then import into that other environment. If you came here from more
of an Azure background, you might be looking at
Microsoft Flow and saying, “Wow, that looks really a lot
like Azure Logic Apps.” That’s no coincidence. Microsoft Flow is built on
top of the Logic Apps Engine, and the majority of the connectors
and capabilities are the same. There is a difference however, in how you pay for execution
of a Logic App versus a Flow. Logic App runs on a trigger
action consumption model. In other words, in the context
of an Azure subscription. For each trigger and
each action that runs, your paying incrementally
for each of those. Whereas, Microsoft Flow is
based on the total run. So if the flow runs five times, that is decremented from
your allowance that you get for a power platform license. There are a couple other areas
that you should be aware of differences between
Flow and Logic apps. One of them is around
the deeper integration that Flow has with the
Common Data Service, including ability to package a Flow with solutions to
make deployment easier. Whereas the Logic Apps is
deployed using the arm templates. Azure Logic Apps have access to
enterprise integration features like B2B EDI that is also not
available in Microsoft Flow. Nothing says that you
can’t use both Flow and Logic Apps as it’s appropriate
for your particular solution. But Microsoft Flow has a lot of
characteristics that make it very desirable to use if you’re building
other power platform assets. As I went through this module, you saw how I use solutions to track the customizations
that I built. Each time we build
an additional asset, we did that from the context of the solution that
we were working with. That was done in
our development environment. We could define test and
production environments that we could deploy
that solution to. The next step in
formalizing and making a little bit more robust application lifecycle management process
out of it would be to leverage something like Azure DevOps
to be able to do some of the actual tracking of the solution
changes that you make. So we could use the Git
Repository that was part of Azure DevOps to store the changes that would allow
tracking the individual changes, and allow teams to have
a little bit more velocity of the changes that they make without
conflicting with each other. We could then use the CI/CD, the continuous
integration/continuous deployment processes that we could
build the pipelines, to basically automate the process of exporting the solution
from source control, building the managed solution, and then using the release pipelines
and approvals if we want to deploy that to our test and
production environments once it got approval from testing. By leveraging Azure DevOps, we would have
a more repeatable process for managing our
application that we built. That brings us to
the end of Module 2, where we looked at tailoring
the power platform for our specific
project requirements. I wanted to leave you with
some additional learning resources, as well as some customer stories
to get you excited about things that you might want to
do in your own organization. I hope all of you join
us in the third module, where we look at extending, diving deeper into some of
the techniques developers can use to unblock
the more complex requirements.

Azure Essentials: Data modeling and Business Intelligence

[Serious Music] – Welcome to Azure Essentials. In the next few minutes
we’ll explore the services Azure offers to help you
model and visualize your data for interactive reporting
and business intelligence. Wherever your data is stored, Azure offers Azure
comprehensive lineup of services to help you ingest, transform
and store the aggregate data so that it can be modeled and explored with commonly used visualization tools, like Microsoft Power BI, Excel and more. Azure’s an open platform.
We want it to give you all the tools that you
need to make sense of the broadest range of data sources, whether you’re working
with well structured operational databases hosted
on-premises or in the Cloud; online data sources, for example
data from your Cloud apps and other reporting services; stores of unstructured
data, such as event logs, emails, documents, media files and more; or even realtime data streams, including telemetry from
sensors and IoT devices. Let’s start with data ingestion. If you’re working across
disparate data sources, you’ll want to first
extract the data you want from each source, transforming
it so that it can be unified and aggregated with other data, and stored in a central data repository. Able to scale to hold all of the data that you might want to report on. If you’ve got structured data in operational databases on-premises, you can leave your data where it is, or you can move it to one of
Azure’s many database options. We’ve got a gallery of
data connectors available to connect to Azure, or
you can develop your own. If you’re working with large
amounts of unstructured data that you’d like to report on, Azure has the scalar compute
power and analytics engines to extract information and
transform it into a state suitable for storing and modeling. Now to ensure that your
reporting stays up to date, it makes sense to automate the ingestion and transformation process on a schedule that suits your needs. Azure offers a range of ways to do this, including scripting your own
batch processes in Azure CLI, or using Azure Data Factory; a full hybrid data integration service. Azure Data Factory allows you to create, schedule and orchestrate your ETL, or Extract Transform
Load workflows at scale, wherever your data lives; in the Cloud, or self hosted on-premises. Now collecting massive volumes of data from multiple structured
and unstructured sources and ingesting data from
all of them in parallel requires a powerful
storage service to give you the foundation for reporting
and business insights. In Azure, Azure SQL Data
Warehouse has the performance, elasticity and compute power
to scale up or down as needed, allowing you to host a
centrally curated repository virtually unlimited in size. But a full data warehouse
solution’s not always required. If your total storage
requirements aren’t gonna exceed four terra bites, Azure SQL server is likely to be sufficient for your needs. A Data Model is the heart
of any analytic system and establishes the structure of your data and the relationships between your data. Whatever the data source,
models provide data views that can be explored for
business intelligence; therefore needs to be
capable of scaling out to user demand and fast. In Azure we focus on enabling you to combine all relevant data into a rich semantic business
oriented data model. Able to cache potentially
many billions of rows of data in memory for lightning fast queries. With Azure you can create this
semantic data model directly in Power BI for an all in
one self service solution, or you can use Azure Analysis Services to build out an IT managed model, accessible by Power BI and
other data visualization tools. Modeling in Power BI or
Azure Analysis Services, is very similar. In each case you create a semantic model, that presents the data as
logically linked tables, mashed up from different sources, presenting a unified, consistent
view of the underlying data using friendly names,
understandable to the business users who’ll be querying this model. Using data analysis expressions or DAX, you can also derive
new data for the model. You can use this to filter the data or calculate and create
new measures and KPIs. One thing to note, there are times where rather than ingesting the
data into a data warehouse, you may ingest data
directly into the model for ad-hoc data modeling. This might be the case
when you’re working with unstructured datasets, where
you’re still exploring data for patterns and structures
not yet supported by the warehouse schema, or where your data needs to stay on-premises. Now if you’re interest in a hybrid model, or ultimately moving your data to Azure and you’ve worked with
Microsoft SQL Analysis Services, or SSAS on-premises, you’ll find working with these data models very familiar. Moving from an existing
on-premises SSAS implementation to Azure’s straightforward. You can move your
on-premises model to Azure and continue to link to your
existing on-premises databases via the Azure Gateway; or you can migrate your on-premises databases too. All you need to do is
give your service a name, specify what capacity you need
and the geographic location where you want it hosted;
and Azure handles the rest. Unlike on-premises implementations, it takes just a few minutes
to spin up a new instance of Azure Analysis Services
and provision more deep provision capacity, to
meet change in business needs. Now it’s in the Cloud, you no longer need to do the capacity planning in advance. You can scale up and out to meet demand. Additionally, with Web designer, you can now connect to the data warehouse and other sources to
develop your data models. With the data model in
place, you can now visualize your data using your visualization tools of like Power BI. Power BI’s a versatile and easy to use way for everyone in your
organization to access rich, interactive reports, and to gain insights from the data from many angles. Using Power BI dashboards
you can create single panes showing complete 360 degree views of your business, project, or department. And you can also provide
realtime streaming of data into these dashboards
from social media sources, service uses metrics or
sensors and IoT devices via Azure IoT services. These dashboards help
everyone in the organization make data driven decisions
and share their other insights with other people and teams. Each user can then build on
top of this as they wish. They don’t even have to be familiar with how to use Power BI. Power Bis support of
natural query language, which means users can
interrogate the model with a Q and A capability,
the data view they need, without having to create a report first. Users don’t even need to type,
as Azure Cognitive Service Integration into Power BI
includes speech recognition too. So that was a quick overview of modeling and visualizing your data
for instructive reporting and business intelligence in
action. Keep checking back on Azure Essentials for more topics, and check out our hands on learning series at the link show. Thanks for watching.