Accelerate your SaaS App development using the power of the Business Application Platform
We're. Ready to get started, good, afternoon. A small. But dedicated crowd. I'm sure, so, now we can see if you fall asleep actually, so, few of you that we will will pay attention to that. So. Welcome to the session about, building. Business apps on the business application platform. My. Name is Julie Julie, Straus I'm a principal, program. Manager, in the business application team, focusing. Specifically, on. The. ISV workload, not, gonna pronounce him loud his last name so he can do had himself hi. Everybody I'm Michael Gray I'm the principal product architect for our business application, is V success team, okay. So, if, the, title doesn't say it but the abstract, was I'm kind, of spelling. Out this is specifically, for, focusing. On is vs and how to build apps on the platform, if some, of you are here that are non Ivy's that absolutely, does not matter and this session will still be relevant but, can I see just for show of hands how many of you are actually building. Apps. For for. Sale or, an, either SSI, or system integrators, or wise V's. Ha. Okay. I'm gonna and how many people are at least potentially, thinking, about how they would leverage dynamics, trying to understand how they would leverage dynamics. Will. Change that then, hopefully. How many of you are already working. With dynamics. How. Many of you already building, on power apps. Okay. It's. A good good. Next good mix okay. So. I. Assume. For those of you who are there working with dynamics, or power, apps all of, them I am sure you have heard our James Phillips the VP. Talk about the, digital feedback, loop such as well for that matter but. We wanted to just bump. It high level and put in context, what the pieces are on the platform so, essentially we think about customers, product, and people, and how. Will. The currency, of data these. Processes. Around these fundamentally. Are changing, literal, every day so, the way we engage with customers the. Way we build our products, and the way we attract and maintain talent. I read. A fundamentally. Transforming. It used to be we, were to gauge with a customer, when they show up in our CE ERP, system, or a CRM system we. Know the name we're entering and we engage now, we have many apps where you're literally creating, profiles for anonymous, users, you already, know them and can map them by the time they log in or you sign, them up for your app and the, same kind, of view of your product.
At. Least building business apps right we collect all the telemetry we understand, where users get blocked where, can we reduce bottlenecks etc. Our, cars right you drive your car we, send telemetry. Back. To how the cars, are manufactured, and, looking. At our kind of the horizontal, apps for Dynamics, 365. The, apps we, deliver as part of the platform sales. Marketing, talent operations. And finance and service are really, all. Located. As part of this digital. Feedback. Loop and. Some of the changes we have been going through for a number of years is really, taking. The apps apart, rather, than being one. CRM, app you now have sales and marketing, more, specialized. But, what is even more important, this, is all working against, a common. Data, platform, common. Data substrate, what, that means is when, you're developing product. When, you were engaging with customers all, the, data and now we. Are making it much easier for that to go into a single. Data store like, looking before we really had CRM, finance. And operations or CRM, and ERP. As. Small, as completely, separate systems, and you will see as we move forward how these systems come, closer, and closer together working. Against, a single data, substrate. Okay. But. Again given, that this is a focus. On is, V there's, a huge role for you to play here, and we get asked, about this all the time like where does the is V ecosystem. Fit, in everywhere. In between and actually on top as well so, the way you can, think, about the platform, you can take the apps that we deliver out of the box and further extend, and. You, can do horizontal. And vertical. Value on top of that so for example you can buy a marketing, app or you, can buy a marketing. App optimized. For banking, right. Or a marketing, app, specialized. For, credit unions what's, different, do, you want to call it a customer, or a member, so, the more targeted, you can get the, more wealth, that is for that entire, ecosystem. To build targeted, specialized, apps on top. Okay. So, stepping back a little we. Had quite a few questions down, in the booth for. What. Is the common data service, what. Is the common data model how, does the things fit together where's, xrm, so. This is a picture of what. Our, systems. Or the platform look like prior. To, march. Beginning. Right where we announced, what we call the common data service. To, all have, you heard about the common data service to all. Some. Of you have so, essentially, before. This we, had we had the business application platform, we, had CRM. And the, marketing, sales and service app built. On top of one platform, which we call xrm there's a huge ecosystem, already. Building. Vertical. Apps on top of that system, extending. The apps we, delivered, then. We have on the other side the ax platform, of finance and operations a separate, data store the ERP, store, also, with a partner ecosystem on, top of that and in them in the middle we introduced, what we call power apps or canvas apps which, was delivered, with what we call common data service, one, oh if, you wanted to integrate the data between. F&O. And ax and xrm, you, would essentially, do that through the common data service, meaning, you, would always move, data to, do that integration. Now. In March we announced, common data service - o which. Essentially. Merged, common. Data service 100 and exo-m. And. What. That means is, whenever. You, build or extend, upon. Dynamics. 365. For sales or marketing, or service you, are working directly against. The common data service. That. Also means that on top of the dynamics apps that we provide you have, the ability to customize, and you have the ability to build power, apps on top so.
There's Some messaging, we'll talk through as well but, that also means you have fewer, moving parts because. You start populating the, common data service, the second, you will use any of the dynamics. 365. Apps. And. There is a little difference in the error so the double errors means we built on that platform that is the data store for. Dynamics. 365. Finance. And operations are, still a separate, store but, we have connectors. That do that you only do one hub and you can push data directly. Into, common. Data service we're, still at a stage where you have to define what they they want to move but over time that will also be, more and more seamless. Obviously. We have done a lot of work with, office. 365, data. From LinkedIn, also attracting. That into, the data platform, into the common. Data service, and obviously. Now is. V apps and, extensions, are. Now not a bar on top of the two of the apps it is, side by side what, that means is before we didn't actually allow you to take xrm, as a platform. And build your own apps without. Dependency. On sales and marketing and service will. Common. Data service to you all we allow you to do that we allow you to have pure. Platform, built, your own apps on top. So. That's a big change for some some, set you, look like I don't, care but, it is it, will give you more opportunities, to go and build apps I liked. Both. Extending, but also building you net new apps. Okay. So. With that one more piece we added we say business. Application, platform, we, have also added bi to that, we always have bi but, we haven't really, done. The work to make it part of the platform so. You might have heard of another announcement we made called. Common data service for analytics, so. We have one common data service, all the schemas, are defined in the common data model so. If you use. Sales, and you, have account as an entity or table, for you those of you used to sequel that table. As soon as you start populating and, using sales that. Table. Of that data is stored in, common, data service for apps you. Can set up data. Sink into, common, data service for analytics, so now automatically.
You Can start building, analytics. App using, power bi on top. Meaning. You do not have, separate, data stores it is all the common data model and, we have different flavors, conceptional. Flavor and an, analytical, layer it, also means as a nice v you, can start thinking about building, analytical. Apps as well as transactional. Apps and actually. For the remainder, of the time we're, going to walk through an end-to-end, demo of what it means to build and extend, etc. Yeah. One. Thing I just wanted to point out really quick on on the, previous slide is that. For many of our applications. For folks who have used relationship. Insights customer, insights, these. Analytic, applications, that we already had are actually, being rewritten, completely. To follow this particular paradigm, so. Within the next year all of these applications, will be rebuilt and a, customer who purchases it has a Dynamics 365, tenant purchases. Relationship, insights for etc, it, will actually be part of their tenant they're not gonna need a separate AI or m/l even though that's what it's built on because that's built into the stack. Make. Sense. Yes. Today. You have to define it and in all full transparency, common. Data for analytics we announced, it a lot of I think the public, preview is, another. I. Think. It's for this summer yes, don't think anyway so there's private preview and. Yes now you have to define what you would like to sync and there's obviously some latency in there their idea is over time it, becomes more and more natural with or, automatic, defining. Because you might have or you will have data. That you never want to flow through your transactional, system like you might have log, etcetera. That you think of CDs. Final it explore, as a kind, of data lake type where you can have more unstructured data as well and much larger data volumes, but, anything, where you want to build a companion. App in addition you. Want to have in the tree in the, common data service. For apps because. It will automatically, flow through. So. For, common. Data size for apps it happened to be sequel, for. Common data service, for analytics, it's also it's based on Azure and. It's. For blob storage for for, actually storage and working, on the computer, on top of that and. Then, obviously for, that as well if you're familiar with power bi are the BI pieces. Analysis. Services, go on top for a lot of that compute, as well since, for right now it's blobstore right so you have semantic. Models, on top for doing your calculations, etc yeah, and one other big reason why they did that is because with the new release and as they they, they continue, the preview you, can actually mount reference. Data from, a separate tenant to, a customer's, tenant or to another SAS implementation. So therefore you don't have to actually copy the data you, can actually say I have a an.
Azure, Blob over here and I have a tenant over here for power bi I can actually reference mount, that to the power bi instance, you, can create a model off that so. The intent is there that that growing. Up story should, be super. Friction-free okay. Okay. Sure. No no, go ahead yeah. Can. You please use the mic yes sorry we, were being sloppy because the room is so small. You. Can. Hear me right now, we can yeah in, the previous slide that you showed where, you know you said you know CBS. Enables, a unique capability, where. Unlike. Previously, where you have to get all of the xrm capability, you can just enable the capability, that you're building in c.d.s and offer that as a SAS solution, how. Does the licensing, model for that work and. The, stock is really, building SAS applications, on top right so how does the licensing, model work and, how does the multi-tenancy. Work because you know my my, multiple. Customers that I sell my service. To may, end up having a slightly different schema, for their own CVS, yeah. So. I just, repeat and some of these I think we will Park because some of them are a little more detailed but. One of them is one, of the question is how does the licensing, work for building, pure. Apps on top of the common data service without the. Dynamics, pieces I think I heard and the second was how does that work, for multi-tenancy, so, if I take the first for licensing, first if. You, build. An app that leverage, any of, the dynamics. 365. Entities. That come as part of the app you, have the full app license, for that if you're, not leveraging any, of those entities which is really how we define, it and use the pure platform, only and what we call the COI entities, then. You have, you then you buy a power bi. Sorry. Power, apps license. So. That is a different, licensing. Model. Obviously. So, that's those two but, it really depends on one of the entities and business logic you. You, used like to extend the app or use any of the core, app entities or do, you built all. Custom, entities, for example, and. Obviously, we're looking at the difference between whether it's, an embedded application, or whether or not you're just placing, an application, into there into their tenant because part of what the platform is intended, to do is change, the paradigm of how we do applications. As well so it's in some cases, that actually maybe a different model that you actually follow, before. You're building your applications, on the platform and actually providing that to your customers, versus today we, actually do have some folks were a pure SAS implementation. And by working with us they said oh and they actually moved much of what they do into. The actual customers. Specific, tenants, so they no longer per, se even have a SAS implementation. And. For, the multi tenant that, is that can be a whole talk on its own so I'll quickly summarize to. Say the. Common data service, for both applications. And analytics. Is intended. For living, in the customer, tenant so. If you want to build a multi-tenant. SAS, app a sure, sequel date of any of the relay or any of the data stores in Azure sequel database Postgres my sequel, is really. Your choice for that but, there are still in to up opportunities. Where, you can feed data from that, into. The, common data service for your customers where they now will have the ability to create their own power apps on top and we do see that so, feel, free to come up afterwards, and we can talk there's, a play for both but, just to be sure, common data services, designed, for, living in the customers tenant. Okay. So. Just, to summarize, what the business application platform. Look like now having, taken you through those, recent, changes, is really, power. Apps which. Now includes. Xrm, flow. And canvas, app from power apps that is what we talk, about as power apps and power, bi you, have the common data services, on each side we, have really connected through, the, definition. All the entities in. The common, data model okay. And, in, addition to act of course, supporting. Dynamics 365. For, building.
Apps Are for extending, and for, building standalone. Business, apps it is also the. Extensibility. Platform. For office, what, does that mean it means that, if you have like. We, you can create business, app that you can embed into teams you. Can have if you have modern, list in SharePoint, and you say customize, you, actually, open, up for the. Maker. Experience. In power apps or if, you want to create a mobile app on top of, a SharePoint. List we, also auto generate. A power app which you can go and create what. Does that mean for us I series it means that customers, will get more and more familiar, to this, tooling for, building, and customizing. App regardless. Of where they are so. That's kind of the intent and where you get the economy of scale and user education and. Obviously. It's all built, on Asha. So. Whatever we do is is kind, of based on Asha and so if you take a technology. Like, flow. Which. Is also share code based with logic apps this is kind of how you get into that, Asha stack, as well but again the core infrastructure, is really Asha, so there's no clips there, yep, yes. You, mean from say office, LinkedIn, etc. Yeah. So. So. We we are working on two levels one which is the integration of their data via their accommodated models with their graph api's, as well. As the fact there's I don't have a time for this but. We. Are looking at what would it mean even for dynamics. To be part of the Microsoft graph all, up and obviously. If that happens, and you'll be able to communicate across the graph for all of that so that's being, talked about now we're. Just debating on what it is but. Yeah. Absolutely. Well and you know one, of the one of the things as Julian was mentioning I think that is also, it's. It's sometimes harder to land I'll be transparent, with some of the IV's and initially. Which is, sometimes. It's the second or third eye it's fee that looks at this and says well you've you've built this vertical, application, or you built this horizontal, application, and all, of a sudden I'm gonna go extend, it and it's actually now easier, for them to go build on it but sooner, or later that's yourself, as well so, you're out there saying great there's a there's, an EMR application.
Out There in the cloud or there's an SAS for education, and now you want to go build on top of that because you don't want to be an EMR for healthcare but you do want to build apps on top of it so we're working to enable through the common data model the ability for you to do that so it's not just about what you deliver it's about how much easier it's going to be for you to deliver everywhere. Else as well. Okay. So. Two, more slides and then we'll go into, demo. And. This. Was also a question that has been coming up in the expo area as lot is like what does it mean that you merged all, of this and if we work from the backend obviously. The, fact that we are defining the, schemas, at a high level across. Applicate. Transactions. And analytics, is is, huge, it also means that as you, engage and, build out for, example vertical, apps you, can go and look at what are the definition, for customer, and built, accordingly, right you can take dependencies. So you can build your own but, that's all documented, there, then. Obviously for the common data service, that, it is a unified. Offering, where you can build apps, horizontal. Or vertical and. The. King dynamics, we have often been talking about vertical apps but obviously we are also opening. Up for the for, the horizontal without. Having dependencies on Dynamics, 365, and, then the fact that we are moving towards a common data substrate, where, whenever, you accrue value, in form of your ëismí apps that, data become, available for. Business users technical, business uses to build composite. Apps on top of that, obviously. All the goodness, from the model driven apps, the. Model driven authoring. Experience where you model, out your business processes, you want to build the app around so, if you're in a bank you want the. Person, there cyanate, having signing, a customer for a loan to, go very through, very specific process, steps every single time you can build your app around that versus, canvas app which is more freeform, more. Lightweight, WYSIWYG. Experience, so you have those two different experiences, that you can use on the platform, obviously, stuff, like server-side, logic business. Flow solution. And packaging, so, if you're used to working with Dynamics. 365, and the XOM platform, you, know you can package up your apps and distribute, through app source we, are still working on what it takes to include, the canvas, driven power-ups as part of solutioning, but, we are working towards. That and obviously Ellison. Is we and thinking, about reselling, you want to be able to package that and then, our SDKs, we had for. Both platforms before, now, it's all a single one and obviously. You can do stuff, like your own custom, plugins. Whenever. We, in the low code no code experiences. Run out of gas for what you need to do we, have the plug-in so you can create your own custom. Workflows, and clock the band and then, obviously on, the canvas app side that. Is the WYSIWYG. Tooling. And. I think that. Really has two values, from an ISV perspective. One, is we see is v's built, more, lightweight companion. Apps where. Instead of having let's say one customer. Engagement, experience you. Built small experiences. Tailored for a specific audience. So if we're going to take the bank example, you. Might have the business process, of the app for how you make. Sure you get all the data you need for signing, a customer, for a loan that, is very process-oriented, you might have a greeting, app where you, have a greeting. Person standing in the bank taking your name see, what you are in for get, you in the right line and say look we have half an hour wait time why, don't you go and take a coffee in the CAF and we'll text you when you're there that's, a very different experience you, don't want them to, see that same UI and, fill, your way around it so that is really what the lightweight power app experience, or the canvas app experience enables.
To, Create these smaller companion. Apps in. In addition to that and in, addition to that it's not just for you as a nice Vee to develop these it is also, enabling, your customers, to, now take the data you bring to the platform, and build. Apps mashing. That up with data they already have in the common, data service so it's really the, ability for them to get more value out of the value you're already providing, yep. Yeah as a matter of fact earlier, today we had a young lady come up to us and ask us how, she should, think about building her particular, power app and. One of the things was she was actually her initial thought was I'm gonna combined all of the different personas that I have as if it's this thick, client as if they're gonna go in and build one entire, application. That meets all the needs of everybody in there and our message back to her was let's kind of focus on what's the specific activities. You're trying to do and what's the persona and that should be in most cases an app to itself so that way you're only doing the activities you need to do within that particular power app. So. Getting, to actually building, on the platform, we think of it in three buckets and we can come up with many different buckets. And pivots for how we talk about it but, we really think about connecting, bed and extend so. Connecting. Obviously. As you can see we would like for all the data to be in the common data service that means you don't really connect anymore the data is already there but that is not the reality you will always have data living, in other systems so we have more than 200. Plus. Connectors, connecting. To external systems. You can either say I want to move this data into the common data service, as part, of my experience you can say I just want to connect on read so you can define how you want to do that we, have the 200 plus connectors, we. See many Ice V's investing. In their, particular, solution. For a specific connector, to a system we are not providing, connectivity out of the box so, that again can be just a piece of connector, you put an app source for resale or it can be part of your solution and again. We. Also have a low. Code experience. To create custom. Connectors. The. Piece of embedding, and that. Actually has many flavors, so there's, taking. Like the one you probably know already this power bi create. Visualizations, and. Dashboards. And embed, into. Either, dynamics, 365. Into. Power apps into canvas app or even into, your your. Own app your multi-tenant, SAS app right you can also take external, data and, embed. Into dynamics 365, you. Can take. Power. Apps canvas, app and embed into both dynamics, and into power bi so. There's a lot of kind of angles, for embedding, the, one gap. That I would call out here that we don't do yet, super well is taking, power, apps so canvas app content, and enable you to embed that into your. Multi-tenant. SAS app if that a requirement. You have we would love to hear about it and we, see obviously, a lot of demand, for the power bi embedding, we, haven't done it for power apps if that's something you feel a big need for please. Feel, free to send, an email would love to hear about it. Extend. Is by. Far the biggest bucket, in. Many ways in terms of kind. Of different flavors, of extensions, you can do we can extend obviously. The, dynamics, 365. Apps right, you can add further, customizations. To them you, if you don't like our search UI you can build your own search, UI you can build custom, controls, if you need a signature, a little pad embedded, in you can do that as a custom, control, so. You can extend the actual app you can do horizontals. You can do vertical, and you can extend the platform so. Let's say you want. To create a vertical app, for, like what Michael, is gonna do a.
Veterinary. Hospital app, right. There's, entities. In there that are very specific to Michael, solutions, like, entity. Like a pet and breed. And, species. If. You say look I think this is super critical for other ISPs, to build on as well he, can go ahead and say I want to extend the common, data model the, definitions. And give github, for how I define. Pet because, I want other. ISPs. In that same space to leverage, that single, entity. For that this, is how kind. Of the Eco the fly wheel, starts. To be created instead of having five, different IVs. Do their own definition, of pet, how, can you collaborate on, a single, one so that when you install it's much more lightweight and reusable, and the customer, can reuse, that same data, on top and just one other thing is there's also kind. Of the flip, side of extend, which is folks. Within office, teams that such are looking at extending their, platforms, via our platforms, the business application platform, is intended, for them to, also say great we don't want to build this functionality, out of the box we're just going to embed it via the. Dynamics, platform so, it's actually far, reaching across the company as well yes so we actually have is vs who built business, app on top of SharePoint as well sometimes. They pull the data in sometimes it lives in SharePoint, as the backend but, that is we that is the business application, platform. That enables those, and and kind of delivers. Those experiences. And I think the session is tomorrow, or that Ryan is doing for CTS. As a whole since this wasn't technically a CVS specific. Yes. But, yeah at the end of this session we have a list of all the different sessions that go more into detail, so. With that it's. Almost at building, time so, this is the entire hour process that Michael, will go through so, essentially, first, create. Entities, this is also connect to entities, that that's first get, data into the system. Actually. Before I go there I want to highlight a few things that we are not covering, they, are in the platform, but we only have an hour and 15 so, we don't have time for them so, these are all the pieces that we are not going to cover in detail but, they do exist in the. Platform, it is not that. We don't, have it right, so obviously solution, and packaging, there is a session tomorrow with Matt Barber he, goes much more into detail on that versioning. Obviously, your building is V app you want to be able to version, you want to be able to patch that, infrastructure, is there security. Obviously. Relationship. You create your own custom entities, we're not going to walk you through it but that's obviously, a key part of the platform the, custom, visual visual visuals. And custom controls, clock, in the Nestea case and obviously the application, lifecycle management. Part. Of the admin experiences, as well as well as the office, and Asha integrations. That are. We. Do actually, and there was a session, I think yesterday to do that but. Think of the. Business application, platform, as the, extensibility. But. Take into account as we mentioned every one of those can. Be part of this and obviously a half of those things you can either embed in or leverage as part of the platform or just well, you, know I may touch on one as we do it but several. Of those we're not going to cover it and literally each of these couldn't even leave easily be in our session, of each as well so. Here so the flow will go through create entities. And. Connect, to data we're not going to connect I think we might be creating. Entities. We, will then go ahead and. Build. Some business logic we will already have that in the demo but here's that this is really the point of what are the business processes, you want to map out as you build the application going. Through actually building the app we, will show you both experiences. We I mean Michael, I'm not really gonna do anything I, just, planned to just you keep me honest yeah so, we will he will show how to build a, form.
Using. Kind, of the model. Driven but, also built a canvas, app to, commit as a Penina and then. Customize. And extend we, will be, customizing, two ways customizing. Because we're adding custom entities, but, also customizing. In the sense that the, starting, point Michael. Will take is we. Pretend, there has been a system, integrator or an IV who already created. A. Solution. For the. Veterinary, hospital and here gonna be further extending. That so. That's kind of how that comes into play then we'll do some, power bi visualizations, that, we are gonna embed and then, publish, publish. Means two things, it means, publishing. Into AB source for, V cell discovery. If you are nicely but, it also means published to your organization. Like once, you have acquired this app how does the customers, actually publish, we're not going to go through that in detail. Nope. Yes we'll, do that yes there's a theater, session, tomorrow. Covering. All, of apps, or publishing, as well, with. That awesome. Demo, Julie do, you want to tee up what you're going to show sure yes so I'm just curious show of hands how many folks. Know. How, to go out and actually create. A CD. S2o, instance. And, start using it. Okay. Okay. So it's so so so a couple. So. Number. One as Julie, mentioned what, really, the starting point of today is in the one of the messages we definitely want to get across especially since an ISV an SI, perspective, is we. Are going to effectively. Say look we. Have a pre-existing solution. And that pre-existing, solution, is going to be an extension, of CD, s in the CDM and the idea behind it is it's it, is effectively. Something, that enables you to have, visualizations. Connectors. Power, apps all, the components, of what we are going to what we call accelerators. And that's one thing that we're focusing, on within the company our vertical. Accelerators. For the industry while at the same time we're looking for sis and ISPs to help us build those accelerators, and also, to target, specific, areas we. In the horizontal industry. And. Across the stack so, the. First thing I want to do just briefly because I know. Not. Many people said they actually knew how to do this because I'll be honest it is fairly. Complicated in some cases so. There's actually sort of five steps that you would want to do if you want to leverage CDs, as a whole, and not per se just power, ups but the whole thing, first. You, need to have an email account that you're gonna leverage because really what we're gonna focus is on is setting up a trial now we're not going to go through that whole process today but I just want to point out how you can do it so you can go back after the session or tomorrow and actually try it out so, whether you use Outlook, or Gmail or, Yahoo you just need an email account that you can associate with this. The. Next thing is you're gonna need at least an, Enterprise III, trial this is the easiest one to get you're, not gonna be required to put a credit card in and accidentally forget and have to start paying 30 days from now you just create the trial it takes about ten minutes, and. You're good to go. Once. You have your III license. What. I normally do is you can see I actually opened up all these tabs on purpose I just keep opening it at a separate tab to the next one. Each one of these represents the apps within, our space, some. Of these within our space like if I scroll down to the marketing app or actually based on our note our new UCI. Visualization. Model which you'll see as part of the work we're going to do today for myself, if I'm just practicing, around sales as the easiest one to do it's the quickest what. It actually ends up giving you is effectively. And, what. You would have called an old version. Xrm, database, excuse, me an xrm, UCI. Web client, as well as, all the new UCI stuff on top of it so it is a true ceadeus instance, anybody.
Who Goes on Purdue and creates a. Dynamics. 9au customer. Engagement, or greater will, be on CD s anybody before that is is effectively, not today. So. Power apps is pretty simple once you've done those those things, realistically, it's just clicking the sign in button it'll. Log you in and from that point which we'll show you in a minute you can start building your apps directly, against that particular instance and then. Lastly the same for RBI the one thing I would recommend for, folks if I'm just curious how many folks use, power behind most of their solutions today or some of their solutions today. And. One, last question how many people use a IR ml in Azure. For. The solutions, that they built. Okay. So. If. You do set this up I would recommend, after you get the power bi part set up there's, one more step you can upgrade it to a pro. Account, for free for 60 days I recommend, you do that as well because. You're going to want to build apps and it's a little easier to do that. So. The first thing I want to show merely is when, when, you look at CD s and now you think about dynamics, the way I explained it to folks is is it's, really a dynamics, 365. Container, many times when we go to customers, and they say you know am, i building an app is it, going to be inside a quote my container, is it going to be a power app where does it actually live today. When you build an application each. Instance, is going to have an actual my apps space, so, that you can actually see all the apps that you've included inside, of your CRM. Instance or in this case customer, engagement customer, engagement at, the same time. You. Will actually still see just. Like you used to if you were to actually go into, this. Is my instance, if you, actually go in and you. Say great I want to look at my custom, instance which reflectively, is your. Dynamic CRM, customer. Engagement, instance that's, where everything, will be. So. Here. Now. Enables. You to look. Here. And. When you build an application and, you deploy it which we'll do later today within the customer, engagement, environment. There's. Actually a new section, for apps that'll, actually show up and, this. Will be where all of your applications. Will show up for customer, engagement. Now. All of these can effectively and they do all run on CD s they, show up here as apps and so you will notice as we do this what. We have power apps we have power bi apps and we, effectively have customer, engagements, F&O. Apps and. So there's the, term gets used quite a lot. The. First thing we want to show is. That. Again. What we wanted to be able to do is effectively, show you. What. Would it mean to produce, an accelerator. Pack or what would it mean to actually extend, a platform, in a way which.
Would Allow you to share. That IP through, app source it may not actually be what you would call for vertical solution, or even a full horizontal, solution but it could be the starting point and so somebody to ask for the gentleman in the back asked about you know the business models and the licensing, models and such so, this is part of the discussion is depending. On what my IP is, what. Does that look like for me to put on apps source and how do i rationalize. Revenue. For that those are not answers we can give you today but, those are things that we are thinking about within, the platform, so, a accelerator. Pack like that could literally be a connector. To a data store a, visualization. Or a single app right. Or it could be a full-blown, app so, those are kind of for you to define yep exactly. So. Inside, of here if. We actually look, at this particular. App. What. We actually want to do. Is. Open. Up the visual designer for this application. And. You'll see all of the, entities. And. Extensions. That we've placed inside, of this particular, solution, and the, only reason I'm not showing you how I built this is because the intent was to show you how to extend, it assuming. That it's already here but, this particular solution. Is, sort, of a standard model of how we look, at how. Somebody would extend the platform this. Is actually a CD s app. Built. Through the power app extensions, in solution, Explorer. So. This is a model driven app for those of you who come from the canvas, app of power outside yep. Right. So. Now on. Top of that as you, guys already knows because it was rendering is what, I've actually done is, pre, created apps for, power bi. One. Of them is focused. On you'll, see here focused. On this, particular. Solution. And you, can actually see here if I, wanted, to I mean I won't take the time at the moment but you see I could, publish the app right now once. I publish this power bi app I can then package it and share it across my organization or with an app source and make, that available to folks or. You know otherwise other partners, to actually build on top of the, nice thing is that any. Of these analytics. That are here remember they're actually extending, the data model, itself that, is being used by that customers, tenant so the idea here would be as if you, were going to leverage this, actual. Solution, you, would install this on your dev instances, of c.d.s and then you would extend it you would package that up and then, you would deploy that foot through app source. The. Other thing is and for folks who I'm just curious how many people use c.d.s one oh. Okay. So. For the folks who did use it before they. Would have noticed. That. When. You actually wanted to use CES that really wasn't connected. To serum as Julie said before you actually had to copy the data in to, CD s itself, with. CD s - oh you. Can actually see here that. When I log in I can. Actually see, all of the different environments. That I have in power apps now an environment, is equal.
To An instance, of CRM. For instance so, you'll see I actually have my, default instance. And then, I have an MS CD. S build and M s CD s build, instances. Of CRM. Automatically. I can actually see, all of the entities that, are in c.d.s and supporting, that particular instance of customer. Engagement because, it's the same back-end there's no there's, no special connector, there's no data movement it is, there and visualized, for everyone to leverage now there's one thing to note, here if I create an entity right, now. In. This, it will show up in my CRM, solution, but today it will show up in your default solution, we. Are going to be changing, it so that you will be able to specify the solution, that you want that particular entity to go into it's, obviously you don't necessarily want to come in and create 30 entities, and realize, you shoved everything inside, of your default solution so when, you extend them it'll, get smarter, as we go along to, enable you to rationalize. What those changes are and where they're targeting, and the reasoning, there is obviously, the power apps environment. Or the common data service one-oh didn't. Have the awareness of solutions. Meaning, whenever, you create an entity, in CRM, or in the model driven it, you will see it in here but you can't filter by a solution, in the same way that's why you have to add it later, on automatically. My. Sincerest. Apologies could, you ask, that again I'm sorry it. Does it does it work the other way around if I create the entity in. Customer. Engagement, does it within, my solution does it then show up yes yeah, and we're actually going to show that because that's one of the big differences, as. I mentioned earlier if you are on 900, or greater than, what you just asked is 100% accurate if you're, on a previous eight - it's not because, they are separate still. So. Now what, we actually want to do is take the solution that we have and we actually want to extend this right, so. The first thing we're going to do is. We. Go over to our now I do want to make one other point unfortunately, if you install the marketing, app which is one reason why I said use this sales, or any of the other ones if you install the marketing, app today unfortunately. The, my apps section which show it should show up under settings doesn't. Actually show up and unfortunately, mine's the marketing one because I wanted to show you something an integration, with the marketing app so I, had, to actually go directly to it so. First. Thing I want to do is I'm actually, going to be inside, of effectively. Customer, engagement, and I'm. Going to create a new, application. Now. Here's. Where you can actually select whether you want to create a. Classic. Web application. Or a new. UCI application. We're, only focusing, on UCI, if you if you build the standard web one you can consider that just like being in standard sales service and marketing for CRM, so. That's a unified. Client. Allow. You, to, build once and it shows up on the, desktop and mobile and, different devices etc we. Are moving towards, making that more default, experience, but still, catching. Up on on feature parity for that but moving forward that's also the richer experience, you will see, I'm. Just curious have has, anybody in the room built apps on, UCI, this way yet. So. Effectively. Everything. You could do in your solution, Explorer, in CRM, you, can do here there's actually a hybrid methodology.
To This so. First of all you'll, notice here that we have the site map my, recommendation. For everybody that tries this wait. Until you are done building your app to actually set your site map that, actually defines how it looks inside, of, CRM, and how it looks inside of your app but. Unfortunately, since you are actually building it based off of what's in your app if it's not in your app yet your, site Maps not gonna be very very. Big so. The first thing I actually want to do is. Actually. Want to create a. New. Dashboard the reason I'm gonna do a classic dashboard. Versus an interactive, is one, of the things I want to show you and that we talked a little bit about before is. Today. We allow we, allow specific types, of power bi embedding, inside of the product today for customer engagement, we're, extending that more so, that you can actually use, user. Base dashboards. Filterable lists, the things that you actually want to do inside there to target say on the account form but. The other thing we wanted to support was the ability for us to, cross, in bed so what I actually did was I actually created, a portal I don't need the portal but I created a portal because what I want to do is demonstrate, the fact that I can embed my portal, into, this application, and build. Marketing, lists, just by clicking through actually, power. Bi. So. You are embedding in. Embedding, I'm, embedding, and embedding yeah it's actually three layers of embedding. So. For the folks again who are used to customer, engagement. What. Happens now is that the UCI client actually will kick you into the solution Explorer, floor sections. And. I'm gonna go through this. And. Wipe these out since I don't need them. I'm. Gonna make. Sure we can see, it. And. We'll call this, really. Vaccine, marketing. Now. You'll. Notice two, things here. Just. Like when you're in the, standard, CRM, client. If you were the Diamonds 365, client if you go in there and you say I want to create a new dashboard in that, UI you can actually select a power, bi dashboard or, you can select a standard, dashboard. The reason, that is is because today. Unless. You do what I'm doing here we only support. User. Based, power bi embedding that means when you create a dashboard as, long as you're logged in you. Can show something but, we don't support that as a system level yet that's one of the things that we're actually adding. Into the platform now and the reason is there's a whole bunch of stuff around security, and modeling that has to do that but. That's why I actually built an app outside, of it so I could actually just embed the app into, this. The. Same way I would do this with, any. Other power app. And. I'm going to turn this off and say, don't. Need it. And now what I actually want to do is I want to I know it seems a little weird but I actually. Now, have to select, this, particular marketing. One. And. Then, I'm actually going to go to my entities because I actually want, to add. Marketing. Lists because obviously the point is for me to demonstrate that we can actually create a marketing, list via. This now. One thing I recommend to folks is pick, your default form if it, says all this, is a little backwards all, does, actually mean all but, it doesn't select them so, it almost looks like it's not going to pick any of them what it actually means is I'm picking all of them for you since you didn't pick something I don't, want that many so, therefore I'm just picking the one that I specifically, want. And these. Are extension. Entities. That. Did not exist, as. Part. Of the. Application that, I installed, from. The si for instance they, actually do extend, the, entities, that came from the si but, they don't affect the s i--'s installation. At all so, they can actually still go and do upgrades on theirs and it won't affect in fact mine so. Essentially, when Michael is gonna package his app up for resale, he, will declare, his, dependency. On whatever, entities. That came from that other app so, that the customer can just store them in turn without Michael, have to be installing all of that but, it's a check the dependency, chain so, it becomes more lightweight.
My. Apologies, my. Internet. Keeps dying, for some reason. So. What. You actually will see. Here. Is that. While. You're working on an app you can just stop and I, know like for myself I was actually building a fairly large one the other day and I. Walked away and forgot and all, my tokens, and everything got wiped down I was like oh man and then I remembered, that it's actually just stored here so if you're working on it you can literally just make, sure you save it and close, it but everything you're doing is actually cached within, that. Now. The one thing I will tell you is anytime. You do anything. Within. This. UI if. You'll notice in the the far I guess, it would be your. Left you'll. Actually see where it says you know designer and then. Bracket, site. Well. For. This anytime. You do anything within the site map, you. Actually have to save it here and publish that first, that, actually has to be published prior to your actual application, so. In this particular instance. We. Have a specific. Area. Within our site map and, then. We have a sub group of. Items. That we want within, our solution. So. You'll see here the dashboard, is here if, I want to add another one I can, specifically, specify. What, I want to add to, this particular, section I. Can. Come over and. Drag. Another sub area, and. Say. I need another entity. And. I can add in the vaccine-type, now. I can add entities. From. Any. Solution. That's in serum, as you normally do when, you do that it. Will create a dependency, for you and when you try, to build your application we try to validate your application, it will in fact tell you so I'm. Gonna save this. And. Publish it. And what, this is actually doing is is going into the site map for customer, engagement, itself, because, it has two layers now that it has to worry about us and we're about the UCI layer as well, as the standard customer engagement. Side. Now. I can go back to my app and, I. Click validate, and it says I'm good. So. Now I publish it at that point you're done the. Application, is actually built. What. I want to show. Is. Now, if I come back over here and i refresh this obviously, there's my application. Now. If I open this application up. You, can actually see now there is there is unfortunately we do have little hiccups, here and there. You'll. See this gap, where my mouse is. For. Whatever reason, the marketing, list icon doesn't, want to show no matter what I tell it to do so. That's. What that is so. What this actually is is, a. Visualization. That, I built in, power, bi desktop I. Then. Went into power, bi. And. I. Created, an app space, for it because. Again I want to publish this as part of my overall app, because, again power bi is directly. Connected. With customer. Engagement, now. My. Apologies, I don't need that one. So. Now I can actually for. Instance. Select. This obviously, like most power bi there filterable go ahead you have a question I've heard people talk about this as c.d.s, a, yeah. Yeah. So as. A. Whole we've kind of gone through a transition. Of what we keep calling this so as a whole the platform, is called CDSA, a for. Apps and a for analytics, originally. We called it C DST, transactional. CDSA, analytics so what, you said is accurate it's just kind of gone through this evolution so. If somebody says to you CDSA, they may not actually mean analytics, so if you were talking to me specifically I actually, say the word fully I don't just say C the SA but, this is a power, bi analytics, app, not. A Content, pack that. Is correct this is a power bi app which. I then embedded. In another app and now, I'm embedding, in here. So. But this also has to both with how the data flows in, from the transactional, layer into, the analytical, layer it doesn't, mean you always do that so for example you could easily create, an app at power bi.
Dashboard. Directly. On top on the, transactional, layer as well so it's not like that has gone away think. Of the CD s4. Analytics, as, additional. Analytical. Capabilities. On top of what you already, today so all of this lot of this you can already do today without that additional. Processing. Capability exactly, and one thing just before I click the button here to think about is when it went like when you work with Julie and myself and a sweetie and some of the other folks we. Don't look at it from even if you came to us and said I'm a 100 percent analytic app I don't want to talk about the transaction layer go away we, would say we really respect that now, let's talk about how you leverage the platform as a whole because, as a whole, pretty much when you calculate answers, in analytics, somebody, wants to do something with that and that answer it's nice to be pretty it's nice to have it visual and I'm not a great visual person so I apologize for this but you know that's nice to look at but if you want to make it actionable like this then, you're gonna put more time into it to actually make it actionable. So. Now what. I ended up doing is saying great I want to create a marketing, list which. In this particular instance is targeted. At account, because. I leveraged account for this, so. Now. I. Gotta click on marketing list the one that's invisible so. Some of the custom entities Michael. Added was for vaccinations, so, you can now go and see based on the records for one whence the pet was last vaccinated. What, are now the ones that are due that we do a marketing, campaign against. And using the visualizations. For. That absolutely. And and, one thing I just want to show and I'm purposely kind of going back and forth little because I want you guys to understand that the platform. Is really connected, so if I, actually intentionally. Come over to you see the new apps now they're all listed right there if I, purposely, now go back over, to my standard, CRM, instance which is still supported, by the same CD s everything is still the same stuff and I apologize my Wi-Fi, is clearly not very good. Hello. There we go. You. Will actually see from in here all, of the data that you're creating. From. Within the applications, because, those extensions.
Actually, Exist. Inside. Of CVS. So. You can see the marketing list there. Open. It up. And. See the fact that I have a lot of animals more than some that screen and it cost me a lot of money for vaccines. Every. Year. Now. One. Other and that one, other important, thing is now we say okay great one. Of the reasons why we did this application. And this extension was not just to say hey look we could create marketing, lists but, the idea behind it is but what now if I had, a persona, of somebody, who, actually received. The calls or they're, sitting at the desk the doctor the vet has now done the vaccinations, and they're like great now I need to close this thing out I actually need to close it out. So. Again when you come over to power apps now we're going to go into power apps now, we can actually quickly, build a. Straightforward. Canvas. Based application. That, will leverage either, one of those solutions that we have the new ones and, in this particular case a lot of people ask us do you only do phone apps and stuff and the answer is no. It's. Really just a matter of if you look here those, are just our default templates, so. You'll see here I'm not picking dynamics 365, because I'm not connected. To Dynamics 365, with a quote connector I'm actually. Integrated. With it in CVS which is much different. Right. So, as you think about the end to end you could have had a business, process that says my, patient, come in I check them in I weigh them I do all that good stuff I leave the screen open, I do what I need and fill it out that, is totally, a valid scenario then, Michael would have extended, the existing app, here, we are showcasing how, you can create a companion, app where, you might have two different people with two different needs, to just go and check the few things that they need to do in each of their apps yep, and. In this particular instance, what. We're actually doing now is saying great you started, out with a common, data model, platform. Then, you added your si package on top of it and now, whether it's literally somebody who works at the vet you'd be probably, you wouldn't actually with other customers you talk to you but I was actually quite surprised how many places I go and they're like oh yeah we do stuff all the time you, know we buy something from you guys we buy we're now siren dynasty and we actually do the work although I will say a lot of them actually do it within Excel I think it's just kind of the, place to go. So. What I want to do I don't want to spend a whole lot time I want to be able to answer some questions is, within. This app it, automatically. Provides, you the credit keep the crud capabilities, on the box the nice thing is is that literally. Within. A, few seconds, I can. Actually come in here change, the application, to whatever fields, etc that I want right, and, I, won't go through all of it because we run it at a time here but once. We're done and you've, added the. What. We will do is change right here. We. Can actually run this application. We. Can then sort. By. The. Different customers that we have yes. That is actually my dogs my. Mother's dog's name princess, or maybe it's a cat I don't remember doesn't. Even know I love my mother but she has like too many for me to remember. But, what you can actually do now and I literally wrote no code is I can easily come in and change. The date if I want edit this or close. Out another. Option. And that. That quickly was, now referenced, in CVS so if you were embedding this in power bi if you were embedding it in CRM. Everywhere. That you were, using this data is updated that quickly. And. So. As Julie. Mentioned more. And more we're having people say well I want to be able to embed power bi inside, of my power apps or vice versa so that's actually a big one that people do nowadays so one of the big changes that they're working on is how, do and, this is the power bi team specifically, how do we enable it so I can build a power app that.
Is Focused, on if I select, a particular record like a contact, or account that a lot will filter just like if you're in power bi right, so that's one of the things they're actually working on now so the goal is in any, of our, application. Spaces, you can have filterable, reports. That. Will traverse whatever you have on the screen. All. Right. Any. Questions, thoughts. So. Your your earlier. You. Earlier made the point that sometimes, people say I just want analytics app and and I don't want all the other things. Going on with these these, these, power apps and all these other entities. And forms, well, I just want an analytics, app. When. I distribute, this to my customers. How. Do they how do they discover, that app because, to them I'm merchandising. This as a power bi integration, that we have yep. How. Do I do that to them in a way that doesn't feel too much of a burden for them to discover. And install yeah, so, so. App source is the mechanism that, we will, leverage for all of our our. Power bi applications as, well. And we are enhancing so, shree's, team is actually looking, at from the ISV side how to make what we do better for you guys I don't mean power, bi better I mean how do we use, our onboarding, tools to, be better for you so part, of it is we, want to make sure that when you create an app an app right, whether it's an analytic. App or a transactional, app or both then. Everybody understands a how, to build them quickly. How. To market. Them effectively. And those are some changes that we're putting into the platform because that that's what makes it more discoverable, obviously, if you put it out there like Android, has seven point six billion apps or something you can't find unless you know exactly what it is so. We're highly focused on how do we enable you to put the right keywords, and vertical notions, and things in there as well. As you, can actually build and I'm not sure folks in this room have done this you could actually build a test drive on Dynamics and so, a test drive actually allows you to say well I have an app I want. To create an instance and I. Can actually record myself talking I can make it interactive so they can click and I can tell them what to do and so they can actually try, not, just a trial it's, an actual walkthrough, from, yourself so you can actually do that whether it's going to be power power bi that's important or, CRM. And. I, guess for me you know when I say to my customers. There's a power bi integration. They would go to app source they would see the integration listed, in the marketplace do, they need to care No so, here's here's the cool thing for you my apologies is in, your app for, instance and, I'll talk about two different ways let's, say that your SAS application. And you say well there's really two scenarios that we talked about user owns the data and Apple, owns the data and user, owns the data that is where it's in their tenant, app bones the data is more this SAS model so, when you put your application in. App, source you, either already know before you did it whether you're the SAS version or you're the tenant version if you're, the tenant version you're, going to include, whatever connectors. You need because we have ISPs who do build analytic apps and they're like oh well I connect to an S I asked to get some data can. I package that up with my app yes you can package that all up so when they do it they go click deploy, close, their eyes I don't want to see anything and then boom all of a sudden the stuffs just start showing up in either, their power app or their customer engagement, or fnot depending on where they're doing it if it, is a SAS implemented it, is still exactly, the same except. There, could be some. I'll. Say hand-holding, only from the context, of we. Are working on making this way better but the idea is you have to actually provide. Them secure credentials, and stuff to connect right so it's over there but you can provide all of that and what we call laughs and also, a last mile, installed. Thing which, actually would allow them to go into a UI that, you you build and you make it as part of your install and it would actually come up and let them type stuff in their license key you, could give it back to them that way and the install could continue, so it, is actually possible to be hands-off the one area that we are also, still work on is dependency.
So If you wanted to build an app that was dependent on Azure functions, right. If it's if it's part of power bi but, maybe your tenant doesn't even have power bi maybe they're like man I I know I need this and they, go to install your app and your app says well I'm dependent, upon X, and X isn't there so therefore doesn't work some, of the stuff we're looking at is how do we make it so that if you're on apps source you, can't even attempt to install that or it'll come up and say wait, you need to make sure you have these things so, we. Are spending. A lot of efforts just on that part, and. Also just to be clear from our perspective, we focus, on the whole plan form because. We don't want it to be hard to, connect these starts right before it literally it was four, different data stores completely. Isolation. If you did want to integrate you had to enable data movement here, we're just saying we, want it to be super seamless, and we do see part in healthcare we do CICS, built the like, the transactional. Side apps, really. Focused on that business process and, the work going into that and I, analytical. Eyes he's building, on top of that and to. That extent like there is they. Have analytical, practices, and doesn't build transactional. Apps but we see them very often collaborate, and say how can you build analytical, packages, on top of transactional, SAP so what we see at least from a customer, perspective they, care about both it doesn't mean that's, built by a single highest V yeah. And, as we kind of talked a little bit before is you know we have these scenarios sometimes, where somebody was a complete, SAS analytic. Application, and then, we said yes but if you were to look at extending, the data model for both their analytic, and transactional, space and at first a lot of more like I don't understand how they leverage what I do in the transactional, space we had to sit down to kind of say here's, how it would work but don't forget when you put it there it actually flows back and then we have other folks who say well I'm used to going out and getting data from CRM, so can I still do that the answer is 100% yes our CVS SDK, is is, I'll, say effectively, the same as if you were using the xrm SDK but the benefit, is is, that since that's one stack and all that data flows into the analytic stack. Automatically. You can say great I want to use AI and m/l out-of-the-box on there if you want to write SPARC jobs and those, are things that you can then install on their, tenant, you're not going to pay for it so that's what some of our larger. Analytic. Players or do it you say hey for. These sets