Episode 325: In the Dynamics Corner Chair: Unlocking Additional Value with Power Automate

WEBVTT

00:00:00.300 --> 00:00:06.850
Welcome everyone to another episode of Dynamics Corner, the podcast where we dive deep into all things Microsoft Dynamics.

00:00:06.850 --> 00:00:15.169
Whether you're a seasoned expert or just starting your journey into the world of Dynamics 365, including Power Platform, I'm your co-host.

00:00:15.369 --> 00:00:17.303
Chris, and this is Brad.

00:00:17.303 --> 00:00:21.332
This episode is recorded on June 20th 2024.

00:00:21.332 --> 00:00:31.949
Chris, chris, chris, another mind-blowing episode, and we haven't had a chance to talk about this yet.

00:00:31.949 --> 00:00:34.764
But did you know, my latest obsession is the Rubik's Cube.

00:00:36.887 --> 00:00:40.741
Yeah, could you figure it out by the time we finish the episode?

00:00:40.741 --> 00:00:42.526
I did, I did.

00:00:42.545 --> 00:00:57.220
There's a sequence, right, right there is a sequence, there's a trick to it or a secret, it's some algorithms or whatever you may call it, and you can have a good workflow to go through to solve one of these yeah you can follow that workflow time and time again and let's solve.

00:00:57.801 --> 00:01:04.409
speaking of workflows, with us today we had the opportunity to speak with the man himself, the product manager from microsoft, working with the business central.

00:01:04.409 --> 00:01:09.612
Speak with the man himself, the product manager for Microsoft, working with the Business Central, connector for the Power Platform.

00:01:09.612 --> 00:01:12.301
With us today we have the opportunity to speak with Vlasde Kutela.

00:01:12.301 --> 00:01:32.218
Good morning, how are you doing?

00:01:32.218 --> 00:01:35.548
Good afternoon, I should say Good afternoon.

00:01:35.548 --> 00:01:37.251
How are you doing?

00:01:38.040 --> 00:01:38.722
I'm fine.

00:01:38.722 --> 00:01:40.750
How are you guys?

00:01:41.721 --> 00:01:45.084
Doing well, very well, I see you're in the famous LEGO room.

00:01:47.171 --> 00:01:47.552
Correct.

00:01:47.552 --> 00:01:59.546
I did a little bit of research before joining this and saw that a couple of weeks ago you actually had my manager, Janik, who was also in this room.

00:01:59.546 --> 00:02:04.512
So I thought I will use the same famous location.

00:02:04.512 --> 00:02:14.030
But I have something to show to you and the audience, because we have a couple of new sets that are ready to be assembled.

00:02:14.030 --> 00:02:19.688
So this is actually a retro radio which has a sound unit in it, apparently.

00:02:20.460 --> 00:02:28.951
We also have this, yes, correct, nasa Artemis launch system with the rocket and everything.

00:02:28.951 --> 00:02:34.350
And then this is very exciting it's Notre Dame.

00:02:34.350 --> 00:02:36.768
Wow, oh, the Notre Dame Lego set.

00:02:36.800 --> 00:02:39.849
So you have three new Lego sets to put into the famous Lego.

00:02:42.344 --> 00:02:44.149
We're getting those every now and then.

00:02:44.149 --> 00:02:54.127
These are waiting for maybe a little bit more autumn weather later.

00:02:54.127 --> 00:02:54.866
I don't know.

00:02:54.866 --> 00:02:57.286
Right now the weather in Denmark is amazing.

00:02:57.286 --> 00:03:02.382
People tend to spend time outside of the office whenever they can.

00:03:03.063 --> 00:03:04.909
Oh yes, I know all about those seasons.

00:03:06.500 --> 00:03:09.406
We also have football in Europe, europe.

00:03:09.406 --> 00:03:25.953
I don't know if you guys are aware, but the european championship for in football, which is soccer in the us right there yeah, that's a famous sport is currently on the way and we have have actually Denmark playing England today.

00:03:25.953 --> 00:03:40.090
So some of my colleagues are already getting ready to be excited, so you have to get some barbecue ready.

00:03:40.169 --> 00:03:42.865
Oh yes, you have to have some beer in the fridge stuff like that.

00:03:42.740 --> 00:03:45.135
You have some beer in the fridge stuff like that, but it's.

00:03:45.135 --> 00:03:53.169
It is today 6pm, so it starts in one hour right now in here.

00:03:53.169 --> 00:04:03.725
I will probably have a look at part of that game later on as well, but I'm not Danish originally, so I'm sometimes torn.

00:04:03.725 --> 00:04:05.222
We still can participate, hopefully we can.

00:04:05.241 --> 00:04:06.524
I'm not Danish originally so I'm sometimes torn.

00:04:06.524 --> 00:04:07.566
We still can participate.

00:04:07.566 --> 00:04:12.413
Hopefully we have enough time so you can get to watch the game with your colleagues.

00:04:12.734 --> 00:04:16.410
Oh, absolutely there's no problem with that, absolutely no problem.

00:04:18.040 --> 00:04:29.045
And also, we need to put the LEGO room on the map as a tourist attraction to anybody who's visiting Lego room on the map is a tourist attraction to anybody who's visiting.

00:04:29.065 --> 00:04:38.312
It is a tourist attraction and usually people are stopping by and we have members from our team showing various kind of offices here.

00:04:38.312 --> 00:04:40.673
We have a flight simulator room.

00:04:40.673 --> 00:04:45.795
We have an Xbox room this one, of course and a few other kind of hidden gems.

00:04:46.495 --> 00:04:47.776
Flight simulator room.

00:04:47.776 --> 00:04:49.677
I would appreciate that.

00:04:52.240 --> 00:05:07.278
That was a couple of years ago when we had several of our colleagues somehow magically convince someone in the site leadership here that some leftover budget could be spent on buying the actual flight simulator equipment.

00:05:07.278 --> 00:05:10.529
So we have the aux sticks and all that stuff.

00:05:10.529 --> 00:05:12.983
Is it the actual?

00:05:13.285 --> 00:05:15.451
flight sim game, or which game is in there?

00:05:15.451 --> 00:05:16.238
Yeah, yeah, yeah.

00:05:16.379 --> 00:05:24.629
I mean, it was actually before we had access to flight simulator Microsoft Flight Simulator so it is running something else.

00:05:24.629 --> 00:05:30.009
I don't know exactly, but we can research that for the next time.

00:05:30.802 --> 00:05:33.088
Oh, excellent, excellent, no, I want to know.

00:05:33.088 --> 00:05:35.103
See, now we can turn into all the fun that's there.

00:05:35.103 --> 00:05:46.810
It's good to have those outlets within the office, and it does increase creativity, because you can take your mind off something sometime and it helps your brain think a little bit differently.

00:05:46.810 --> 00:05:50.310
But we definitely appreciate you taking the time to speak with us today.

00:05:50.310 --> 00:05:58.173
I've been looking forward to having a conversation with you, as I do with each of the members of the community that take the time to speak with us.

00:05:58.173 --> 00:06:04.411
Before we jump into it, though, do you think you could take a moment to tell everyone who's listening a little bit about yourself?

00:06:05.634 --> 00:06:06.154
Absolutely.

00:06:06.154 --> 00:06:08.238
My name is Boazic Oteuco.

00:06:08.238 --> 00:06:25.694
I work as a PM, which stands for Product Manager or Program Manager, at Microsoft, based out of Microsoft Denmark, which is actually formally not Microsoft Denmark but Microsoft Development Center Copenhagen.

00:06:25.694 --> 00:06:43.110
These are two different business entities located in the same building, and we are a development center for Dynamics products, and Dynamics Business Central, specifically, is headquartered here in this office.

00:06:43.110 --> 00:07:01.869
It's on the outskirts of Copenhagen in Denmark, and, yeah, we have most of the engineering team based here and then, of course, a few other remote locations here and there across Europe and the US.

00:07:01.928 --> 00:07:09.071
As well, so you work as a product manager with Microsoft and the Dynamics product.

00:07:09.071 --> 00:07:12.670
Which product in particular do you work with?

00:07:14.221 --> 00:07:19.228
Yeah, I'm responsible for integration between Business Central and Power Platform.

00:07:19.319 --> 00:07:21.267
That's my main responsibility.

00:07:23.362 --> 00:07:45.526
But when I got hired into this office I was actually responsible for the mobile app first, then a little bit of different kind of elements of UI, web client UI and kind of different aspects of the user interface of our product, and that stays with me until now and going forward as well.

00:07:45.565 --> 00:07:46.951
I will be looking at that as well.

00:07:46.951 --> 00:08:02.923
So kind of user-facing elements, but also integration with Power Platform and for that it is mostly right now Power Automate, power Apps, and recently we started doing a little bit more with Copilot Studio.

00:08:02.923 --> 00:08:17.487
Of course, as you know, we are looking at Copilot scenarios and Copilot being built inside Business Central, but also different scenarios that we can offer to the community using Copilot Studio.

00:08:17.487 --> 00:08:29.466
And as a program manager or product manager officially right now this discipline is called product management, previously program management.

00:08:29.466 --> 00:08:34.808
So as a product manager, I'm looking at what's going on around us.

00:08:34.808 --> 00:08:53.432
I'm looking at the markets, talking to partners, talking to the community, talking to customers, from time to time presenting the content, presenting news and, of course, working with engineers also to actually deliver the components or the elements of the product.

00:08:55.081 --> 00:08:55.582
That's great.

00:08:55.582 --> 00:08:57.188
That is Power Automate.

00:08:57.188 --> 00:09:18.662
I know when they introduced Power Automate or even the early onset, the integration with Business Central to Power Automate, it totally opened up the use of the application from where instances where someone may have to develop a solution, now they could use Power Automate to complete that solution and work with the data in a bi-directional format.

00:09:18.662 --> 00:09:41.179
When working with Power Automate and designing what you would need for the integration between Business Central and Power Automate, what are some of the areas that you look at to determine which entities that you may set up or which information that you will allow to have access to from the outside in Power Automate?

00:09:43.850 --> 00:09:44.192
outside.

00:09:44.192 --> 00:10:03.510
In Power Automate, yeah, we try to offer the technical capability or the capability to integrate with the product, and that is through both having the connector, that component that reaches to the data, but also integration in the UI.

00:10:03.510 --> 00:10:15.412
So the fact that you can have power automate flow show up in the business central UI on the side and that works independently of a specific entity and specific data.

00:10:15.412 --> 00:10:46.820
And, of course, the business central architecture is is defined in such a way that we have our, our platform, our, our kind of server layer, and then, on top of that, apis, and those APIs are responsible for communicating from the outside, so communicating with Business Central, giving access to data and allowing for the data to be written back to Business Central, and those APIs are provided by Microsoft.

00:10:46.820 --> 00:10:53.788
So we have a set of APIs out of the box, like the V2 APIs that we currently own.

00:10:53.788 --> 00:11:16.469
We have a couple of additional sets of APIs for various kinds of use cases, and then partners also are able to provide additional APIs APIs for our data sets or our data that is not included in the standard APIs, but also for data that is created by partners.

00:11:16.469 --> 00:11:36.631
So if you build an extension for Business Central with your own tables, with your own data, different, completely different entities, which actually happens quite often, because Business Central is this kind of programming platform for business applications, based, of course, on Business Central.

00:11:36.631 --> 00:12:03.211
But sometimes we have partners who build applications that have much more objects and tables and components included, provided by the partner, than what we originally provided with Business Central, and for that, of course, in the same way, those partners can open up with their own APIs and all of those APIs are accessible through Power Platform.

00:12:03.279 --> 00:12:06.549
So Power Automate, power Apps and so forth.

00:12:06.549 --> 00:12:07.841
We have different kind of.

00:12:07.841 --> 00:12:10.969
You know we can go a little bit deeper if you're guys interested.

00:12:10.969 --> 00:12:11.671
Oh, I'd like to.

00:12:11.671 --> 00:12:12.552
I'm interested in it.

00:12:12.552 --> 00:12:14.644
We have different technologies for that.

00:12:15.167 --> 00:12:16.490
No, I'm interested, I understand it all.

00:12:16.490 --> 00:12:21.585
I listen to you speak and it brings so much to my mind as far as questions and functionality and technology, and one of them you hit to my mind.

00:12:21.585 --> 00:12:24.749
As far as questions and functionality and technology, and one of them you hit.

00:12:24.749 --> 00:12:57.846
So you had mentioned, if there's standard APIs which may be the foundation of the connector right, or the connector is something that's within Power Automate that connects to Business Central and consumes those APIs, and if you create an extension, whether it's an ISV extension, internal extension for those that may do internal development, or a partner extension is there anything that needs to be done from the Par Automate point of view for those APIs to be accessible, or are they just already accessible?

00:12:57.846 --> 00:12:59.610
Is there a certain structure that they need to follow?

00:13:02.041 --> 00:13:02.761
That's a good question.

00:13:02.761 --> 00:13:27.879
Any API, any extension that creates an API in a standard way and, of course, we have some documentation explaining best practices, how to create custom APIs for Business Central but any API that is created in a proper way will be available to Power Automate through this connector out of the box, no additional steps required.

00:13:27.879 --> 00:13:56.893
So the connector is actually a component in Power Platform, and Power Platform right now has something like 1,400 different connectors for various data sources external and I mean first-party Microsoft-owned product, but also various external systems and Business Central is one of them, and this is a component that allows systems to work with each other.

00:13:56.893 --> 00:13:59.327
It's like a proxy kind of a thing, right.

00:13:59.327 --> 00:14:02.210
It handles authentication and so on.

00:14:02.210 --> 00:14:33.208
It handles also access to different APIs, so it is able to read various API roads in a specific instance of Business Central and allows you, for instance, in Power Automate it gives you like a UI where you can kind of go through the API hierarchy and select the one that you want to work with and connect with and create an action in Power Automate to read data from a specific API.

00:14:34.200 --> 00:14:39.249
I mean, you would think you're reading from a table, but you actually are going through APIs, right.

00:14:39.249 --> 00:14:47.269
So you actually are calling an API, but you don't need to understand the technicalities behind those APIs.

00:14:47.269 --> 00:14:53.303
It's just basically a structure of data In Power BI.

00:14:53.303 --> 00:14:54.908
It is even nice.

00:14:54.908 --> 00:15:06.870
The UI is even nicer because they have a very nice preview of the whole hierarchy of APIs and you can just cherry pick the ones that you are interested in and build your query.

00:15:06.870 --> 00:15:14.772
Power Automate has like a slightly different UI where you have a couple of levels of those.

00:15:14.772 --> 00:15:28.431
You know, selectors with different types of APIs, and then you get to a specific one and then Power Apps, on the other hand, has like a more like a flat list of different APIs that you select.

00:15:28.431 --> 00:15:39.389
But whatever you choose, you always have access to all those APIs that are provided by Microsoft and partners or from your own extension as well, of course.

00:15:40.533 --> 00:15:41.562
That's nice, it's a quick.

00:15:41.562 --> 00:15:44.320
You know everyone likes to use the word or the term.

00:15:44.320 --> 00:15:46.000
Now you know, low code, no code.

00:15:46.000 --> 00:16:03.653
So I guess using the connector you know if we talk about that gives someone easier access to the Business Central data and they can handle all of the without understanding the technical architecture of an API and the connectable assist with authentication for the user as well as selecting the correct company.

00:16:03.653 --> 00:16:05.114
That's always been one of those challenges.

00:16:05.114 --> 00:16:07.836
You know, with Business Central you have a multi-company solution.

00:16:07.836 --> 00:16:08.976
How do I know which company I'm in?

00:16:08.976 --> 00:16:10.278
How do I know which environment I'm in?

00:16:10.278 --> 00:16:16.446
Because you may have a production or a sandbox and all of that is something that you can configure with in the Connect here.

00:16:17.668 --> 00:16:34.828
Precisely, and environment and the company is part of that hierarchy, because environment would be on top right and then in each environment you have multiple companies, or you might have multiple companies and those companies could have slightly different APIs inside right.

00:16:34.828 --> 00:16:50.947
So you're going through that hierarchy and, as I said, like Power BI, power BI Desktop, this kind of report designer has like a very nice kind of experience where you have a tree view of everything that is available for you.

00:16:52.181 --> 00:16:53.586
Maybe you can get that in Power BI.

00:16:53.586 --> 00:17:01.201
So is the connector that you use for Power BI the same connector that you use for Power Automate and Power Apps, or is it something different?

00:17:02.083 --> 00:17:06.453
Yeah, so specifically, power BI is a different connector, it's a different code, something different.

00:17:06.453 --> 00:17:09.079
Yeah, so specifically Power BI, it is a different connector, it's a different code.

00:17:09.079 --> 00:17:18.587
It's using the same concept and it's also calling our PIs, but Power BI as a product is slightly different than the rest of Power Platform for various historical reasons.

00:17:18.587 --> 00:17:29.319
So the technology the connector is written in is slightly different than we had to and we still have multiple versions of that connector.

00:17:29.319 --> 00:17:56.305
We actually have a connector for on-prem version of Business Central that we keep using or offering to our customers, but of course, the majority of our improvements, efforts and different new features are introduced to the cloud version of Business Central Connector.

00:17:56.325 --> 00:18:02.015
So, as it sits today, the Power Platform Connector for Business Central can work both online and on-premise.

00:18:02.015 --> 00:18:04.125
Is there a difference between the two?

00:18:04.125 --> 00:18:08.808
Is it limited functionality between the two based upon the architecture, or are they the same?

00:18:10.703 --> 00:18:29.068
The functionality is limited for Business Central connector on-prem and specifically Business Central connector for Business Central on-prem is not able to react on triggers that happen inside Business Central because you have to expose data.

00:18:29.068 --> 00:18:48.851
So there is a way to expose data and have kind of access to your data, but we cannot kind of offer the same level of interactivity between those two systems, one living inside your on-prem environment and, of course, the rest of Power Platform being in the cloud.

00:18:48.851 --> 00:18:51.567
And the same, for instance, for Power BI.

00:18:51.567 --> 00:18:54.686
We have in Power BI integration.

00:18:54.686 --> 00:19:00.480
We have the ability to embed a report or dashboard inside Business Central.

00:19:00.480 --> 00:19:16.643
So you have a report and dashboard that you create and that report lives in the Power BI service online and that's where you can kind of go to your Power BI dashboard or you can use your Power BI mobile app on a mobile device.

00:19:16.643 --> 00:19:21.525
You're accessing your dashboard and data that is in the cloud.

00:19:21.644 --> 00:19:23.883
I mean Power BI as a system lives in the cloud.

00:19:23.883 --> 00:19:26.111
I mean Power BI as a system lives in the cloud.

00:19:26.111 --> 00:19:40.388
Then embedding that specific selected report or dashboard inside Business Central, which is also online, that works seamlessly because they share the same authentication.

00:19:40.388 --> 00:19:54.169
We're talking about the same Entra tenant, so there is a way to embed, and Business Central offers a very nice UI to kind of just, you know, select all of those reports and just pick one and interact with it.

00:19:54.169 --> 00:20:06.652
But for Power Business Central on-prem that's not possible, because then Business Central on-prem would have to reach out to cloud Power BI.

00:20:06.652 --> 00:20:16.387
I mean, I know that there are partners that have done something around it and it's technically possible.

00:20:16.387 --> 00:20:19.388
I mean, everything is possible in software, right it?

00:20:19.690 --> 00:20:19.750
is.

00:20:21.163 --> 00:20:24.511
But it's not the standard way and not the reasonable way, I would say.

00:20:24.511 --> 00:20:27.092
It's not the standard way and not the reasonable way, I would say.

00:20:27.092 --> 00:20:39.289
But of course we have a lot of customers who are still working on-prem and would like to stay on-prem, and for them we all, of course, offer some capabilities in Power Platform realm as well.

00:20:40.082 --> 00:20:50.548
That's good to have both options for online and on-prem, with, again, some limitations based upon the architecture you mentioned with the cloud environment, authentication and data, versus where it sits.

00:20:50.548 --> 00:21:00.237
On-prem, which sometimes you know, you get a lot of the same functionality, but sometimes the challenges have to deal with authentication and where the data may reside and how much data you need to transfer.

00:21:00.237 --> 00:21:09.873
Answer when working with the connector and you know, my mind gets blown as far as how this world is now spreading out.

00:21:09.873 --> 00:21:13.003
Before it used to be a nice little world of business central or, you know, Microsoft Dynamics Nav.

00:21:13.003 --> 00:21:19.691
Now it's spread out now because of, you know, the ability to go into Power Platform and have these external connectors to integrate with.

00:21:19.691 --> 00:21:22.198
What are some of the?

00:21:22.198 --> 00:21:25.646
If someone were to start working with the Power Platform connector?

00:21:25.646 --> 00:21:28.313
I want to get into working with the Power Platform Connector.

00:21:28.313 --> 00:21:39.483
What are some insights that you may have or some suggestions you have to overcome some challenges, or what are some of the biggest challenges that you see when someone starts working with that?

00:21:43.511 --> 00:22:07.119
I don't know if this would be the biggest challenge, but of course, there is some basic kind of stepping stone, some basics that you need to sort out as a customer in order to start, and that, of course, starts with a license or an account or the ability to actually use one of those.

00:22:07.119 --> 00:22:23.137
Luckily, business Central paid license gives our customers access to Power Automate, power Apps, power BI and so on at no additional cost for majority of use cases.

00:22:23.137 --> 00:22:33.255
So this is something that comes with our licensing terms or licensing guide, and it's described there as limited usage rights.

00:22:33.255 --> 00:22:57.695
That's the specific term the licensing guide uses to describe a situation where you would be integrating power automate flow, for instance, inside Business Central for the business scenarios to extend Business Central to add some additional functionality in Business Central.

00:22:57.695 --> 00:23:14.594
If you would like to build a power automate flow that doesn't touch Business Central data and just sends you an email every day with weather forecasts for your city, very nice scenario, but that has nothing to do with Business Central.

00:23:14.594 --> 00:23:19.815
For that specific flow you would have to have a separate Power Automate license.

00:23:19.815 --> 00:23:31.074
But if you have built a flow that sends you a weather forecast for your customer location before you go and visit that customer on a given day.

00:23:31.074 --> 00:23:34.900
That's a scenario that uses business central data.

00:23:34.900 --> 00:23:40.317
So you might think about this as within those limited usage rights.

00:23:40.944 --> 00:23:54.798
Of course, it's just an example, but in order to get that, you have to either start Power Automate like a welcome wizard and select your region, click through a couple of questions.

00:23:54.798 --> 00:24:02.775
They ask the user, that starts, and then, of course, you have to approve also on the Business Central side.

00:24:02.775 --> 00:24:08.329
You have to approve also on the business central side.

00:24:08.329 --> 00:24:24.700
There is a privacy guide at the beginning of of the integration when you're starting and we're asking you to approve that um integration between those two systems, um and allow that to be offered to use either by you or all users in your organization.

00:24:24.700 --> 00:24:36.289
When you do that, there is actually a very easy way to get started inside Business Central because we offer multiple templates which you might think about.

00:24:36.289 --> 00:24:40.971
Like you know, predefined Power Automate flows, so we have a gallery of those.

00:24:41.905 --> 00:25:08.688
When you start and you go to Automate Group on, let's say, a customer list, you will see there is a list of different templates provided by us and you can just take one of them and have a have a flow that is built based on the template and, of course, later on modify, edit, so you will have to learn a little bit.

00:25:08.688 --> 00:25:16.554
We're talking about no code, low code, no code capabilities of Power Platform, for instance.

00:25:16.554 --> 00:25:34.211
If you're talking about Power Automate, it is still some form of a macro engine executing steps one by one, being able to go through some loops or some conditions.

00:25:34.211 --> 00:25:49.534
But it's like a very lightweight computer program and of course some basic understanding of how that works is required if you want to modify and start editing that a little bit.

00:25:49.534 --> 00:25:54.817
But it's not a huge problem, I would say.

00:25:54.817 --> 00:25:56.833
So getting started is not that complicated.

00:25:58.106 --> 00:26:02.330
And once you're online and you have the connector enabled, you have access to an environment.

00:26:02.330 --> 00:26:03.494
You can choose that environment.

00:26:03.494 --> 00:26:06.107
And you touched upon the licensing.

00:26:06.107 --> 00:26:11.026
Licensing to me across this whole system is one of those I'll say over and over again.

00:26:11.026 --> 00:26:16.505
I try not to even pretend to understand because to me it just gets a little complicated.

00:26:16.505 --> 00:26:31.074
But the licensing if you have a business central user, you have access to use Power Platform or Power Automate if you're using it within a Business Central scenario as part of a process within Business Central to extend it.

00:26:31.074 --> 00:26:36.256
So if it's reading or writing, you said it's limited use Is the limited?

00:26:36.357 --> 00:26:36.459
use.

00:26:36.459 --> 00:26:38.451
As far as Limited usage rights, yeah.

00:26:38.731 --> 00:26:39.213
Usage rights.

00:26:39.213 --> 00:26:40.891
Okay, so it's limited usage rights.

00:26:40.891 --> 00:26:44.594
Does that mean it's read-only as well?

00:26:44.775 --> 00:26:45.746
No, no, no, or is it?

00:26:45.746 --> 00:26:46.650
You have access to write back?

00:26:46.650 --> 00:26:50.173
Yes, you have access to data.

00:26:50.173 --> 00:27:07.515
You can read and write data and the fact or entities that you as a user specific user have access to in Business Central, that can be controlled in Business Central as well, and Power Platform and our connector would honor that right.

00:27:07.515 --> 00:27:12.884
So, if you set up permissions, this user is not able to read employees' data, for instance.

00:27:12.884 --> 00:27:20.134
They won't be able to read employee data, regardless whether they use Excel, our web client, mobile app, power Platform.

00:27:20.134 --> 00:27:21.789
That is obviously honored.

00:27:21.789 --> 00:27:23.094
That is obviously honored.

00:27:23.094 --> 00:27:41.377
But, of course, if that user has the right to read and write data from a specific table, let's say customer's table, they will be able to do it also through Power Automate or Power Platform solutions using our connector.

00:27:42.226 --> 00:27:59.372
Connector is actually one of the ways to do to interact with our data because, as I mentioned, we have Power BI, which is read-only by nature, so that uses slightly different technology, also called a connector, but slightly different technology.

00:28:00.252 --> 00:28:04.578
But we also have another tool which is based on Dataverse.

00:28:11.244 --> 00:28:29.939
So if you, for those of our listeners here who are not familiar, dataverse is the data management platform from Microsoft, more like a complex database system for business applications, and that is also a system that sits below Power Platform.

00:28:29.959 --> 00:28:39.655
So Power Platform is built on top of Dataverse and Dataverse has a concept of something that is called virtual tables.

00:28:39.655 --> 00:28:41.989
We also support that.

00:28:41.989 --> 00:28:51.896
So virtual tables allow you to take a given API from Business Central so we're still talking about APIs in the same way and visualize that.

00:28:51.896 --> 00:29:18.338
That means a given table or API from Business Central let's say, customers API becomes a table in Dataverse and it's visible, accessible, just as any other table in the Dataverse user interface, and you can edit the data, build views on top of that, build apps on top of that.

00:29:18.338 --> 00:29:30.115
You can use that data in Power Pages, for instance, because Power Pages is built on Dataverse only, so it requires Dataverse, and so on.

00:29:30.115 --> 00:29:38.035
So there are kind of situations or scenarios where you would use Dataverse and you would use Dataverse virtual tables.

00:29:38.035 --> 00:29:47.816
As I said, it's just another technology to access business central data through APIs and have them offered to Power Platform.

00:29:49.086 --> 00:29:52.253
Are all Power Platforms sit on top of Dataverse.

00:29:52.253 --> 00:29:55.461
All of them.

00:29:56.267 --> 00:30:00.057
So, as I said, power BI is a slightly different beast.

00:30:00.057 --> 00:30:19.704
Power BI has its own data management system because the data that is imported, let's say, into Power BI and there are various ways how that can be done is, by default and by design, read-only.

00:30:19.704 --> 00:30:26.554
So all the ways of integrating data through Power BI is read-only.

00:30:26.554 --> 00:30:50.666
So they can offer different types of, let's say, more advanced data store mechanisms and also mechanisms for storing bigger data sets and data sets that are already aggregated, pre-calculated, and so on and so forth.

00:30:50.666 --> 00:30:57.392
And then you're going into different data type of solutions for analyzing data.

00:30:57.392 --> 00:31:03.653
So they are not using directly Dataverse as, for instance, powerapps do.

00:31:04.665 --> 00:31:12.611
Yeah, for some reason throughout the years, I always find Power BI to be entirely, even though it has the name Power in front of it.

00:31:12.611 --> 00:31:19.296
For some reason I don't ever consider it as part of the Power Platform family, even though it technically is.

00:31:19.296 --> 00:31:24.457
So I'm trying to have that concept in my mind be the same family.

00:31:24.457 --> 00:31:28.144
So you had mentioned about quite a few features.

00:31:28.144 --> 00:31:38.671
Is there any underutilized features in Power Automate that maybe people should consider, maybe start utilizing because it's underutilized right now?

00:31:41.527 --> 00:31:46.198
If we're talking about integration between Business Central and Power Automate, I can, of course, comment on that.

00:31:46.198 --> 00:31:47.380
If we're talking about integration between Business Central and Power Automate, I can, of course, comment on that.

00:31:47.640 --> 00:31:50.201
If we're talking about Power Automate in general.

00:31:50.201 --> 00:31:54.208
Let's leave it to my colleagues from Power Automate team.

00:31:54.208 --> 00:32:20.921
Yeah, I would definitely say that we see a lot of interest in our approval scenarios and those approvals that are built on top of Power Automate are some maybe a hidden gem, maybe a feature that might be, I wouldn't say, forgotten.

00:32:20.921 --> 00:32:28.688
But you know that's something that sits a little bit behind and not everyone is able to kind of fully use it.

00:32:28.688 --> 00:32:56.768
But it's also an interesting discussion when to use this instead of using our internal approval engine, the one that you internal approval engine, the one that you probably know even from the NAV times, because not always power automate is the answer, and that's, of course, a natural choice, a natural path.

00:32:56.768 --> 00:33:39.001
But there are ways, there are moments where the approval system should actually be happening and should be, partially at least, orchestrated outside of Business Central, when that approval needs to use some data on top of data from Business Central in order to execute the approval, find the right approver, maybe apply some rules that should be built in when the approval is actually going and adding some data to external system.

00:33:39.001 --> 00:33:57.453
When a request for approval happens, it has to be logged somewhere else on top of Business Central, when the approval, the fact that the document or the change, data change has been approved needs to be logged somewhere else as well.

00:33:57.453 --> 00:34:11.255
And I'm not even talking about, you know, sending the actual request for approval to your mobile device, sending someone's text message or WhatsApp message, stuff like that.

00:34:11.255 --> 00:34:23.829
It's all possible in Power Automate using different connectors not necessarily inside Business Central, because Business Central would not know how to send a text message or a WhatsApp message.

00:34:23.829 --> 00:34:25.414
Power Automate does.

00:34:25.704 --> 00:35:00.385
So there are cases where this system makes total sense, but also then and this is also discussions we have been quite often with customers the actual approval process then is to some extent handled through Power Automate and is run in Power Automate, and the data is stored in Power Automate, actually in Dataverse environment, and not necessarily everything is stored in Business Central.

00:35:00.385 --> 00:35:21.695
So there is always a little bit of a compromise and a little bit of a decision in terms of which system to use and how to build it, but it has a great potential, so definitely something that I would like to see more of our customers kind of being interested in.

00:35:21.695 --> 00:35:31.036
We actually also know that we have plenty of things to do in terms of our features or features that are missing.

00:35:31.036 --> 00:35:48.570
But we are trying to deliver with every wave, with every update, trying to deliver new improvements in that area and react on feedback and talk to our partners.

00:35:49.713 --> 00:35:52.077
Yeah, that's Improve, that's great.

00:35:52.077 --> 00:36:04.472
So I know there's been a lot of the AI co-pilot where it's simplifying it in a sense, where you need to create a part automate flow and just be able to describe it.

00:36:04.472 --> 00:36:12.653
Is that a continued push for people Like you know, let's say, for example, myself are very interested in it?

00:36:12.653 --> 00:36:16.813
You know, obviously you can get started with using Copilot to build that.

00:36:16.813 --> 00:36:24.894
You know what's one way for me to learn more about Copilot using with Power Automate.

00:36:24.894 --> 00:36:26.418
You know where do you get started.

00:36:26.418 --> 00:36:29.815
I know there's still a lot of people figure out where do I even begin?

00:36:29.815 --> 00:36:33.311
There's so many things you could do with Power Platform or Power Automate in general.

00:36:36.108 --> 00:36:43.635
No, this is a good point and definitely an interesting development that is happening right now in front of our eyes.

00:36:43.635 --> 00:36:48.596
So let's talk about that and demystify a bit.

00:36:48.596 --> 00:37:10.954
First of all, power Automate as a product has a co-pilot experience in the designer, especially the new designer, where when you are editing a flow, you have already this kind of macro instructions, step-by-step, what to do and so on.

00:37:10.954 --> 00:37:19.755
You have that already on screen and then you would like to modify it, you would like to add a new action and you would like to add an approval or condition and so on.

00:37:19.755 --> 00:37:53.137
So the normal procedure is you select one of the actions from this whole catalog and all actions in Power Automate, so those building blocks like like loop condition and so on, and various kind of actions that are offered in standard mode but also from those connectors.

00:37:53.137 --> 00:38:10.541
So there is like a a really really huge selection of different things that you that you need to understand and of course, there is a you is different search experiences and different kind of ways to select or indicate your favorite actions.

00:38:10.541 --> 00:38:13.434
But you need to understand what you're doing to some extent.

00:38:13.945 --> 00:38:21.940
If you are using Copilot, pain inside Power Automate, you can tell Copilot hey, I would like to add an additional approval step.

00:38:21.940 --> 00:38:23.289
I need to send an email.

00:38:23.289 --> 00:38:41.148
Additional approval step I need to send an email and the copilot inside Power Automate would know ah, okay, so that user would like to use the Outlook connector action to send an email and it will add it to Power Automate flow.

00:38:41.148 --> 00:38:43.494
So it's a great help.

00:38:43.494 --> 00:38:45.929
They already.

00:38:45.929 --> 00:38:54.135
They also introduced a feature where you can start that flow describing what you would like to create.

00:38:54.135 --> 00:38:59.088
As you mentioned, you kind of like create a flow using natural language.

00:38:59.088 --> 00:39:07.675
That feature actually, by the way, was available in Power Automate even before this whole, you know, chat GPT revolution.

00:39:07.675 --> 00:39:13.476
That happened, what was like almost two years ago, right?

00:39:14.485 --> 00:39:16.954
Yeah, november 20, 2022.

00:39:16.994 --> 00:39:18.166
Yeah precisely so.

00:39:18.166 --> 00:39:20.554
That feature already existed in Power Automate.

00:39:20.554 --> 00:39:24.690
It was based on a slightly different model but the concept was the same.

00:39:24.690 --> 00:40:25.389
Business Central right now is integrating with that feature and that is because Power Automate team also introduced a different interactive kind of way of creating those flows and there was a really cool demo at a recent build conference where they were showing how Copilot from Power Automate is able to kind of interact with the user and detect the intent of the user and maybe even suggest the ways of building automation based on that intent and then on the end the output of it will be a proposed flow structure which then of course the user or the creator in the flow designer experience can continue to edit and also use co-pilot features to add more and more steps to it.

00:40:25.389 --> 00:40:34.780
So it's like an interactive design process between the user and co-pilot inside Power Automate.

00:40:34.780 --> 00:40:39.096
So this feature is currently being integrated inside BC.

00:40:40.425 --> 00:40:44.898
At this point today we don't have it yet shipped in production.

00:40:44.898 --> 00:40:49.876
So you have seen various kind of videos and posts about that.

00:40:49.876 --> 00:40:56.134
You have seen us demoing that at recent conferences, but this is not yet released in production.

00:40:56.134 --> 00:40:57.610
Just wanted to clarify.

00:40:57.610 --> 00:41:30.097
But we're working on finalizing this and we hope to have that later this wave, and that will allow you to start flow from within Business Central, not only by selecting a pre-built template that we have, but just like typing or, you know, using Windows H and dictate feature in Windows to just speak to your computer and explain what you wanted, and then observe the results and then edit.

00:41:31.429 --> 00:41:32.135
That would be amazing.

00:41:32.135 --> 00:41:34.449
I saw that on the piece.

00:41:34.449 --> 00:41:39.951
What Surface Copilot Plus or something like that, which is going to be pretty exciting.

00:41:41.005 --> 00:41:42.110
That is another angle.

00:41:42.110 --> 00:41:52.496
That is another angle, but it's actually Power Automate, because Power Automate offers this feature to translate the natural language into a flow.

00:41:52.496 --> 00:41:55.753
Already that feature is available in Power Automate.

00:41:55.753 --> 00:42:00.713
What we are right now building inside Business Central is just that kind of integration right.

00:42:00.713 --> 00:42:12.018
So this Power Automate user interface needs to fit inside BC, but the feature itself is available so it's easy to go and play with that in Power Automate.

00:42:12.018 --> 00:42:32.956
Of course, Power Platform teams various Power Platform teams are integrating Copilot in the design experience so you can also build Power Apps using natural language right, Describing what is that you needed, and then Copilot will build that.

00:42:33.606 --> 00:42:45.293
It's almost meant to be for Copilot and Power Platform, because a lot of times when you're using Copilot, you could ask exactly what you're trying to accomplish with Power Automate or Power Platform.

00:42:45.293 --> 00:42:49.416
I mean, you have all the tools you need to build something for you.

00:42:49.416 --> 00:42:51.405
It just makes more sense.

00:42:51.405 --> 00:42:51.764
Now.

00:42:51.764 --> 00:43:04.375
You know, I've been working with Power Automate and sometimes you have several people that would help you, or a company may have, you know, internal IT staff members.

00:43:04.375 --> 00:43:06.436
A company may have internal IT staff members.

00:43:06.436 --> 00:43:14.461
How do you manage in terms of versioning, Someone jumping in, making some changes or I make some changes?

00:43:14.461 --> 00:43:20.606
Is there an easy way for someone to be able to manage?

00:43:21.487 --> 00:43:22.208
some of those versions?

00:43:22.208 --> 00:44:01.391
Yeah, that's a good question and that's also where you will see, or you see already, power platform, various power platform teams and components, kind of evolving from, you know, like a couple of years ago being relatively simple tools for a single creator, local developer, and right now becoming a tool for normal standard development teams or traditional development teams with support for tools like GitHub versioning and so on.

00:44:01.391 --> 00:44:22.224
So Power Automate right now has the ability to, you know, like the definition of the flow is actually a JSON content which can be stored in a standard source control version, you know, being versioned as a normal kind of source code.

00:44:22.224 --> 00:44:32.016
We have added support for Power Platform solutions to our AL go for GitHub tooling.

00:44:32.016 --> 00:45:07.916
So if you're building your solutions for Power for Business Central specifically, you can build code in AL and extensions for Business Central and Power Platform solutions, you can build that or use that in the same build process and it will generate an extension for Business Central but also a Power Platform solution, and that solution in Power Platform is this kind of package so it can include a Power App, power Automate, power BI and so on.

00:45:09.467 --> 00:45:28.840
So this is kind of currently normally supported in our development tools and of course you can discuss, like in some cases, should I need a Power Automate inside my fantastic AL program that I love, inside my fantastic AL program that I love?

00:45:28.840 --> 00:45:39.476
I know that there are some traditional developers out there that do not believe that the new modern world is coming.

00:45:39.476 --> 00:45:40.197
But yeah, it is.

00:45:40.197 --> 00:45:44.657
So get started with PowerEdge Copilot.

00:45:46.047 --> 00:45:47.090
No, it's definitely coming.

00:45:47.090 --> 00:45:52.393
The world changes and sometimes it's important to look forward to see some of the benefits that you have.

00:45:52.393 --> 00:46:05.835
I'm happy to hear that there's an effort into the source control management or the version control management to work with deployments, because even with it being a JSON file, whatever it is, a simple change could affect the flow.

00:46:05.835 --> 00:46:12.132
To go back, a few moments ago you had talked about the workflow and I liked one point that you had mentioned.

00:46:12.132 --> 00:46:16.351
It's not always just because you have the tool doesn't mean you have to use the tool.

00:46:16.351 --> 00:46:23.534
You need to evaluate your process to determine would the standard business central workflow work or do you want to use a Power Automate workflow?

00:46:23.534 --> 00:46:30.833
In discussions that I've had with Power Automate and workflows in particular, I would like to talk about some other scenarios afterwards.

00:46:32.307 --> 00:46:34.724
It's a matter of what are some considerations.

00:46:34.724 --> 00:46:44.097
You had mentioned one, which was if you need to have access to an external system to come up with a decision, such as maybe emailing or doing a WhatsApp message or something.

00:46:44.097 --> 00:46:52.478
The decisions such as maybe emailing or doing a WhatsApp message or something would be one consideration for when to use Power Automate or to use a flow for an approval process.

00:46:52.478 --> 00:47:05.338
What are some other considerations that you would suggest for when to use Business Central processing and Power Automate processing, but then also in a particular workflow.

00:47:06.005 --> 00:47:14.210
Is it that once you hand it over the approval to Power Automate, now Power Automate owns the approval and it finishes there?

00:47:14.210 --> 00:47:19.295
Or is there a workflow or a process where you can send something for approval?

00:47:19.295 --> 00:47:31.070
An external process will occur, whether it has to read data from Power Automate to have a flow and then come back into Business Central to be able to pick up the process again, to continue the approval process.

00:47:31.070 --> 00:47:32.387
So is it my question.

00:47:32.387 --> 00:47:39.219
More is is it a complete handoff or is it a handoff for a step, come back and then I continue within Business Central?

00:47:41.746 --> 00:47:42.728
Yeah, it's a good question.

00:47:42.728 --> 00:47:52.661
There is some form of a handshake system between business central approval system and the power automate.

00:47:52.661 --> 00:48:08.614
It's relatively simple but in essence business central approval actually starts power automate and then at the end whatever is happening on Power Automate could be for multiple days, even right.

00:48:08.614 --> 00:48:24.074
The end result will be sent to Business Central and stored and the basic workflow in Business Central that uses Power Automate would be very simple.

00:48:24.074 --> 00:48:38.115
But you can imagine kind of mixing them a little bit more and kind of like maybe getting some additional actions on Business Central side after the approval was completed on Power Automate Possible.

00:48:40.239 --> 00:48:55.226
I would say that most cases for situations or for customers who are interested in a little bit more flexibility and a process that is happening outside of Business Central for a good reason.

00:48:55.226 --> 00:49:21.996
As I said, external data, storing data somewhere, for instance storing some prerequisites or outputs of the approval process on a SharePoint location that all is available in Power Automate very easily and it's also easily editable.

00:49:21.996 --> 00:49:27.873
So if you have a requirement from your customer, hey, I would like to change this a little bit and add something.

00:49:27.873 --> 00:49:44.197
It's relatively easy to modify an already running Power Automate flow to add more without calling a developer or without doing too much of tweaking in what is available in Business Central.

00:49:44.965 --> 00:50:13.632
Now, that said, business Central approval engine, that built-in kind of engine, is also relatively flexible and has an ability to deliver most of the standard kind of scenarios, right Multi-level approvals, group approvals, and so on and so forth, sending an email with that approval details, and so on.

00:50:13.632 --> 00:50:24.077
So there might be scenarios where you can just do everything in Business Central without touching Power Automate.

00:50:24.077 --> 00:50:30.114
You would be, of course, a little bit limited to the UI that we offer in that workflow engine.

00:50:30.114 --> 00:50:42.197
That workflow engine UI, or the UI when you build and configure your approval, is a bit old style, I would say.

00:50:42.197 --> 00:50:57.253
So for some it might be a little bit difficult to to understand how to tweak it, but on the other hand, it might be absolutely good enough for some cases, right?

00:50:57.253 --> 00:50:59.416
So yes, it depends a little bit.

00:50:59.436 --> 00:51:10.844
yes, you had mentioned primarily workflows was a good use case that you said was a hidden gem, where using Power Automate within the flow process working.

00:51:10.844 --> 00:51:17.588
We've talked about Power BI for reporting again, which it's its own animal, and then, with this, consuming APIs.

00:51:17.588 --> 00:51:27.708
What are some other use cases that you have come across where leveraging the connector for Power Automate enhanced the Business Central implementation?

00:51:29.914 --> 00:51:37.269
Well, I think we should also go a little bit beyond Power Automate, but let's stay with Power Automate for a while.

00:51:37.269 --> 00:51:44.271
So Power Business Central is integrated with Power Automate in three different ways.

00:51:44.271 --> 00:51:49.315
You might say we talked about approval process and the approval engine.

00:51:49.315 --> 00:52:14.675
That's probably the most kind of common scenario, but you have also two different other ways, and they are actually represented inside BC in the Automate group, because the gallery of templates differ and we have different templates for those three different kind of use cases, and so let's leave approvals on the side now.

00:52:14.675 --> 00:52:57.519
The other use cases are when we are talking about automated flows that run in the background, read data from Business Central and process the data, and for that you might have scenarios where either you need to react on data changes in Business Central and, for instance, you're integrating with some system and you need to send data whenever that data changes in BC or whenever a new sales order is approved or posted stuff like that or you need to build an integration that is happening or reacts on an event that is outside of Business Central.

00:52:57.519 --> 00:53:03.436
You get a new email, you get a new order from a third-party system.

00:53:03.436 --> 00:53:12.445
Now that you have to integrate with inside Business Central, you want to build something that runs every Monday morning.

00:53:12.445 --> 00:53:25.581
That's also another kind of type of an automated flow based on different events trigger that is happening outside of business center.

00:53:25.581 --> 00:53:35.318
It could be pretty much anything, starting from an email or new files that showed up on a SharePoint location.

00:53:35.318 --> 00:53:42.954
If someone uploaded a new file, that triggers some automation, that happens to add some data to BC.

00:53:42.954 --> 00:53:45.351
That's also one of the popular scenarios.

00:53:45.351 --> 00:53:50.177
Those types of flows would be kind of invisible to the user.

00:53:50.177 --> 00:53:57.992
They are running behind the scenes and they can react with data or interact with data.

00:53:59.405 --> 00:54:03.389
And then the third way is the action that is based on the flow.

00:54:03.389 --> 00:54:34.672
So in BC we have that way, that integration component where you can build an action, place it in this central UI, you can personalize that, move it, rename it and so on, and that action looks like a normal action in the action bar on the, let's say, sales document page but triggers a flow power automate flow and that flow shows up in business central on the side as a power automate site pane.

00:54:34.672 --> 00:54:58.992
There is a very easy way to build some additional user interface components in power automate so you can ask file name, date, additional comment or text field, so you can build a drag and drop way, some additional UI that shows up in BC and then process the data.

00:54:58.992 --> 00:55:07.355
So then Power Automate Flow is aware of the data from BC because it is running in the context of a specific record.

00:55:07.355 --> 00:55:27.219
You are on a sales order, you press that button, power Automate got the idea of that sales order, the user, the environment, the company, the date, all that stuff, and then it can additionally get the user input at runtime.

00:55:27.344 --> 00:55:57.793
So the user wrote a comment or selected a date, and then Power Automate Flow uses the data from Business Central record from the user, reads anything else that is needed from other third-party systems and then executes the action and then sends an update or writes back to BC or sends notifications, sends an email, whatever you want, but it's an action that is then triggered manually by the user.

00:55:57.793 --> 00:56:21.916
Power Automate calls it an instant flow, which is like basically an instant flow run instantly when the user selected, and the fact that it could be integrated within BC and shown in the UI gives our consultants and customers a very easy way to expand Business Central.

00:56:21.916 --> 00:56:40.896
Right, if you need to add something, especially if you need to add something that kind of interacts with the external world or one of the actions is that interaction with the external world, sending a Teams message or an email?

00:56:40.896 --> 00:56:48.177
That type of a flow based on an action is really useful.

00:56:49.086 --> 00:56:50.311
Talk about some scenarios.

00:56:51.186 --> 00:58:06.818
I think last year, one of the summit sessions, I did a summit and I love how Power Automate continues to push the envelope, because I was able to take the Power Automate, use it with Power Virtual Agents and Teams and Outlook, and then Business Central, where the conversation started from a chat with the end user about, you know, maybe at their website or something like that, where you ask certain questions and it takes those answers as variables and then use Power Automate to go ahead and collect all of that and either post it on Teams or send an email and say, hey, there's a new client that's interested and then have it right into Business Central as a contact or a customer which is at that time was like this is amazing, this is amazing, and I'd love to see more of those, more of those demos showcasing like, hey, you can have a basically almost a free sales order taker Not free, but like a sales order taker where you don't have any interaction and I just want to say, hey, I'm interested in this, you know, and then have a record show up in Business Central as a new client.

00:58:07.865 --> 00:58:08.969
So it is quite powerful.

00:58:08.989 --> 00:58:10.074
That's a perfect scenario.

00:58:10.074 --> 00:58:20.518
This is a great scenario and this is also something that, as you mentioned, it was already possible for using Power Virtual Agents.

00:58:20.518 --> 00:58:33.431
So Power Virtual Agents used to be or this is the product that existed for a while called Power Virtual Agents and that was designed specifically to build chatbots.

00:58:33.431 --> 00:58:49.414
Those chatbots were relatively programmed in a similar way as Power Automate, so they were prescribed and they were able to call Power Automate and that way you will be able to call Business Central and so on.

00:58:49.414 --> 00:58:54.891
Nowadays, microsoft actually rebranded this product as Copilot Studio.

00:58:54.891 --> 00:59:01.215
So right now, part of Power Platform family is a product that is called Copilot Studio.

00:59:01.215 --> 00:59:06.431
But it's not only a rebrand, it's actually much more powerful.

00:59:06.431 --> 00:59:19.436
It still has the same concept of topics and bots and so on, and you can still use Power Automate, but you can also use our connector, or most of the connector, as plugins, as data plugins.

00:59:19.436 --> 00:59:48.795
You can point that chatbot or copilot that you create because you're actually creating copilots using Copilot Studio to a specific documentation page or feed it with some data and it will learn and it will build some logic and it will build some kind of conversation with the user and then you can hand off to data to create some data in BC, as the example that you explained.

00:59:48.795 --> 01:00:20.568
But on top of that, copilot Studio and actually the rest of Power Platform products also have access to AI Builder, which is part of Power Platform platform, and that AI builder allows, gives you a capability to build your own large language model actions.

01:00:20.568 --> 01:00:26.400
So you build your own black box prompt which takes an input and spits out something, right?

01:00:26.400 --> 01:00:35.135
So you think about your, your own kind of add-on to ALM and then you can use it inside your Power Automate flows or inside your Copilot Studio chat experience, right?

01:00:35.135 --> 01:00:49.246
So if you think about the customer is coming to your website, that chatbot based on the Copilot Studio, copilot can be placed inside your PowerPages website.

01:00:49.246 --> 01:00:54.753
So you build a page using PowerPages, another component from PowerPlatform.

01:00:54.753 --> 01:00:58.152
It can read data from Business Central.

01:00:58.152 --> 01:01:02.914
You can see my catalog of items, for instance.

01:01:02.914 --> 01:01:16.490
So inventory published for your users, for your potential users, external users, sure, but you can build an experience where that customer can kind of explain what they really want like, explain a little bit more.

01:01:18.289 --> 01:01:22.869
Then the prompt you will have to build like a specific prompt for your use case.

01:01:22.869 --> 01:01:44.780
Think about, I don't know, you have a bike shop and you have different bike components and the user is interested in building a specific type of a of a bike or needs to buy a special kind of headlamp that would be available for them, lamp that would be available for them.

01:01:44.780 --> 01:02:04.400
They can explain pretty much in natural language and you just build a prompt that reads the data, reads the input from the customer, but it's also grounded in some knowledge about the domain, in some knowledge about the domain, right?

01:02:04.400 --> 01:02:14.213
So let's say, you have a couple of Word documents that explain how to offer those different types of lamps or bike components to your customers.

01:02:14.213 --> 01:02:27.014
So the output of that black box kind of prompt, using AI Builder, could be a suggested list of items or like products that we would like to offer.

01:02:27.204 --> 01:02:35.996
And then, as you know from various examples online, the ability of generating an email as a response.

01:02:35.996 --> 01:02:42.518
That's a basic capability of any ALM model right now.

01:02:42.518 --> 01:03:03.552
So building some form of, you know, automated or semi-automated tool that would take an input from a potential customer, save that data as a contact, propose an email response with some suggested lines, no problem at all, right?

01:03:03.552 --> 01:03:10.315
So for a specific use case, that is perfect scenario for Power Platform.

01:03:10.315 --> 01:03:11.527
So definitely.

01:03:11.527 --> 01:03:16.711
I mean it's just mind-blowing sometimes like what can be done.

01:03:16.711 --> 01:03:21.233
It just requires a little bit of poking around and learning those new tools.

01:03:21.233 --> 01:03:23.693
But it's really, really amazing.

01:03:24.126 --> 01:03:27.972
You just did a dreamer, I listened to all of this and you could do anything with it.

01:03:28.686 --> 01:03:30.556
It's just the way.

01:03:30.556 --> 01:03:37.574
And what were the efficiencies we're able to gain from all of this and to also offer better customer service?

01:03:37.574 --> 01:03:51.601
You know you talk about the order entry and in suggesting products it's something that's available 24 hours a day and the amount of data that can be processed in a shorter period of time to offer those suggestions.

01:03:51.601 --> 01:03:58.067
You know we're going to have all this like I want this, and it'll be automatically built, put together, sent and shipped within a few moments.

01:03:58.067 --> 01:04:06.222
It is mind-blowing and it does force someone to change the way they think.

01:04:06.222 --> 01:04:19.472
He mentioned earlier how sometimes some may be a little resistant to identify or to see what's happening, but it seems to be here and I see a lot of, a lot of changes coming from.

01:04:19.472 --> 01:04:23.237
It is well too.

01:04:30.130 --> 01:04:57.010
Wow, yeah, and the whole thing is that, as we discussed, you as a business central partner, integrator or even an admin or operator of Business Central inside a company, if you're familiar with those tools and you can kind of visualize or you can imagine what could be done for a specific scenario that you have in mind.

01:04:57.144 --> 01:05:05.331
So if you're thinking about improving your business process, power Platform might be an ideal tool, just because it is this kind of low code, no code.

01:05:05.331 --> 01:05:10.597
But of course, as we discussed, it doesn't have to be Power Platform.

01:05:10.597 --> 01:05:37.630
Sometimes it's very easy to just use a Business Central mobile app, load it on your device, customize the UI a little bit inside Business Central just using a page customization tool, and just remove some of the fields that are not needed, build something more simplified and that will be shown on your mobile device and you can edit data and that's it.

01:05:37.630 --> 01:05:39.996
Maybe that's what you needed.

01:05:39.996 --> 01:06:00.318
Right, you don't need to build a separate specialized app for that, but if you do, then Power Apps could be your friend, because then it allows you to build a user interface for a mobile without actually coding the mobile platforms.

01:06:01.106 --> 01:06:16.641
Yeah, I think in the SMB space this is certainly an advantage and a differentiator, especially when you're growing your business and sometimes adding more people may not be the right thing.

01:06:16.641 --> 01:06:34.010
Certainly, I would highly encourage for SMBs to look at Power Platform, to kind of expand the business that way, and I still think that there's a lot more that we need to do to educate the SMB space about its capabilities.

01:06:34.010 --> 01:06:41.952
It's slowly getting there, at least from my experience, because a lot of people are still like, wow, I didn't know that existed.

01:06:43.405 --> 01:06:44.329
I didn't know you could do that.

01:06:44.329 --> 01:06:55.367
Some of that I think it goes with also the partner channel being aware of it, because if customers aren't aware of it, where are they going to hear from it?

01:06:55.367 --> 01:06:57.434
If partners aren't aware of it, where are they going to hear from it?

01:06:57.434 --> 01:07:02.155
So it's, and listen to you talk about even the mobile app as a solution.

01:07:02.155 --> 01:07:17.626
It's how many people would think that modifying the mobile app slightly, like you said, with the page customization, would be a solution and not have to create something in power app or have to create a new page or a new option or a new integration as well.

01:07:17.626 --> 01:07:21.172
So it's, it's, that's the only thing that keeps you know.

01:07:21.233 --> 01:07:28.773
It sort of scares me is knowing all of these options, because before you could have a few people who knew things well.

01:07:28.773 --> 01:07:51.773
Now you have to really know what options are available and then be able to determine how to you know, analyze and evaluate which solution is going to provide the better, which, which tool is going to provide the better solution for the problem that you're trying to solve, because you know, as you'd mentioned, the mobile app may be perfect in one case, a power app may be perfect in another case.

01:07:51.773 --> 01:07:56.076
And then, using the Business Central application itself may be another one.

01:07:56.076 --> 01:07:57.289
That is a challenge.

01:07:57.289 --> 01:08:01.644
With all of these new options, which is the best for a scenario?

01:08:01.644 --> 01:08:02.380
How do we solve that problem?

01:08:02.380 --> 01:08:03.782
Which is the best for a scenario?

01:08:03.782 --> 01:08:05.844
How do we solve?

01:08:05.884 --> 01:08:06.144
that problem.

01:08:06.144 --> 01:08:06.385
That's the-.

01:08:06.385 --> 01:08:18.435
Yeah, we are trying from our end here, you know, updating documentation, changing, publishing various videos and kind of sharing the knowledge.

01:08:18.435 --> 01:08:56.393
I'm a big fan, of course, of, you know, speaking to our partners whenever I can and sometimes we have events happening here in the office, sometimes, of course, different conferences and meetings that we that you know, in the community, in the partner community or partner channel, in business central partner channel, we also present in, like, we're working with Power Platform teams as well, right, so, because we actually are kind of similar or the same engineering organization, so we're working quite closely with them.

01:08:57.225 --> 01:09:25.377
Sometimes, you will see, you know, business Central mentioned in Power Platform announcements and news because it's actually a very popular product from Microsoft for similar group of customers, because Power Platform quite often is also popular within SMB customers.

01:09:25.377 --> 01:09:29.252
So we tend to work with them.

01:09:29.252 --> 01:09:31.807
They come to our conferences.

01:09:31.807 --> 01:09:35.295
You will see Power Platform people speaking at directions.

01:09:35.295 --> 01:09:38.150
You will see us speaking at Power Platform conferences.

01:09:38.150 --> 01:09:48.835
I will be speaking in Vegas a couple of weeks from now again talking about Business Central and showing Business Central to our platform community.

01:09:48.835 --> 01:09:51.233
So we operate together.

01:09:51.233 --> 01:10:02.515
But, yeah, of course, always it's a huge challenge, especially that the world is moving forward, so all of those tools are evolving constantly.

01:10:02.515 --> 01:10:09.275
So, yeah, it is a bit of a challenge to keep up as pretty much with technology.

01:10:09.317 --> 01:10:14.893
Oh, it is it is and it's, you know I don't know if anybody has the answer it's just a matter of how to manage the information.

01:10:14.893 --> 01:10:20.011
There's a lot of information being presented to a lot of people, so how do you filter it and process it?

01:10:20.011 --> 01:10:20.895
This is another.

01:10:20.895 --> 01:10:23.509
It's a philosophical conversation.

01:10:23.509 --> 01:10:29.096
I go down sometimes as far as data management but, uh, this, I think of this.

01:10:29.096 --> 01:10:31.300
You know I had to start drawing lines.

01:10:31.300 --> 01:10:38.386
I know things exist and I'll just stop there and know that, hey, let's talk to somebody about this to explore the option.

01:10:38.386 --> 01:10:40.248
Uh, they have the awareness.

01:10:40.248 --> 01:10:47.096
So, uh, well with that belagia, so well with the Appalachia.

01:10:47.256 --> 01:10:50.761
As with every episode, I'm always overwhelmed, mind blown.

01:10:50.761 --> 01:10:56.899
There's always a lot of information and it's amazing to see how much the world is changing, how rapidly it's changing.

01:10:56.899 --> 01:11:15.287
But I would like to thank you for taking the time to speak with us today to share some of your insights onto using the Power Platform with Business Central, talking just a little more about what the connector is and also we've been touched upon, you know, identifying the different solutions and options that are available for some of the areas.

01:11:15.287 --> 01:11:28.146
If anyone would like to learn a little bit more, as we were just talking about Power Automate, the Power Auditor, connector and some of the options.

01:11:28.146 --> 01:11:31.677
How do you suggest somebody get in contact with you, or are there any specific resources you think that someone should look at to get the information?

01:11:33.725 --> 01:11:50.537
Yeah, so, as always, we have gathered all the resources under various kind of akams links, if you're familiar with this concept, under various kind of akams links, if you're familiar with this concept, the one and single link to rule them all is always bcol.

01:11:50.537 --> 01:12:06.034
So akams slash, bcol gives you a doc page with various kind of links to different doc sites and resources that will be, also for partners, but also for customers.

01:12:07.024 --> 01:12:21.396
And in the same way you can go from there from BC All, but we have individual resources for Power Automate, like BC Automate, bc PBI, bc Power Apps and so on.

01:12:21.396 --> 01:12:29.671
The easiest way is just to start with BC All and then for partners, we have a Yammer community as you might be familiar with.

01:12:29.671 --> 01:12:37.855
We have a really kind of active community and discussion on Yammer.

01:12:37.855 --> 01:12:42.587
We use that as a tool to talk to partners directly.

01:12:42.587 --> 01:12:49.456
So I'm kind of actively operating within that Power Platform group that exists there.

01:12:49.456 --> 01:12:53.274
And then, of course, my email is no secret.

01:12:53.274 --> 01:13:06.073
So, if anyone would like to, I mean no secret at all, because basically Microsoft employees have all common email addresses, right?

01:13:06.073 --> 01:13:09.332
So which is the first name, dot, last name at microsoftcom.

01:13:09.332 --> 01:13:13.552
So that's how you can also reach me blazeykotelko at microsoftcom.

01:13:15.006 --> 01:13:16.011
Excellent, excellent.

01:13:16.011 --> 01:13:17.909
Well, thank you again for your time.

01:13:17.909 --> 01:13:18.814
We appreciate it.

01:13:18.814 --> 01:13:22.770
Time is the currency of life and once you spend it, you can give it back.

01:13:22.770 --> 01:13:28.703
So anybody who speaks with us, we appreciate you doing that and thank you again.

01:13:28.722 --> 01:13:29.284
Thanks a lot, guys.

01:13:29.284 --> 01:13:34.373
It was great talking to you and being on the show.

01:13:34.373 --> 01:13:37.298
Thanks a lot All right, great Thank you Talk to you soon.

01:13:37.298 --> 01:13:37.840
Bye, take care.

01:13:38.625 --> 01:13:45.737
Thank you, chris, for your time for another episode of In the Dynamics Corner Chair, and thank you to our guests for participating.

01:13:46.016 --> 01:13:47.560
Thank you, brad, for your time.

01:13:47.560 --> 01:13:50.944
It is a wonderful episode of Dynamics Corner Chair.

01:13:50.944 --> 01:13:54.512
I would also like to thank our guests for joining us.

01:13:54.512 --> 01:13:57.546
Thank you for all of our listeners tuning in as well.

01:13:57.546 --> 01:14:12.127
You can find Brad at developerlifecom, that is D-V-L-P-R-L-I-F-Ecom, and you can interact with them via Twitter D-V-L-P-R-L-I-F-E.

01:14:12.127 --> 01:14:25.453
You can also find me at matalinoio, m-a-t-a-l-i-n-oi-o, and my Twitter handle is Mattelino 16.

01:14:25.453 --> 01:14:29.109
And see, you can see those links down below in their show notes.

01:14:29.109 --> 01:14:30.472
Again, thank you everyone.

01:14:30.472 --> 01:14:32.016
Thank you and take care.