Episode 439: AI in Business Central: Bridging the Gap Between Developers and Functional Consultants

WEBVTT

00:00:01.360 --> 00:00:04.959
Welcome everyone to another episode of Dynamics Corner.

00:00:05.759 --> 00:00:08.880
What's subscription and what's AI?

00:00:09.039 --> 00:00:10.720
I'm your co-host, Chris.

00:00:10.960 --> 00:00:11.679
And this is Brad.

00:00:11.759 --> 00:00:14.560
This episode was recorded on December 9th, 2025.

00:00:14.720 --> 00:00:16.239
Chris, Chris, Chris.

00:00:17.120 --> 00:00:18.399
What is AI?

00:00:18.960 --> 00:00:19.760
I don't know.

00:00:20.239 --> 00:00:22.879
I don't think I can go three minutes without thinking about AI.

00:00:23.199 --> 00:00:31.359
But in this episode, we had the opportunity to talk about AI and development and the future of development, along with the subscription building model within Business Central.

00:00:31.440 --> 00:00:33.039
With us today, I had the opportunity to speak with a lot.

00:00:54.560 --> 00:00:55.200
Hi, hi.

00:00:55.439 --> 00:00:56.640
What about yourself?

00:00:57.280 --> 00:00:58.159
Doing very well.

00:00:58.320 --> 00:00:58.960
Doing very well.

00:00:59.039 --> 00:01:00.960
I've been looking forward to speaking with you.

00:01:01.359 --> 00:01:03.359
You know, it's interesting.

00:01:03.600 --> 00:01:09.200
I just wrote a blog article about an AI vibe coding experience.

00:01:09.359 --> 00:01:11.519
Experiment that I did over the weekend.

00:01:12.480 --> 00:01:13.519
I saw that post.

00:01:14.159 --> 00:01:14.799
This morning.

00:01:15.359 --> 00:01:16.000
Yes, yes.

00:01:16.159 --> 00:01:17.920
I put it out there this morning.

00:01:18.400 --> 00:01:20.000
I have Raspberry Pi.

00:01:20.079 --> 00:01:22.239
I use Pi Hole for advertising.

00:01:22.400 --> 00:01:24.079
Not ad for ad blocking, excuse me.

00:01:24.159 --> 00:01:25.599
Jeez, I'm all messed up this morning.

00:01:25.840 --> 00:01:29.040
For ad blocking, I use Pi Hole running on a Raspberry Pi.

00:01:29.120 --> 00:01:35.439
And then Sunday morning, I realized that Pi Hole has an API.

00:01:36.480 --> 00:01:42.640
And I have a little 1.3 inch OLED display that I purchased for my Raspberry Pi.

00:01:43.359 --> 00:01:44.000
For another one.

00:01:44.079 --> 00:01:46.400
I have multiple Raspberry Pis, not the Pi that's running the Pi hole.

00:01:46.480 --> 00:01:49.760
I put it on, I put the OLED display on the Raspberry Pi.

00:01:50.400 --> 00:02:00.719
And then I said, okay, I'm going to see if I can vibe code without writing one line of code, something that will pull the API.

00:02:01.760 --> 00:02:11.120
Using the API, pull the statistics from the Raspberry Ui running Pi hole and display it on the Raspberry Pi that has the OLED display.

00:02:11.919 --> 00:02:14.240
I've never programmed in Python before.

00:02:14.400 --> 00:02:21.039
Thankfully, with knowing development, I understand enough to um read code.

00:02:21.199 --> 00:02:25.360
But I said, I'm going to go through this experience without writing one line of code.

00:02:26.000 --> 00:02:27.919
And it did it.

00:02:28.319 --> 00:02:29.120
Success?

00:02:29.360 --> 00:02:30.080
Success.

00:02:31.520 --> 00:02:37.759
What blew me away was I I I said, um, we need to, here's an API.

00:02:38.000 --> 00:02:40.960
Here's the endpoint, here's the structure of what it looks like.

00:02:41.199 --> 00:02:48.560
And then, you know, here's you know the structure of the API, here's the API endpoint.

00:02:48.879 --> 00:02:54.960
Um, and then here's the response because I started in the API documentation, and I need to pull out this.

00:02:55.439 --> 00:03:15.439
So just giving it that information and telling it what I wanted to do with some prompts, it went through the whole thing of connecting through the API, getting a token, put in code to refresh the token if it needed to, then display information onto this little OLED display.

00:03:15.680 --> 00:03:16.960
It created documentation.

00:03:17.039 --> 00:03:18.639
Now, this OLED display had buttons.

00:03:18.800 --> 00:03:26.639
It even suggested do you want uh to make one of the buttons be an exit from exiting the application?

00:03:26.960 --> 00:03:32.400
I was floored because it knew, and again, this little OLED displays is not like displaying on a monitor.

00:03:32.479 --> 00:03:35.520
You have to code to display the information.

00:03:35.680 --> 00:03:43.199
It's not just you know displaying something on the screen, it's uh display that you have to display the programming, and then it knew to program the buttons.

00:03:44.319 --> 00:03:44.960
Wow.

00:03:45.360 --> 00:03:48.000
I was and you didn't write one line of code.

00:03:48.240 --> 00:03:50.639
I didn't write one line of code, completely prompted.

00:03:50.800 --> 00:03:52.240
And and again, I did this in my house.

00:03:52.319 --> 00:03:55.120
I wasn't on anyone's you know system and we're not doing anything crazy.

00:03:55.199 --> 00:03:57.280
I have you know disposable pies, I'm working on it.

00:03:57.520 --> 00:03:59.280
You know what the best thing about it?

00:03:59.680 --> 00:04:03.520
Yep, what it took one hour to complete.

00:04:04.560 --> 00:04:06.960
Start to finish with documentation.

00:04:07.840 --> 00:04:13.759
It will pull the API so I don't have to open up the pie hole dashboard to see the statistics again.

00:04:13.919 --> 00:04:15.360
Do I look at that stuff that often?

00:04:15.520 --> 00:04:17.439
No, because I just runs.

00:04:17.519 --> 00:04:20.399
But I figured I just have a little vibe coding fun experience.

00:04:20.639 --> 00:04:24.240
And during that time, I cleaned my smoker.

00:04:25.759 --> 00:04:27.759
Oh, your barbecue smoker?

00:04:27.920 --> 00:04:28.319
Yes.

00:04:28.639 --> 00:04:31.439
My smoker, my smoker grill, excuse me.

00:04:31.600 --> 00:04:36.319
Yes, my smoker grill, I cleaned during this process and I was done.

00:04:36.480 --> 00:04:40.319
I started at 1500, I was done at 1600, including cleaning my grill.

00:04:40.560 --> 00:04:41.920
That's incredible, man.

00:04:44.160 --> 00:04:46.000
I was floored.

00:04:46.319 --> 00:04:53.199
And with that, before we get into talking about some of this and a little bit more during today's conversation, can you tell us a little bit about yourself?

00:04:54.399 --> 00:05:00.079
Yeah, so um I would say I'm I'm I started with NAV like in 2008.

00:05:00.240 --> 00:05:01.439
That's quite a few years.

00:05:02.240 --> 00:05:07.199
Oh no, and currently, yeah, we're all on the plane with the business central.

00:05:07.839 --> 00:05:15.759
So I'm I'm I'm working in a German company named IT Hammer IT Consulting uh in a product development basically.

00:05:17.040 --> 00:05:26.319
And you could say I have um yeah more contacts with Microsoft directly than I used to recently.

00:05:26.879 --> 00:05:30.240
I'm contributing more to code, that's how I would put it.

00:05:30.800 --> 00:05:37.199
The other way, I mean technically or let's say it other ways, I'm just uh technical dude, mostly.

00:05:39.279 --> 00:05:40.000
No, that's good.

00:05:40.160 --> 00:05:40.879
Technical dude.

00:05:40.959 --> 00:05:41.600
I like that.

00:05:43.040 --> 00:05:44.000
Technical dude.

00:05:44.160 --> 00:05:46.399
Um no, but you've done some uh interesting things.

00:05:46.560 --> 00:05:48.079
Wanted to talk with you about one.

00:05:48.399 --> 00:05:52.000
Um what is your take on AI and development with Business Central?

00:05:53.360 --> 00:06:02.079
Um I think I I feel like probably like many people uh that it's picking up I would say slowly, still slowly.

00:06:02.560 --> 00:06:06.800
I think some of us are experimenting more than the others, that's for sure.

00:06:07.600 --> 00:06:17.680
I kinda like it how the future feels like it will look like but I think it was here at the beginning somehow, I would say.

00:06:17.839 --> 00:06:22.800
I mean we have seen um you know enormous I would say advance in recent months.

00:06:26.160 --> 00:06:32.720
So you can yeah, yeah, so you get something really usable at this point of time.

00:06:32.879 --> 00:06:42.160
However, I'm not the guy that's like uh or so far my experience was like that that uh whatever I got, I had to fiddle a bit.

00:06:42.319 --> 00:06:46.560
So it was never a complete story spit out of the AI.

00:06:46.720 --> 00:06:52.160
But basically, um I think that's something that we should count on in the future, generally speaking.

00:06:53.040 --> 00:06:56.160
I I think I think so too, and I think you hit some points.

00:06:56.240 --> 00:07:03.839
I think I had an experience I talked about at the introduction to this with Python, which is a more popular language, there's more information out there.

00:07:04.079 --> 00:07:07.839
And just throw some questions out there for discussion based upon your context.

00:07:07.920 --> 00:07:16.800
And I've been also talking with a lot of uh individuals within the business central community space, or ever you want to talk about about AI and development.

00:07:17.120 --> 00:07:24.399
And I I've been speaking with not just technical dudes like us, I've been speaking with functional consultants as well.

00:07:25.040 --> 00:07:33.519
Do you think there's a difference in adoption between using AI when you're a developer or a functional consultant using AI for development?

00:07:33.680 --> 00:07:43.279
Because and the reason why I positioned the question, I've been speaking with a lot of functional consultants who've been dabbling with AI development now.

00:07:43.439 --> 00:07:52.720
And as they had mentioned, the recent models working with you know, everyone started using Claude uh I think Sonic 4.5, they've had some great results.

00:07:52.800 --> 00:07:57.199
I've been using um Codex 5.0 lately.

00:07:57.279 --> 00:08:02.959
Uh 5.1, I didn't have too much luck with for just I didn't like the way that it was prompt and interacting pack with me.

00:08:03.040 --> 00:08:04.240
But I've been getting better results.

00:08:04.319 --> 00:08:06.160
So it is getting better with AL.

00:08:06.800 --> 00:08:23.759
Now, I've been speaking with both developers and functional consultants, and in the conversations I've had, it seems a lot more functional consultants, because they understand the application, are doing development with AI for Business Central.

00:08:24.720 --> 00:08:26.720
Creating some small applications and PTs.

00:08:29.680 --> 00:08:35.600
Yeah, so that's an interesting, interesting yeah, developing story, right?

00:08:35.840 --> 00:08:41.120
So I I I mean I I I also see it happening, right?

00:08:41.200 --> 00:08:44.480
Um I wouldn't say it's really that prominent.

00:08:44.559 --> 00:08:47.919
I don't know at least in in the surf time I'm moving around.

00:08:48.559 --> 00:08:54.000
But yeah, um that can I mean that will happen for sure to some extent.

00:08:54.399 --> 00:09:00.720
However, I I see that I think that I mean both sides should adopt it too.

00:09:00.799 --> 00:09:07.039
I but I think the usage or the way how the the the functional how to use it is different currently.

00:09:07.440 --> 00:09:10.320
And I think it's probably going to stay that way.

00:09:10.639 --> 00:09:16.399
I mean it's great if if some if they can develop some something on their own, so to say.

00:09:17.440 --> 00:09:22.080
But for the moment I don't see it, at least in my circle, happening in in masses, so to say.

00:09:22.399 --> 00:09:23.200
No, I I understand.

00:09:23.360 --> 00:09:25.600
I don't think it's in masses anywhere.

00:09:25.840 --> 00:09:28.960
Uh as well as here's what kind though, like how though, Brad?

00:09:29.039 --> 00:09:32.000
Like, for example, you know, what would be their use case?

00:09:32.159 --> 00:09:38.799
You know, are they just building a table and a page or are they creating a full-on stack?

00:09:39.120 --> 00:09:43.200
Because it it's um about both.

00:09:43.360 --> 00:09:49.759
Um and I think there's some challenges now with even because I've been working with business central development as well, too.

00:09:49.840 --> 00:09:58.320
And we can and this is why I wanted to uh talk with you today about and then we also have the whole just to preface it, I have a million subscription billing questions for you too.

00:09:58.480 --> 00:10:04.799
But uh uh the whole topic, you know, we we were speaking before about AI and development.

00:10:04.960 --> 00:10:09.600
I I think it does depending what you're building, and I also think it depends how you prompt it and what you understand.

00:10:09.679 --> 00:10:13.519
I'm not going to talk about some of the things that they shared with me because I don't know if anybody wants anything shared.

00:10:13.600 --> 00:10:16.879
Uh, but they were more than a little bit basic tables.

00:10:16.960 --> 00:10:19.200
The basic tables and pages, I think it has down pretty good.

00:10:19.279 --> 00:10:24.879
They had some functionality uh in them, and I was impressed with some of the functionality uh as well.

00:10:25.120 --> 00:10:33.840
And it's it makes me wonder um business central is a framework and AI has to know the framework to develop the code.

00:10:33.919 --> 00:10:36.639
Whereas if you do something like I did, you're starting from scratch.

00:10:36.720 --> 00:10:39.519
It's like you're you're basically creating a framework with the language.

00:10:39.679 --> 00:10:46.559
Where AI, I think, with something like business central in the AL language, it's a little more challenging for the AI, right?

00:10:46.879 --> 00:10:52.240
Because you have a predefined framework that you need to develop within for functionality.

00:10:52.399 --> 00:10:58.399
So if we want to uh do bulk posting of documents, for example.

00:10:58.720 --> 00:11:01.600
Um, you know, Steve Endo did a vibe coding session.

00:11:01.679 --> 00:11:02.399
I think he did that.

00:11:02.480 --> 00:11:04.480
Uh he did some stuff with Business Central.

00:11:04.559 --> 00:11:10.000
It has to understand the application in the context of the comp of the application for it to develop it.

00:11:10.159 --> 00:11:15.679
Uh so but but the concept is not too far too far different than what you did with the pie hall, right?

00:11:15.759 --> 00:11:26.399
You have you have very little knowledge of the development uh language, and you're able to build a full working solution for what you're trying to accomplish.

00:11:26.639 --> 00:11:26.879
Correct.

00:11:27.120 --> 00:11:39.759
I'm assuming they're gonna have the same approach with functional consultants who understands the application, but not so much the development coding language, and they're yeah, they could build a full stacks, a full solution.

00:11:40.240 --> 00:11:44.159
I think even I think you need the development for some of the more complicated stuff.

00:11:44.399 --> 00:12:02.159
But I think I think it shifts where development you would also need it, it it almost proves to me that for development, and I've always felt this for development, you should have a good understanding of the application so you can develop better solutions and know if you need to even develop.

00:12:02.320 --> 00:12:08.399
Uh, because now with all the features and functionality within the application, sometimes you don't even need to make a uh modification or enhancement.

00:12:08.720 --> 00:12:14.080
But it it comes up with the importance of understanding the application.

00:12:14.159 --> 00:12:29.279
Whereas I think you know, a developer wants to type code, and I think a functional consultant doesn't know how to, so they're almost limited to okay, well, how can I talk with the AI agent uh to create the application?

00:12:29.600 --> 00:12:30.720
So I think.

00:12:32.480 --> 00:12:37.759
Yeah, so I I don't know if you have attended any of the you know Viecko, probably.

00:12:38.320 --> 00:12:38.879
Yes.

00:12:39.200 --> 00:12:54.559
I mean he has interesting takes on on that topic, and I kinda can identify with some like yeah, so the consultants or function consultants may have even more insights into how the app works, so they might even in some instances produce better code, right?

00:12:54.720 --> 00:12:55.600
By using AI.

00:12:56.000 --> 00:13:09.840
Perhaps uh but actually uh th those developers that have future are the ones that currently have experience and can basically um utilize AI properly, so to say.

00:13:10.080 --> 00:13:16.960
Where uh whereas I would probably compare um functional consultants with junior developer, I guess.

00:13:18.639 --> 00:13:28.799
So I think I think there are some challenges that are yet to be overcame overcome.

00:13:33.360 --> 00:13:37.120
They will definitely produce something, but for the moment I don't see it happening.

00:13:37.200 --> 00:13:40.080
Actually, I I think that penetration has to happen in development for a system.

00:13:40.480 --> 00:13:42.960
That's how I feel like okay.

00:13:44.240 --> 00:13:48.720
And uh I've seen it create some good documentation and such as well.

00:13:48.960 --> 00:13:57.759
And you know, all those developers are technical dudes like us, documentation is usually the last thing that somebody wants to do.

00:13:58.960 --> 00:14:07.919
And also, I think you really need to understand the workflow of what you're doing and then be able to do small prompts, right?

00:14:08.000 --> 00:14:15.919
It's very difficult to say you can do it, uh, and I've gone through some exercise of okay, create me something that does this, this, this, and this.

00:14:16.080 --> 00:14:35.360
But it's almost better to start with the prompting of here's sort of a background, and then exactly yeah, step one is to do this, uh, and step two is to do this, and step three is to do this, so it's like smaller steps instead of expecting it to be um yeah, actually, uh your good you I mean, good point.

00:14:35.440 --> 00:14:44.320
So that's where I expect actually AI to shine for functional consultants in the first step at least, like uh writing stuff down.

00:14:44.639 --> 00:14:46.960
And I think AI is really excellent at that.

00:14:47.039 --> 00:14:56.960
I mean, well, yeah, I mean as a function consultant, a lot of the things that they do is you know build use cases, document it with you know a technical design.

00:14:57.600 --> 00:15:00.399
Um, you know, so they have a proper structure already.

00:15:00.480 --> 00:15:14.639
So if you take those proper structure from a function consultant, which they do often with a business case or business process uh in mind, I'm sure they can walk through those steps and then be able to build a solution.

00:15:14.960 --> 00:15:30.080
So they may be a little bit slower in in terms of like uh understanding and and fully grasping that, but if but if they understand the business case, business use, uh I'm sure they can uh you know go through the whole thing and vibe code it.

00:15:30.559 --> 00:15:31.440
Yeah, yeah, yeah.

00:15:31.679 --> 00:15:40.480
I mean, I would definitely support and uh so to say the other side to to try it out and then let's see what the result is.

00:15:40.879 --> 00:15:46.159
Yeah, no, it's uh it's it's an interesting it's an interesting world that we're in.

00:15:46.320 --> 00:15:56.320
Uh you know, it seems like you can't go three minutes without hearing something about AI somewhere in the world, unless you have all external communication shut off.

00:15:57.039 --> 00:16:04.080
But it's it's yeah, I've been talking a lot more because again, it's interesting uh to me to see what you can do with AL.

00:16:04.639 --> 00:16:08.639
Is it is it do you think now is it blending the role?

00:16:08.879 --> 00:16:11.039
Because back then, in NAB days, right?

00:16:11.200 --> 00:16:17.200
You have a functional consultant, they know the application, and then you hand it off to a developer and then they work together.

00:16:17.440 --> 00:16:26.480
Do you feel like uh uh new newer or even you know uh people in this space for a long time, do you think their role is starting to blend where they could do both?

00:16:26.720 --> 00:16:30.799
Maybe complex ones goes to you know an actual developer.

00:16:31.360 --> 00:16:37.440
Um I I I cannot tell for sure, uh, but I feel like AI can bring us together somehow.

00:16:37.679 --> 00:16:47.200
That's how I feel like because currently I I I feel like there is a lot of um like often those two sides don't understand each other very well, generally speaking.

00:16:47.360 --> 00:16:51.679
And I think I mean let's talk about the normal process.

00:16:51.759 --> 00:17:01.200
There is a feature that should be developed, and uh some functional consultant tries to, you know, has a lot of thoughts and have it in the head, try to put it on the paper, uh in in letters.

00:17:01.919 --> 00:17:14.640
And I mean, although he might have an idea what is actually should be built, I mean the developer might have no clue whatsoever by just looking up the thoughts that the functional consultant has put in some task or whatever.

00:17:14.880 --> 00:17:30.160
And when I see what AI can do with that, which is like a pile of thoughts of functional consultants, which has you know uh a lot of experience, I I think it can bring you know those words much closer together, generally speaking.

00:17:30.799 --> 00:17:41.680
Transferring thoughts to to to getting something faster, I think uh you hit it perfectly, um, in my opinion.

00:17:41.839 --> 00:17:55.519
I think that it is going to force developers to be more functional and functional to be more development oriented, in turn doing exactly what you said, bringing everyone together.

00:17:55.680 --> 00:18:04.960
I think it's going to cross those roles because I think some of the smaller development tasks are no longer going to be necessary for coding.

00:18:05.200 --> 00:18:14.720
It's going to be necessary to be able to understand the application and how to do it because it it's really pretty good now with adding a feel to a page.

00:18:14.880 --> 00:18:28.079
It's really good at going through and updating tooltips, it's really good at doing a lot of those what I call minor things that are nuisances in a sense for someone to do in development, even creating an API page, right?

00:18:28.160 --> 00:18:30.640
You can say, here's the table, creating an API page for this.

00:18:30.720 --> 00:18:33.759
And I've done that recently for several of those.

00:18:34.000 --> 00:18:36.480
And it does a really good job of that.

00:18:36.640 --> 00:18:41.759
So, from a point of view of the developer, it's going to cut out a lot of that.

00:18:41.839 --> 00:18:46.160
So then you're going to have to have some of understanding the application and how to prompt it to do that.

00:18:46.319 --> 00:18:48.960
And then I think from a function consultant, it's going to be the same way.

00:18:49.039 --> 00:18:56.799
How do you communicate this to an AI or a developer to be able to instruct them on what to do in the detail that you need to do it?

00:18:56.880 --> 00:19:02.720
So your point of bringing everybody together, it's going to bring everyone together to where I think you're going to have a lot of crossing.

00:19:02.880 --> 00:19:07.920
Uh, and it's going to be important to have a crossing, and it's um the rules will change.

00:19:08.640 --> 00:19:09.920
I certainly hope for that.

00:19:10.000 --> 00:19:19.440
Because as a developer, I see that there are developers lacking functional knowledge, and and I see that AI could jump in basically.

00:19:19.920 --> 00:19:20.559
That's good.

00:19:20.799 --> 00:19:23.599
Have you done what what type of experimenting have you done with it?

00:19:24.000 --> 00:19:24.880
Have you done much?

00:19:25.680 --> 00:19:32.799
Well, I was thinking about what can I share in this podcast, and I realized that I basically nowadays I use it like every day.

00:19:33.119 --> 00:19:41.440
It doesn't, I mean, it it's it's it has become a part of my uh you know uh uh routine, daily routine actually.

00:19:41.839 --> 00:19:48.319
I mean it yeah, just I mean, like really the stupid stuff stuff that I don't know, I just don't Google any longer almost.

00:19:50.720 --> 00:19:51.200
Yeah.

00:19:51.519 --> 00:19:59.519
And that's why we're going to have ads and AI responses, because I had a conversation with someone this morning about that same thing as who uses search engines anymore?

00:20:00.160 --> 00:20:00.960
just ask AI.

00:20:01.759 --> 00:20:02.240
Exactly.

00:20:02.720 --> 00:20:06.160
That that's what happened to me at least in I mean like in in last month.

00:20:06.559 --> 00:20:08.160
And in development also, right?

00:20:08.240 --> 00:20:17.519
Uh I I'm even trying to push myself to explore more because I think I'm I'm not in the let's say leading the pack.

00:20:17.680 --> 00:20:24.319
I'm just learning so to say and I learn every day about how to put it to the purpose.

00:20:27.200 --> 00:20:33.759
And from the scope of AAL do you do see it facilitates any of your development now?

00:20:34.319 --> 00:20:45.519
Yeah yeah yeah so I mean like autocomplete is like there's I I would probably cry tomorrow if it would go away for whatever reason.

00:20:45.839 --> 00:20:54.079
And yeah developments I think in the new future have more chances to utilize it better rather than maintaining the base up or something like that.

00:20:55.440 --> 00:21:06.000
So the context is important I would say so I'm still switching between do I put the effort to put the context to AI or I do it by myself.

00:21:06.960 --> 00:21:22.400
So that that's still a challenge I would say it is it is because it's it's tough and that's where I'm saying is it you know the development for using AI versus a functional consultant use an A because the developer is going to do similar to what you had said.

00:21:22.720 --> 00:21:34.799
Is it more difficult or more time consuming for me to type the context or to type the fields in the page and and put it together and then have to review it and do it.

00:21:34.960 --> 00:21:38.880
So it's it's it's an interesting world that we're in and it's moving fast.

00:21:39.039 --> 00:21:42.160
And do I want to fast forward a couple years?

00:21:42.400 --> 00:21:42.720
No.

00:21:43.039 --> 00:21:55.279
But I almost would like to in a sense just to see what where we all are and uh what space we're in because uh I've been having a lot of fun with it and getting a lot of practical use out of it as well.

00:21:55.359 --> 00:22:50.319
And I'm almost uh I don't want to say afraid I'm almost uh curious curiously uh um yeah awaiting to see where we end up we should touch up on that also like I I also feel that there is kind of uh uh fear for I don't know from certain um population but I don't fear feel it to be honest I'm I'm also like you like hoping to see what comes next right so I don't have a fear that it will replace me I don't know I I cannot explain it I just feel like let's do it and try to put it to use no absolutely well I like I said I think I do believe that it won't replace like AI is not going to replace people I think uh it will have new opportunities but I think people using AI will replace people because I think in some cases you will become a little bit more efficient and be able to do uh a better job to for lack of better terms.

00:22:50.480 --> 00:22:58.400
Again everything has to be reviewed I'm not saying it's going to hit everything 100% of the time and I'm not one of those skeptics that looks for everything that AI faults don't get me wrong.

00:22:58.640 --> 00:23:02.319
One thing I learned in coding with AI is I commit every change.

00:23:02.480 --> 00:23:02.799
Why?

00:23:02.960 --> 00:23:19.039
Because I I need to roll back because it will go off um I I was vibe coding something else just as an experiment with uh some of the tools that I use and it went totally out into left field and started modifying things totally outside of the context of what I wanted it to modify.

00:23:19.279 --> 00:23:22.720
So thankfully I was able to roll back to you know a previous commit.

00:23:22.799 --> 00:23:33.519
So that's uh I like I said I don't want to say it's 100% perfect all the time but the neither are people so uh we just have to to learn to accept it.

00:23:33.680 --> 00:26:26.000
So uh you do quite a bit it's it's I have so many things I want to talk with you about uh the AI topic again it's it's it's interesting to me but the other part is um uh recently well it seems again when you get to my age a day a year seems like you know they all seem like yesterday um subscription billing was added to business central recently a couple versions ago I think a couple waves ago right two or three waves ago October last year yeah yeah yeah two waves ago right because we had yeah this is October April third wave yeah three waves ago so uh about a year ago it was added and uh rumor has it you know a little bit about subscription building yeah so that's true the rumors are true uh so the the the C Hammer was the company that um uh they say licensed uh this app for Microsoft because Microsoft at some point of time figured they have um um you know something that is kind of missing and I think they basically explored a bit uh what's there on the market so I don't know the the details but uh at the end it ended up uh choosing uh the solution that was belonging to the product family called Dice actually and I was the one that was kind of in charge of transferring this IP from CHAMER to Microsoft and along the way um there were some technical uh stuff that had to be improved because I mean you're taking over the the the the partner IP partner code which might not be hundred percent aligned with with uh coding side uh standards and whatever for Microsoft so I was kind of um yeah supporting that path of transferring the IP to Microsoft so I was not the the one that developed the whole stuff uh I did I was involved with certain parts to some extent uh but basically yeah that's this full story kind of so so with that that it it seems that there's been a few portions of the application that they have um licensed from other parties um yep and it's you know some of that stuff is not you know it's not a secret so you know subscription billing was one of them that again was licensed from an organization you work with I have some questions on that uh it and I don't if uh whatever you can talk about I'm not certain what you can and can't talk about but so you said you worked in the process to transition it from your organization over to Microsoft uh so that it was within the base application.

00:26:26.319 --> 00:26:34.960
Do you do the coding in that process or do you do you work with the engineers or the technical dudes at Microsoft and then they enhance the code.

00:26:35.279 --> 00:26:37.839
How does that relationship in that process work?

00:26:39.200 --> 00:28:02.559
Yeah so uh yeah i it has multiple aspects uh or uh so you do the code along the way that's for sure because there were simply stuff that were were not aligned and uh when Microsoft acquires some third party solution they also have something called work for hire for a while meaning that they count on the fact that you are the one that the company they have purchased from is the most familiar with with actually what's in there and can basically uh they are the the ones that can do the changes the fastest uh compared to them um so I would say initially that was done mostly by CHAMER most of the changes uh nowadays it's starting to shift to Microsoft and we're hoping to kinda um um put it in in uh or let's say um bring it to that state that Microsoft can maintain it by themselves completely we're not there yet so we are still uh involved in uh delivering fixes and some futures however the the the amount of work we are doing right now is getting lower and I guess I don't know but I guess that's probably something they they normally do with other letters also.

00:28:03.279 --> 00:29:08.880
Yeah I I assume it takes makes sense and I understand what you're saying for your team to work with the application for a certain period of time while it's being brought into the application because you understand the application understand how the application works and then that gives the internal team the opportunity to learn the application and understand how it works so that then they can maintain it and keep it within the realm of their workflow and their future for uh future plans uh for the application as well um how long did that process take to transition it from your your code base in a sense into Microsoft is that something that's lengthy or is that something that gets done rather quickly and again I'm not talking about the whole I'm talking about what's the point that you already knew you know that it was already known that the application was going to move the the whole other you know process I don't have any interest in I'm just interested in knowing the process from the technical aspect of it.

00:29:09.279 --> 00:30:24.079
Yeah so I think I think uh the talks started somewhere around 2023 when the Microsoft's uh end of 2023 when they started looking around uh we were passing some procedures that they have when they are acquiring third party uh IP and that happened somewhere in March April 2024 and when they said okay we are buying it that happened somewhere in June July I don't know something like that and then in October it went into release uh but the work is I mean I wouldn't I mean the question is where you drew the draw the line when do you say it has been uh transferred so if I would I would have I would have to answer that question I would say probably April this year it came to a form when it's kind of uh aligned with a lot of stuff Microsoft is doing like demodata and everything but but it was released in the October last year and then it's we had some um additional work to do in order to align it more I see that's not too that's not too long that sounds pretty fast.

00:30:24.559 --> 00:30:43.440
It's not I thought it was a I honestly thought the process would be uh a little more lengthy or it'd be a lengthier process to well transition but you're saying yeah moving fast that's for sure I laugh because you say they're going fast.

00:30:43.839 --> 00:30:44.880
They are going fast.

00:30:44.960 --> 00:30:50.640
It seems like every day I learn something new about the application that a feature that was just added maybe overnight or something.

00:30:50.720 --> 00:30:54.880
I I say that in jest but it it the application is evolving so quickly.

00:30:55.279 --> 00:31:04.880
But what's obvious they try to to I mean they they try to identify the gaps and to fill them in that's how I interpret it right now.

00:31:09.200 --> 00:31:55.680
So um so with the subscription billing application as well uh so is Microsoft handling all the support or are they still sending some of the support over to you uh they're taking it on their own uh they are they are taking some of them to on their own and some of them uh are passed to us still uh I mean that's that's probably obvious when you look at the uh repo it's now in the on the BC apps repo so that can be checked uh and I think I feel like it's still uh I wouldn't say a lot but quite a few stuff are in in the pipeline so to say and I expect it to reduce some in this year and I and they are still I mean they are also uh having their own support channels and sometimes they resolved it by themselves and sometimes we do.

00:31:56.240 --> 00:32:32.799
Yeah but I'd say when I when it comes to something which so there are also circle of knowledge is kind of stuff you know not only Microsoft in all companies they have the the stuff that they know better than the others and I would say the subscription billing is not something that's really nowadays widespread for example across the Microsoft so we still get uh uh fix some stuff at the same and I'm I'm not sure when this will end we hope that this will happen I don't know end of this year or next year um but we're still working together with Microsoft.

00:32:33.119 --> 00:33:19.680
No it's good that they're working together uh a few more questions on this uh so what about the existing customers that you had did you have to do a migration for them from yeah yeah yeah yeah so I don't know if you have followed up the story about the subscription billing but it wasn't extensible up until uh April in the first release in the the the very first release was not extensible I saw a lot of chatter about that because everybody likes to make changes we couldn't we couldn't migrate them uh like all of our customers not all but like I would I think most of them right now have received an information that uh we plan to switch them to the uh Microsoft subscription billing because it's also in their interest because currently they pay for our app still and yeah subscription billing for Microsoft is kind of free for them.

00:33:20.400 --> 00:33:52.559
We have invested um quite a few time in migration routines because the apps um that are now a part of Microsoft are actually not identical to what we had you know they have changed they have evolved um they might even have some other features which are not completely the same so we had to write the the the the code that does that with the hope that it should be an effortless migration and I can only say that some of our customers started this process as far as I know nobody is completely switched.

00:33:52.799 --> 00:35:29.920
We have of course the customers that are starting with Microsoft billing already but the migration wave is still about to start and be finished I guess in the next year 2026 that's the goal so to say that all of them have switched and and the problem is of course uh I mean the problem uh um the current state is that you know in this dependency Hammer has its own family of apps uh which is called DICE and it has uh roughly 20 apps and they're all entangled somehow right so imagine that we had to isolate those two apps which uh were called subscription billing and usage based billing to pull them out right in the middle of the dependency tree uh give it to Microsoft and now try to integrate all of the remaining eight in with uh what Microsoft has so it was quite a challenge so that's that sounds like a challenge yep but ongoing no no it's uh you get the I mean sometimes those slow changes are good I mean Microsoft itself when I work with the applications they do a good job of moving slowly in some areas to to to much much chat or sometimes to allow you to migrate some of those customers uh we're talking about the subscription billing and you you mentioned usage billing uh what is a quick overview of the subscription billing portion of it I think uh I jumped right into the questions yeah I should have started off with what it is and what you can do with it but uh there was a little assumption of me I mean that again I'm the technical guy so I I care more about that stuff but uh what is the subscription billing feature and what can you do with that subscription billing?

00:35:30.320 --> 00:39:47.599
It's basically uh a new module that enables to manage I hope any kind of subscription billing inside of Business Central it probably cannot cover every everything out of the box but that is the idea uh and uh that means it provides the new entities inside of business central like subscription header lines uh contracts uh and the framework for managing uh billing hopefully effortlessly I mean without effort and so Chammer has done it for quite a while uh and uh CHammer has focused on IT industry companies in general uh and uh quite a few of those customers were having like a huge amount of contracts and everything so mass data processing was kind of an imperative and when we come to the usage-based dealing that's a scenario where you have somebody like companion or Microsoft uh giving you the usage data on a vendor side right and you want to import it in your system and say okay based on what you have gave me like Microsoft and companion I'll build my customers so that's user-based data so if you you do not have to use it you can work uh without usage based billing data processing just by manually entering everything in the system but as I said CHAMR has a pool of these customers that uh you know have I know thousands of contracts or thousands of tier customers or even working with government and they have simply the need to to you know process thousands of lines so when we're talking about a subscription you're talking that if I have a monthly invoice for services or I have a monthly invoice for something it allows you to set it up in the system and then those subscription invoices would be created periodically at certain intervals correct yeah exactly I mean most normal period is monthly period like that's most widespread uh system so you basically set it up I mean uh mobile I don't know um TV cable whatever and then you set up uh these periods and monthly you can issue you have a worksheet that generates um uh uh invoices for I don't know how which you know how many customers you might have or customer uh contracts and that's the point yeah and then the usage based billing is the consumption so so you had mentioned like from Microsoft a companion so if you're dealing with other services so if it's a disk space you know that may be variable where you charge per uh you know gigabyte per megabyte per kilobyte whatever the you know whatever they're going to charge you at yeah and then you get that monthly based upon usage and then you could tie that into your own usage based system as well if you had another metric for for uh consuming usage as well yeah yeah yeah so you basically import it and based on that you uh create um uh images on sale side and you can also connect it with the purchase images that you get from companion Microsoft I like that that's um yeah so uh that's not the only I mean there are also third parties you probably know that right that also do similar jobs yes and to be honest some of them have their own strengths and uh I would say subscription beneath Microsoft has his own strength but the the I mean when you have something standard uh in in Microsoft uh business central it's kinda appealing to take it because you don't have to pay for it I guess absolutely it is appealing if um it's within the base product because of a couple of reasons one it's going to it continues to evolve with the base product much easier and if it doesn't do exactly what you need now that there's extensibility in it um you know as you'd mention at first it wasn't extensibility which a lot of people had some questions on but I also understand the delay on it as well uh sometimes I think some chatters just because it's easier to chat at just like saying AI is wrong instead of saying okay what what about the AI is right?

00:39:47.760 --> 00:39:52.079
Uh let's focus on the what is wrong of it just uh I think that's human nature.

00:39:52.239 --> 00:40:01.679
But I think it's a little bit easier because then you get additional features for you know additional Features and functions within the application.

00:40:01.760 --> 00:40:03.760
You have the migration path that's much easier.

00:40:04.320 --> 00:40:10.800
I mean, anyone who has an app, again, in the app source, they usually stick with the same process.

00:40:11.039 --> 00:40:14.000
But I can see benefits to both.

00:40:14.639 --> 00:40:15.280
But it is.

00:40:15.360 --> 00:40:23.679
Again, it's uh I tell everyone, no one will ever be the only one at anything because if somebody has a good idea, you bet that somebody else is going to try to do the same thing.

00:40:24.079 --> 00:40:25.280
Competition's good.

00:40:25.920 --> 00:40:26.320
It is.

00:40:26.480 --> 00:40:27.519
I think competition's good.

00:40:27.760 --> 00:40:28.960
Competition's important.

00:40:29.199 --> 00:40:32.400
And um, you know, not everything's for everybody.

00:40:32.559 --> 00:40:36.719
It's uh that's why they have many different types of motor vehicles that you can purchase.

00:40:36.880 --> 00:40:38.559
Uh there's something for everybody, right?

00:40:38.639 --> 00:40:41.599
They all have different features that appeal to to other people.

00:40:41.760 --> 00:40:43.760
So or other uh geez.

00:40:44.239 --> 00:40:46.639
I think everybody knows what I mean when I said that.

00:40:48.079 --> 00:40:49.840
It's my face and so no, that's good.

00:40:49.920 --> 00:40:50.559
That's interesting.

00:40:50.800 --> 00:40:52.480
So, what other great things have you been doing?

00:40:52.639 --> 00:40:53.440
You do quite a bit.

00:40:53.519 --> 00:40:59.840
It's very difficult to um yeah, you know, to to to hammer in on a number of things that you do.

00:41:00.079 --> 00:41:04.880
Um you had uh gone to AMIA recently as well, correct?

00:41:05.199 --> 00:41:05.840
Yep, yep.

00:41:05.920 --> 00:41:07.440
So I went to Posnan.

00:41:08.239 --> 00:41:16.559
Um I presented a session about um 15 AI features nowadays that are present in Business Central.

00:41:16.960 --> 00:41:30.159
So uh other than that, I I was recently uh doing something in regards to the German uh e-documents connector, not relevant for you guys from US.

00:41:30.800 --> 00:41:36.960
Yeah, we uh we still we still put stuff in the mail and we still have checks.

00:41:37.199 --> 00:41:45.360
I don't understand for the life of me why the United States still does that.

00:41:45.920 --> 00:41:50.400
I I I can't even think of a reason other than trying to make somebody somewhere makes money on it.

00:41:50.480 --> 00:41:58.880
That's all I have to tell you because checks if yes, somebody somewhere is making money on checks because I can't think of another reason for it.

00:41:59.199 --> 00:42:01.519
Although I can't tell you how many checks I write in a year.

00:42:01.599 --> 00:42:04.159
I think I have written one check in the past two years.

00:42:04.719 --> 00:42:16.880
Brad, there's one thing that uh I had to do actually recently where I had someone come out and and and service my pellet stove, and uh it's like and I was ready to you know take my iPhone and pay this guy.

00:42:17.039 --> 00:42:18.800
It's like no, we just take checks.

00:42:19.039 --> 00:42:20.320
Like, how about cash?

00:42:20.480 --> 00:42:22.480
Don't even take cash, check.

00:42:22.719 --> 00:42:23.840
I'm like, what?

00:42:24.639 --> 00:42:26.320
I don't have my checkbook.

00:42:26.639 --> 00:42:27.519
I don't know who does that.

00:42:27.599 --> 00:42:30.159
I receive more checks than I right.

00:42:30.719 --> 00:42:45.519
Thankfully, when I have service here, it's either cash in a case of corona, or um or it's uh like um you know, most technicians now will have a mobile device that has you know a touch on it that you can do.

00:42:45.679 --> 00:42:48.639
So we get we're getting more and more, but a lot of people still use checks.

00:42:48.800 --> 00:42:50.800
You said 15 features, 15 A.

00:42:51.119 --> 00:42:52.480
So what caught me on that session, right?

00:42:52.639 --> 00:42:55.280
This is why I wanted to go to this, and there's a reason why I'm gonna go to this.

00:42:55.519 --> 00:42:59.760
Is um can you give me a quick rundown of the 15 AI features in Business Central?

00:43:00.159 --> 00:43:01.199
Well, out of the head.

00:43:01.280 --> 00:43:03.760
So they're like um even the ones you remember.

00:43:03.840 --> 00:43:13.440
I I listen, I can't remember them all either, but there are those four built around uh items like um um the marketing text for start.

00:43:13.599 --> 00:43:18.239
I mean, before that there was uh like image recognition that's not that well famous one.

00:43:18.559 --> 00:43:30.079
Then uh there is you know item substitutes, uh you also have suggest sales lines, then there is um e-documents matching, bank reconciliation before that.

00:43:30.159 --> 00:43:52.719
You have the summary in the in the cards, then you have the chat, uh, analysis, analyze, and actually the ones that I uh for the ones that I like the most or I have highest hope for are the agents and not the sales uh agent, which is also pretty fine for some uh I would say business models.

00:43:52.960 --> 00:44:05.440
But I think the I really have high hopes of payables agent generally speaking, because I tried it and um for SMB, which the business central is meant for, I think it has a good perspective.

00:44:06.559 --> 00:44:15.920
So I just um before before preparing this session, I just threw you know the the some random invoice I had, and I was like, let's see whether it recognized anything.

00:44:16.000 --> 00:44:26.960
And I was like, wow, like you know, I I got something on an email which is a PDF, and I get it posted in in like without any data exchange definition or whatsoever.

00:44:27.679 --> 00:45:03.039
Yeah, I think I think you're right, the payables agent is maybe underrated in terms of usage because in many cases you deal with almost the same vendors every time, and so it's easier for it to learn of the type of invoices that you will receive uh via email, uh, versus you know, versus the sales agent, which is you can have a ton more random invoices or orders, uh order information, but the payables agent I think it's a great fit for a lot of organizations that I mean everybody handles with a vendor, right?

00:45:03.199 --> 00:45:05.039
So yeah, you're right.

00:45:05.119 --> 00:45:08.000
I it's a great call out on the payables agent.

00:45:08.320 --> 00:45:11.440
Yeah, it it's still not uh it's still in preview, however.

00:45:11.760 --> 00:45:16.719
They are trying to push it to the you know, red uh RTM.

00:45:16.800 --> 00:45:17.760
How would you say that?

00:45:17.920 --> 00:45:21.599
So basically to be publicly available, uh not in preview mode any longer.

00:45:21.679 --> 00:45:23.519
And I'm looking forward to.

00:45:23.920 --> 00:45:38.000
I mean, there are some I I think why they are trying to to I mean that's what they said, that why they are trying to uh put it in public as soon as possible because they're hoping for the feedback, what should be improved.

00:45:38.800 --> 00:45:39.360
Yeah.

00:45:39.840 --> 00:45:42.719
That is a key, and I say this to everybody.

00:45:42.800 --> 00:45:45.519
It's important to get something out there because you get the feedback.

00:45:45.599 --> 00:45:50.000
It's almost like if you write, if you tell somebody, okay, give me your ideas of what features and functionality.

00:45:50.159 --> 00:45:52.239
I could just picture the conversation because we could have it here.

00:45:52.400 --> 00:45:55.840
Give me some ideas for uh purchase and payables agent.

00:45:56.079 --> 00:45:57.679
And everybody would just be quiet.

00:46:02.079 --> 00:46:02.880
Why doesn't it do that?

00:46:02.960 --> 00:46:19.039
So it is good to get something out there, and then also you know what to invest your time in as well, because if if you don't have feedback for usage or features, you could delay or take time because you're doing something and you may have this big portion of it that you think extremely important, because everything's a good idea.

00:46:19.360 --> 00:46:23.599
And this is just for any development cycle, not just the purchase and payable agent I'm using as an example.

00:46:23.840 --> 00:46:30.559
You could spend weeks on a feature that nobody ever even uses, and then you may be missing a feature, you may be missing a feature that's extremely important.

00:46:30.639 --> 00:46:34.079
So that feedback um is important on there as well.

00:46:34.480 --> 00:46:53.840
The thing is, I was like uh before the these AI ages, so to say, I was wondering how to you know get a PDF from email process, and either you would you would reach out to Power Automate or or I mean there is also functionality that you can call from Outlook, not sure if you're aware of it.

00:46:54.239 --> 00:47:08.480
Uh it's it's uh so it's it's it's uh add-on for uh add-in for for Outlook so that you can also process PDF documents and put them in in inbound uh incoming documents and it worked, but I think this is another level.

00:47:08.559 --> 00:47:10.719
I really hope it will be another level.

00:47:11.039 --> 00:47:15.199
And it looks like it's it promises a lot, I would say.

00:47:16.000 --> 00:47:25.679
Yeah, I wonder I wonder if for all the people that have ever used uh power automate to do that will still will eventually switch and just use the power uh payables agent.

00:47:26.000 --> 00:47:27.119
Yeah, I don't know.

00:47:27.199 --> 00:47:27.920
We'll see.

00:47:28.079 --> 00:47:37.360
Yeah, I will see you know the other agents are also coming, so they might you know some new world of agents.

00:47:38.000 --> 00:47:39.840
Do you name your compile agent?

00:47:40.079 --> 00:47:40.559
Sorry?

00:47:40.800 --> 00:47:42.239
Do you name your agents?

00:47:42.719 --> 00:47:44.079
Do I name my agents?

00:47:44.239 --> 00:47:46.079
Like you my like personal name or what?

00:47:46.320 --> 00:47:48.480
No, no, when you're working with an agent, right?

00:47:48.639 --> 00:47:49.679
Do you name them?

00:47:50.000 --> 00:47:52.800
Like my no, the AI agents.

00:47:52.880 --> 00:47:54.719
When do you name them when they're doing work?

00:47:55.039 --> 00:47:56.800
Oh I started talking line.

00:47:57.119 --> 00:48:00.559
I I I have better conversations with my agents than I do with people sometimes.

00:48:00.800 --> 00:48:04.000
Yeah, they're if you tell them what's their name, they will remember it.

00:48:04.159 --> 00:48:05.199
I know that for sure.

00:48:05.360 --> 00:48:07.360
So I haven't told them their name.

00:48:07.440 --> 00:48:10.400
I just you give it you're giving them their name.

00:48:10.559 --> 00:48:15.679
The moment you give them their name, they be you know they become a little bit more personable, right?

00:48:15.920 --> 00:48:16.400
Right?

00:48:16.719 --> 00:48:17.679
I'm doing that.

00:48:17.840 --> 00:48:24.079
In my uh I'm going to have a good agent file, and I'm going to say your name is going forward.

00:48:24.639 --> 00:48:26.559
And it goes to the to the agent memory.

00:48:26.639 --> 00:48:30.880
So mine, for example, for the I I use like all bunch of them, I tried them all.

00:48:31.199 --> 00:48:36.159
But the GPT one, uh, the dog, my daughter give gave him the name, and it's cous crew.

00:48:36.719 --> 00:48:38.800
That's the current name of my agent.

00:48:39.679 --> 00:48:44.159
And he also responds like that, like I'm cous crew, and I'll deliver you the answer.

00:48:44.480 --> 00:48:45.519
So try it out.

00:48:47.519 --> 00:48:48.159
That's it.

00:48:48.320 --> 00:48:53.599
As soon as we're done with this, I'm going to set up and I'll have multiple agents depending upon how I feel.

00:48:53.920 --> 00:48:56.559
Give them who I want to talk with.

00:48:56.800 --> 00:49:02.079
Um lingering question I have, I just throw this out there for conversation.

00:49:02.159 --> 00:49:04.400
And I was thinking about it on my run the other day.

00:49:04.559 --> 00:49:06.320
Thankfully, I've been able to run again.

00:49:06.639 --> 00:49:17.840
And with all of these agents doing all of this work, what is that going to do to licensing?

00:49:18.880 --> 00:49:22.719
Because the agents are going to be able to do work of users.

00:49:23.440 --> 00:49:26.880
Licensing today is based on user subscriptions.

00:49:27.039 --> 00:49:30.079
I know you can pay by usage with the agents, right?

00:49:30.159 --> 00:49:37.519
That's how the whole the premise is going to be that um there's going to be a fee for the use of the agents.

00:49:38.079 --> 00:49:44.159
But I think there's going to be a big shift from user licenses to how this these agents are going to be licensed.

00:49:44.400 --> 00:49:49.760
So I'm I'm curious to see how that licensing model works out and how you charge for it.

00:49:50.000 --> 00:49:51.199
Again, I'm just throwing that out there.

00:49:51.280 --> 00:49:55.679
I'm not suggesting or asking anybody uh what their answer is.

00:49:55.760 --> 00:49:57.920
But what do you what are your thoughts on that?

00:49:58.800 --> 00:50:12.000
Well, I would I would simply, I mean, I would suggest anybody who wants to try it out, uh, because you know when you get a business central tenant, you get a small amount that you can use, like a couple of processes, and then you're done for agents.

00:50:12.159 --> 00:50:15.199
The agents are the only ones that are built right now by Microsoft.

00:50:15.440 --> 00:50:31.199
So I would just say, I mean, that would be my suggestion if you're not you want to try it out and to try to use it in real life, go with the pay as you go uh subscription, uh connect it to your environment, and you know, check out how much it consumes.

00:50:31.360 --> 00:50:33.440
So and put a budget on it.

00:50:34.159 --> 00:50:35.199
Yeah, yeah, yeah.

00:50:36.639 --> 00:50:46.239
The most important thing you can do is put a budget on it because I mean let's let's talk about as an example for payables agents.

00:50:46.559 --> 00:50:53.440
I don't feel like I mean it depends on the on the company size, of course, but like that's like a handful of people doing that.

00:50:53.920 --> 00:50:59.119
And um it also depends on the volume of the purchasing wage that you might get.

00:50:59.760 --> 00:51:09.519
But I think anything like double or three-figure sceneways shouldn't be that much pain uh cost-wise, and the people would be happy with the result and result, hopefully.

00:51:11.280 --> 00:51:14.079
I would say it's I mean that's it's it's that's all the new stuff this year.

00:51:14.239 --> 00:51:15.679
So uh, you know, the agents.

00:51:15.760 --> 00:51:18.239
Um Chris, you mentioned co-pilot agent.

00:51:18.719 --> 00:51:20.000
I think I heard you say.

00:51:20.480 --> 00:51:22.159
Yeah, co-pilot agent, right?

00:51:22.239 --> 00:51:34.400
So like you know, being able to you know add that as part of your uh you know business decision of creating sort of your own agent that interacts with Business Central.

00:51:34.639 --> 00:51:38.000
Um uh because I I think that's where it's going.

00:51:38.079 --> 00:51:41.519
I mean they're they're you know Microsoft's pushing that very, very hard.

00:51:41.760 --> 00:52:05.199
And I'm sure it's not a secret about the MCP servers, you know, and and and I know AJ has done this and I've I've dabbled it you know for quite some time is interacting with the MCP server for Business Central with Copilot, build a full solution in like five minutes, five, ten minutes, and then and then also calling email, you know.

00:52:05.280 --> 00:52:15.360
Uh you you had mentioned about interacting with Outlook and be able to do more than that is just a few prompts and connecting it and nothing else, you know.

00:52:15.599 --> 00:52:17.039
It's pretty straightforward.

00:52:17.199 --> 00:52:52.320
So the the ability for for for you to create an agent for a specific use case that's repeatable and then have it interact with all the different applications that you have, not just Business Central, um, but you can also create a record in Business Central and fully interact with it, and then at the same time connect it with the other Microsoft uh applications and beyond as a huge benefit for the SMB space that don't quite have you know the budget of enterprise level.

00:52:52.880 --> 00:53:00.000
So if you look at it from that perspective, it helps it helps it create a level playing field for for their growth.

00:53:01.599 --> 00:53:04.719
Yeah, I think however, I mean we're talking about the copilot studio in general, right?

00:53:04.880 --> 00:53:06.239
Yeah, copilot studio in general.

00:53:06.400 --> 00:53:16.719
Yeah, yeah, I think we're yet to see what the application will be because I I have a feeling, that's my feeling currently, that uh it's not that widespread yet.

00:53:17.360 --> 00:53:29.280
I mean, talking about the business central, people mostly stay inside the business central, and copilot studio means you building an agent which is attached to I don't know, website um um or some other channels.

00:53:30.239 --> 00:53:36.079
And I'm I'm curious to see, and I'm MCP is also is it in preview already or not?

00:53:36.159 --> 00:53:36.639
I'm not sure.

00:53:36.719 --> 00:53:38.000
I think it is preview, yeah.

00:53:38.559 --> 00:53:41.039
It is in preview and it's in 27.2, I believe.

00:53:41.199 --> 00:53:41.599
Yeah, exactly.

00:53:41.679 --> 00:53:42.400
Yeah, 27.2.

00:53:42.880 --> 00:53:46.000
Yeah, so 27.2 you can uh work with it.

00:53:46.320 --> 00:53:52.320
Yeah, so I think uh yeah, let's see next year what will happen.

00:53:52.719 --> 00:53:54.639
Because I'm interested to see use cases actually.

00:53:54.880 --> 00:53:55.920
Yeah, that's what I'm gonna say.

00:53:56.000 --> 00:53:56.880
It's use use case.

00:53:57.039 --> 00:54:04.000
The adoption is usually gonna be tough because you're trying to find where in your business would this fit, right?

00:54:04.320 --> 00:54:08.320
Uh and in using in using that and kind of a day-to-day.

00:54:08.480 --> 00:54:12.480
So adoption is gonna be a little bit interesting where people are gonna be using it for sure.

00:54:12.719 --> 00:54:16.079
Yeah, if we if we don't know, I am sure AJ will know.

00:54:17.039 --> 00:54:17.920
Yeah, yeah.

00:54:18.239 --> 00:54:30.239
I mean, even for you had mentioned about the uh computer use uh agent, where it looks at the screen of your computer and it will just read the context of your screen.

00:54:30.400 --> 00:54:36.880
So I think that's why it's important for for that use when you have tooltips on your business application.

00:54:36.960 --> 00:54:39.679
Uh so you no longer need a true API.

00:54:39.840 --> 00:54:47.519
That's what the computer use agent does, is that there's no API needed, it just looks at the context of what you have on your computer.

00:54:47.679 --> 00:54:56.639
So if you if you design an application in Business Central, you have very good tooltips, it's going to understand that context in the screen, interact interact with it.

00:54:57.119 --> 00:55:04.480
Do you know I remember when the modem, you know, when I could buy a 1200, 2400 bud modem, and that was a big thing, and I had CompuServe email.

00:55:04.800 --> 00:55:05.920
CompuServe.

00:55:06.159 --> 00:55:08.639
And I remember when the cell phone was created.

00:55:08.880 --> 00:55:11.519
I really want to go back to those times.

00:55:11.840 --> 00:55:15.039
I I think uh simple times.

00:55:15.679 --> 00:55:31.519
You know, I'm listening to you both talk about all this, and I'm just like, wow, it's um it's it's just uh you know, those those movies back from the 60s and 70s talking about the you know the futuristic space future.

00:55:31.679 --> 00:55:32.079
Uh-huh.

00:55:32.320 --> 00:55:33.679
We weren't too far off.

00:55:34.239 --> 00:55:34.800
Yeah, yeah.

00:55:34.960 --> 00:55:39.840
So I start I had a like um a feeling like I'm not sure where the future comes, right?

00:55:40.239 --> 00:55:44.000
And I wasn't sure about whether it's good or bad for me.

00:55:44.719 --> 00:55:51.280
But right now I have a feeling it cannot pass by me, it's me like ignoring it, right?

00:55:51.360 --> 00:55:53.440
So it's going to hit everybody, actually.

00:55:53.599 --> 00:55:59.920
Yeah, whether you're yes, it's it's yes, you you said that well.

00:56:00.320 --> 00:56:03.840
It's um uh it's not going away.

00:56:04.000 --> 00:56:08.079
It's uh it's it's it's a good time to take a look at uh what's available.

00:56:08.239 --> 00:56:10.800
Again, you don't have to rush, you don't have to use it just to use it.

00:56:10.880 --> 00:56:14.239
Uh as you talked about like the use cases, come up with practical use cases.

00:56:14.960 --> 00:56:24.639
I know with myself, I had to start small, like very small, simple things, not create an application.

00:56:24.719 --> 00:56:31.840
And I'm not even talking just development, I'm talking because you had mentioned you use it with your daughter and in ChatGPT and talking with them about stuff.

00:56:32.000 --> 00:56:34.320
But I started very, very small.

00:56:35.360 --> 00:56:41.360
And now I have a better understanding of it and I can know where to apply it.

00:56:41.679 --> 00:56:48.000
In in generality, though, I think people don't realize indirectly they're already interacting with AI.

00:56:48.079 --> 00:56:50.559
I mean, we mentioned that I don't Google anymore.

00:56:50.719 --> 00:56:52.000
Uh you're right.

00:56:52.079 --> 00:56:57.519
I I still go to google.com to Google stuff, but it summarizes for me.

00:56:57.679 --> 00:57:01.599
And and then you can turn it into AI mode, which you have a full chat.

00:57:02.079 --> 00:57:12.639
You really don't have to Google and search which the first, you know, the first thing that comes up on the list of among different links, it just summarizes it for you, saves you time.

00:57:12.960 --> 00:57:15.360
I remember when that was invented, by the way.

00:57:15.679 --> 00:57:16.320
Search engines.

00:57:16.400 --> 00:57:22.960
You know, search engines used to be pretty much manual where people had links and pages, and these are the sites.

00:57:23.119 --> 00:57:26.559
Like uh, I'm telling you, my poor brain has gone through a lot.

00:57:26.880 --> 00:57:29.280
Uh but to your point, Chris.

00:57:29.840 --> 00:57:31.280
See, I think of all these things now.

00:57:31.360 --> 00:57:33.519
It's um, I don't know, maybe that's a sign of being old.

00:57:33.599 --> 00:57:35.199
You saw it reminiscing.

00:57:35.519 --> 00:57:40.480
I think everybody uses AI a lot more than they think, like you said.

00:57:40.639 --> 00:57:44.079
It's not just in the search ending, but even like customer support.

00:57:44.320 --> 00:57:49.920
I saw a statistic on one large software company, and it really stuck out that they get like 30.

00:57:50.239 --> 00:57:54.079
It's a large software company, enterprise software company, and it's not Microsoft with Business Central.

00:57:54.159 --> 00:57:55.119
They saw this uh statistic.

00:57:55.199 --> 00:57:56.320
It was one of the other ones.

00:57:56.559 --> 00:58:02.239
They had 35,000 support requests, of which 30,000 were answered by AI.

00:58:02.480 --> 00:58:04.880
5,000 required a human.

00:58:05.360 --> 00:58:06.559
That's impressive.

00:58:06.880 --> 00:58:08.000
That is impressive.

00:58:08.159 --> 00:58:10.880
That's probably them asking for a human at that point, right?

00:58:10.960 --> 00:58:13.360
It's like, ah, I understand this is AI.

00:58:13.440 --> 00:58:15.440
Uh or whatever, you went through it.

00:58:15.519 --> 00:58:24.480
Or again, it might have been, you know, speak to a person or something, but this is the world we're in where I bet you a lot of your customer support type requests are handled by AI.

00:58:24.960 --> 00:58:40.239
I I I will say, just to go back into the enterprise level in our space, um uh I did I did have a conversation with uh two individuals that are similar industry, they're tech guys like us, but they're in a different world.

00:58:40.400 --> 00:58:44.159
One worked in Amazon and the other one works at Oracle.

00:58:44.480 --> 00:58:50.880
And so we were having a conversation about AI and using AI as kind of a day-to-day routine.

00:58:50.960 --> 00:59:00.400
And surprisingly, surprisingly, the two of them said that I haven't really dabbled into it as my day-to-day.

00:59:01.519 --> 00:59:09.280
So it's you know, again, I I'm living in this uh the Microsoft world where like everything's thrown to as co-pilot.

00:59:09.519 --> 00:59:14.159
Um, they even advertise now, and you know, I watched watching Monday Night Football the other day.

00:59:14.880 --> 00:59:33.360
Copilot by Microsoft was uh was uh marketed, but from hearing it from two different places, uh they said, and they're both technical developers, and they're like we don't we don't really we use it, but we don't it's not part of our daily routine.

00:59:34.880 --> 00:59:36.639
So that's surprising to me.

00:59:37.199 --> 00:59:38.159
Yeah surprising.

00:59:38.719 --> 00:59:43.199
So that's uh like a story between electrical cars and tuk tukes in South East Asia, right?

00:59:43.360 --> 00:59:50.159
So like you're gonna have electric cars across the developers, but you'll still have a lot of tuk tuk.

00:59:55.280 --> 00:59:58.880
It'll come, it takes time to adopt and and then eventually everybody will have it.

00:59:59.119 --> 01:00:02.559
Um Well, thank you so much for taking the time to speak with us today.

01:00:02.639 --> 01:00:04.480
I could speak with you uh for a long time.

01:00:04.559 --> 01:00:06.639
We'll have to have you on uh about some of these other topics.

01:00:06.719 --> 01:00:09.360
There's more topics I wanted to talk with you about.

01:00:09.519 --> 01:00:18.400
Um, but we do appreciate you taking the time you uh spent to speak with us today because uh any time you spend with us, you can't spend doing something else, and time truly is the currency of life.

01:00:18.480 --> 01:00:24.239
So I uh we do appreciate um uh you and all that you do, and you do some great things as well.

01:00:24.400 --> 01:00:34.559
Um if anyone would like to have some more information about um you know subscription billing, about AI with Business Central or any other the great things that you do, what's the best way to get in contact with you?

01:00:35.840 --> 01:00:38.000
Well, I would say maybe email.

01:00:38.079 --> 01:00:38.719
I don't know.

01:00:39.360 --> 01:00:43.760
I haven't thought about that, so uh will you put the email somewhere?

01:00:43.840 --> 01:00:45.920
Or I don't know how to yes, yes.

01:00:48.559 --> 01:00:51.280
Maybe even better idea is our blog, so there is a contact form.

01:00:51.360 --> 01:00:56.880
I have a blog, like it's Milian RS, uh point RS, so just drop me a line and I'll respond.

01:00:57.039 --> 01:01:03.920
If you have my email or Teams, you can also reach me out or public repos for Microsoft, whatever.

01:01:04.480 --> 01:01:05.119
Excellent action.

01:01:05.280 --> 01:01:05.920
Thank you, Milan.

01:01:06.239 --> 01:01:10.079
And uh we'll put uh your contact information within the show notes of this.

01:01:10.159 --> 01:01:14.880
And uh we look forward to speaking with you soon, and hopefully I get to see you at one of the upcoming events.

01:01:15.199 --> 01:01:16.559
Yeah, hopefully I had fun.

01:01:16.639 --> 01:01:17.760
Thank you guys for your time.

01:01:18.000 --> 01:01:18.719
No, thank you very much.

01:01:18.800 --> 01:01:19.599
I'll talk with you again soon.

01:01:19.679 --> 01:01:20.400
Chao ciao, bye.

01:01:20.800 --> 01:01:21.199
Bye bye.

01:01:23.039 --> 01:01:30.400
Thank you, Chris, for your time for another episode of In the Dynamics Corner Chair, and thank you to our guests for participating.

01:01:30.639 --> 01:01:32.159
Thank you, Brad, for your time.

01:01:32.320 --> 01:01:35.840
It is a wonderful episode of Dynamics Corner Chair.

01:01:36.079 --> 01:01:39.440
I would also like to thank our guests for join joining us.

01:01:39.599 --> 01:01:42.320
Thank you for all of our listeners tuning in as well.

01:01:42.559 --> 01:01:46.400
You can find Brad at developerlife.com.

01:01:46.639 --> 01:01:50.960
That is D V L P R L I F E dot com.

01:01:51.199 --> 01:01:56.719
And you can interact with them via Twitter, D V L P R L I F E.

01:01:57.360 --> 01:02:10.079
You can also find me at mattalino.io, m-a-t-a-l-in-o.io, and my Twitter handle is Mattalino 16.

01:02:10.960 --> 01:02:13.840
And see you can see those links down below in the show notes.

01:02:14.000 --> 01:02:17.119
Again, thank you everyone, thank you, and take care.