Feb. 26, 2026

Episode 506: Vibe Working, Not Vibe Coding: Is This Where We Are Headed?

Episode 506: Vibe Working, Not Vibe Coding: Is This Where We Are Headed?
Apple Podcasts podcast player iconSpotify podcast player iconYoutube Music podcast player iconRSS Feed podcast player iconAmazon Music podcast player iconAudible podcast player iconYouTube podcast player icon
Apple Podcasts podcast player iconSpotify podcast player iconYoutube Music podcast player iconRSS Feed podcast player iconAmazon Music podcast player iconAudible podcast player iconYouTube podcast player icon
Season 5

In this episode of Dynamics Corner, Kris and Brad are joined by Renato Fajdiga, a Croatia-based Dynamics veteran with a decade of experience spanning NAV development, Business Central consulting, and Finance & Operations implementation across 12 countries. Renato shares his unique perspective on running both BC and F&O, side by side, explains when multi-country organizations should lean toward one platform over the other, and breaks down how his team uses Microsoft Fabric to address consolidation challenges that ERPs were never designed to handle. The conversation takes a fascinating turn into AI, where the group compares Copilot capabilities between BC and F&O, and debates what happens when AI handles your transactions, reports, and even tells you to enjoy your day at the beach. Renato also shares how he uses AI in his personal life — from workout plans with follow-up suggestions to hiking route planning with AllTrails — proving that the impact goes well beyond code. Whether you're an SMB evaluating your first data warehouse or a consultant navigating the rapidly shifting ERP landscape, this episode is packed with insights and a few laughs along the way.

Send a text

Support the show

#MSDyn365BC #BusinessCentral #BC #DynamicsCorner

Follow Kris and Brad for more content:
https://matalino.io/bio
https://bprendergast.bio.link/

00:01 - Setting The Agenda: F&O Vs BC

00:27 - Guest Intro And Early ERP Tales

05:25 - Career Path And Current Roles

07:05 - Big Picture: AX, NAV, And Microsoft ERPs

07:51 - When To Choose F&O Over BC

10:53 - Multi‑Country, Localizations, And Tenants

12:36 - Performance, Setup, And Scale Realities

15:43 - Consolidation Strategy: Use Fabric, Not ERP

18:16 - AI In BC vs F&O: Copilots And Agents

20:28 - What Is Microsoft Fabric And OneLake

21:51 - Getting F&O And BC Data Into Fabric

24:13 - Data Migration Philosophy And Costs

27:05 - Agents, Analysis, And Actionable Insights

30:11 - Beyond Coding: Everyday AI Use Cases

33:25 - Trust, Quality, And AI‑Built Apps

36:11 - Analyst Mode Dreams Inside BC

38:35 - One UI Vision: Reports, Agents, Actions

41:07 - AP Agent To Insights: Work Reimagined

43:21 - Designing Reports For Executives

46:05 - SMB Data Warehousing: Practical Starting Points

WEBVTT

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

00:00:05.200 --> 00:00:09.679
What is the difference between FNO and Business Central?

00:00:09.759 --> 00:00:10.800
Which one do you choose?

00:00:10.880 --> 00:00:12.400
I'm your co-host, Chris.

00:00:12.640 --> 00:00:13.439
And this is Brad.

00:00:13.519 --> 00:00:16.239
This episode was recorded on February 12th, 2026.

00:00:16.399 --> 00:00:17.679
Chris, Chris, Chris.

00:00:18.160 --> 00:00:25.280
FNO Business Central, Fabric, Power BI, AI, Data Lake, One Lake.

00:00:25.600 --> 00:00:27.359
There's a lot of things out there.

00:00:27.839 --> 00:00:31.440
And with us today, we had the opportunity to break some of that down with Renato.

00:00:55.920 --> 00:00:57.920
Is it both of us are not moving?

00:00:58.799 --> 00:01:01.200
But now it's better, but it was only bread.

00:01:04.400 --> 00:01:05.920
I hope I was paused in a good position.

00:01:06.000 --> 00:01:14.719
Because you ever see like how sometimes when you're in meetings and such and somebody will either drop or they'll have uh internet connectivity issues and they're in some crazy pose.

00:01:15.519 --> 00:01:15.760
See?

00:01:16.159 --> 00:01:16.959
Yeah, obviously.

00:01:18.159 --> 00:01:19.120
Yes, exactly.

00:01:19.200 --> 00:01:19.840
That's an idea.

00:01:19.920 --> 00:01:20.239
That's it.

00:01:20.319 --> 00:01:22.319
That's an idea for a website for somebody to create.

00:01:22.400 --> 00:01:23.599
What would we call it?

00:01:23.760 --> 00:01:26.400
Like disconnected pictures or something.

00:01:26.560 --> 00:01:42.799
And just the crazy pictures that people are hung in when they get disconnected, which is um But you know, we are like uh six years ago when all this stuff started, you know, COVID and so on, and you still have like you know, you are on mute, you're on mute.

00:01:42.959 --> 00:01:46.000
Oh yeah, that's the famous, that's the famous quote.

00:01:46.239 --> 00:01:46.879
You're on mute.

00:01:48.799 --> 00:01:50.400
Well, can you say that again?

00:01:50.560 --> 00:01:51.680
You broke up.

00:01:54.480 --> 00:01:55.439
Can you say that again?

00:01:55.519 --> 00:01:57.200
Uh you uh you broke up.

00:01:57.519 --> 00:02:02.959
I'm pretty sure they sell t-shirts for those men that says you're on mute, or a hat that says you're on mute.

00:02:05.040 --> 00:02:10.800
Well, to everyone's defense, I'll give, you know, I'll have to be the nice guy today.

00:02:11.120 --> 00:02:21.680
Like with Teams, if you go into a meeting now, it can be set to pre-mute everybody who joins, but I think that's also if there's a certain number of people already in the meeting that will mute the person who attends.

00:02:22.080 --> 00:02:26.800
And I'm assuming that's so that they won't cause a disruption to people already speaking.

00:02:26.960 --> 00:02:28.639
But that's true.

00:02:28.960 --> 00:02:30.400
It's it sounds like a good story.

00:02:30.560 --> 00:02:32.159
It sounds like a good story.

00:02:32.960 --> 00:02:35.759
Especially for the big groups that uh yeah.

00:02:36.240 --> 00:02:44.400
But speaking of that, uh you figure we'd still would be able to get like those large gallery meetings to work properly, right?

00:02:44.479 --> 00:02:52.479
Where you have 10 or more people, 16 or more people to be able to see everybody, and then also be able to see who's talking.

00:02:52.639 --> 00:03:03.120
It's um we can AI vibe code the space shuttle and a rocket ship, but we can't have good video conferencing.

00:03:03.520 --> 00:03:04.400
Exactly.

00:03:05.599 --> 00:03:11.360
Because it this is still good enough, you know, and there is no need to improve.

00:03:11.680 --> 00:03:12.319
Good enough.

00:03:12.400 --> 00:03:13.439
Yes, good enough.

00:03:13.680 --> 00:03:16.639
We can have the effect you could suffer the rest of the time.

00:03:17.039 --> 00:03:24.240
Yeah, we can we can still have effective meetings, but uh enough of talking about our video conference woes.

00:03:24.400 --> 00:03:24.960
That is an idea.

00:03:25.039 --> 00:03:26.639
If somebody wants to make that website, let me know.

00:03:26.719 --> 00:03:29.360
I'd be interested in seeing all the photos and people could submit them.

00:03:29.520 --> 00:03:31.680
Uh, can you tell us a little bit about yourself?

00:03:32.159 --> 00:03:36.000
Okay, thank you, Brent and Chris, for having me on on this podcast.

00:03:36.159 --> 00:03:39.680
I think after a while we managed to somehow sync our calendars.

00:03:40.879 --> 00:03:42.000
Yeah, yeah.

00:03:42.080 --> 00:03:44.159
So thank you for uh having me on this.

00:03:44.240 --> 00:03:45.599
I'm very happy to be with you.

00:03:45.759 --> 00:03:47.280
Uh my name is Renato.

00:03:47.520 --> 00:03:50.080
I'm coming from Croatia, Zagreb.

00:03:50.400 --> 00:03:59.360
Uh so uh in NAV world or in dynamic space, I was I can say now a decade, and you know it's such a good word.

00:03:59.439 --> 00:04:05.360
You know, I'm a decade, I have a decade of experience uh with working with ERPs.

00:04:05.520 --> 00:04:30.720
Uh and I started as a developer, so I was uh NAV developer, and I was just remembering two days ago with my current manager uh in this company what was my first task uh as a as a developer then, and it was like we had to connect NAV with a printer, uh you know, and we didn't have that kind of printer because you know it's the old one where you have your those um continuous papers, you know, with the whole society.

00:04:31.360 --> 00:04:39.839
And we didn't have it, and then the customer sent this to us to our uh premises and sent five boxes of those papers just so we have for testing purposes.

00:04:41.839 --> 00:04:44.319
Exactly true story matrix matrix.

00:04:44.720 --> 00:04:53.839
I had that happen to me as well early on where it was a laser printer, and someone had to send me a laser printer to the office for me to configure.

00:04:54.240 --> 00:05:01.120
And uh well, I want to go back to your stories, but I also remember it was faster one time.

00:05:01.279 --> 00:05:10.720
I was going between uh the north, well, New York and Boston area at one time, working with a lot of um implementations in New York City.

00:05:11.360 --> 00:05:20.959
It was faster to get on the train from Boston, go to New York, grab a backup, come back to be able to restore it to work on it.

00:05:21.839 --> 00:05:22.399
Yeah.

00:05:23.439 --> 00:05:24.079
Different times, yeah.

00:05:24.399 --> 00:05:25.920
Different times, yeah, yeah.

00:05:26.160 --> 00:05:32.240
And from those development uh exercises, uh, I switched to uh consultancy.

00:05:32.399 --> 00:05:40.560
So I was uh dynamics NAV consultant, uh, and then uh six years ago I uh switched uh role.

00:05:40.720 --> 00:05:54.399
Now I'm leading the team uh responsible for implementation of financing operations, business central, public, and so on at the customer side, but I also have my own company uh that I am consulting for Business Central.

00:05:54.560 --> 00:05:59.519
As you know, business central is my my true love, I would say.

00:06:00.319 --> 00:06:04.639
I share that love because I have business central in my veins, as they say, going through it.

00:06:04.800 --> 00:06:12.800
So you work with Finance and Operations, Fabric, and Business Central, and you also do consulting.

00:06:13.199 --> 00:06:14.720
You have to be Superman.

00:06:16.160 --> 00:06:20.160
Yeah, uh you know they have only 24 hours, so yeah.

00:06:21.360 --> 00:06:22.800
You work all 24 hours.

00:06:23.040 --> 00:06:24.319
Do you work all 24?

00:06:25.279 --> 00:06:36.879
Yeah, that's that's an interesting combination because I mean if you go back historically, we had Nivision, we had Xapta, which was DamGuard.

00:06:37.040 --> 00:06:42.079
Nevision had the Nivision software, Damgard had Exapta, or yeah, it was Xapter at that point.

00:06:42.160 --> 00:06:43.920
I forget when it was AX or Xapta.

00:06:44.079 --> 00:06:51.600
Then they merged, and then Microsoft Perch, and because then it wasn't like wasn't it like Nevision DamGuard that the company switched at one point or something?

00:06:51.680 --> 00:06:52.560
I don't know.

00:06:53.439 --> 00:07:02.160
And then it was always talked that you know AX, Exapta, or Finance and Operations was like the big brother to Business Central.

00:07:02.480 --> 00:07:05.519
And you're working with both of them today.

00:07:05.759 --> 00:07:08.319
Is there that much of a difference between the two?

00:07:09.040 --> 00:07:22.319
I mean, in in in if you think about uh how much you need to implement ours, and if you hope only to implement all modules, yes, it would be like big, big brother uh uh comparison to BC.

00:07:22.639 --> 00:07:28.800
Uh but it's very nice to see that, for example, we are using finance modules mostly in our organization.

00:07:29.120 --> 00:07:34.000
And you can do the same process in the both systems uh without any any issues.

00:07:34.079 --> 00:07:45.680
And users can very easily switch from one to another tool uh because we have some users that are working at the same time in BC and finance and operations, and they are uh so they're using both.

00:07:46.399 --> 00:07:47.120
Yeah, yeah.

00:07:47.279 --> 00:07:53.120
We have in one of our country we have Business Central, while in the other 11 we have uh finance and operations.

00:07:53.439 --> 00:07:58.720
Uh so it it's quite that's that's an interesting pick of why they would someone would choose that.

00:07:58.800 --> 00:08:03.360
I listen, every business makes decisions for the moment just sounds you know a little different from it.

00:08:05.360 --> 00:08:16.399
Okay, mostly because they just upgraded from NAV to BC and it was like no uh no benefit to migrate them to immediately after they migrated to BC to F and O.

00:08:16.560 --> 00:08:24.240
So they let they say okay, we want to keep a little bit of BC, and then uh let's see uh when we are going to move to group-wide solution.

00:08:26.800 --> 00:08:27.600
That's amazing.

00:08:28.079 --> 00:08:31.759
So you're saying so that they can work in finance, it's similar in finance.

00:08:32.080 --> 00:08:35.679
I have only seen FNO or finance and operations.

00:08:35.840 --> 00:08:39.360
Um, I did sit through a small demonstration of it.

00:08:39.440 --> 00:08:43.039
I've gone through a demonstration on how to develop in it many years ago.

00:08:43.200 --> 00:08:48.080
Um, but I never really had the opportunity to use it at any uh level.

00:08:48.240 --> 00:08:54.799
And I was always curious to know because it then you have two ERP systems under one umbrella.

00:08:54.960 --> 00:09:05.759
Well, you have many ERP systems now because you also have Great Plains, but I think we know where that's going in the next couple years, um, within the next couple years, uh what the differences are between them.

00:09:06.000 --> 00:09:09.039
So it's it's it's challenging to see.

00:09:09.200 --> 00:09:20.960
I mean, I've always thought that Business Central was geared towards the SMB small to medium businesses, and the finance and operations was geared towards the larger organizations.

00:09:21.360 --> 00:09:27.840
But now I'm also thinking and seeing like Business Central could run a large organization with the current technology.

00:09:28.080 --> 00:09:41.919
Maybe many, many years ago it it had some constraints uh for some the it also defines what you could depends what you define a large implementation, because I've seen several large implementations even back of NAV 2009 with several hundred users.

00:09:42.159 --> 00:09:50.240
So I was just curious to know what the difference would be for for driving somebody to one versus the other in 2026.

00:09:52.240 --> 00:09:54.960
I mean, I would now go, if you ask me.

00:09:55.360 --> 00:10:06.639
I would go and let I mean our uh situation is specific because we have 11 countries and they are all on the same environment, same tenant, everything works between one database.

00:10:06.879 --> 00:10:09.360
Except business title is its own database.

00:10:09.600 --> 00:10:17.360
To achieve that kind of uh uh work, you will need 11 environments or multiple tenants and so on for BC.

00:10:17.759 --> 00:10:20.240
So this is the way when I will go to F and O.

00:10:20.480 --> 00:10:30.960
If you have multi-country, uh lot of localization, a lot of partners, uh very heavy processes, a lot of transactions, uh then yeah, go to F and O.

00:10:31.279 --> 00:10:39.840
Even though, as you said, uh we can also support uh a lot of transactions as well with uh business central, with proper configuration, of course, of BC.

00:10:40.320 --> 00:10:47.440
Um because you can also have issues uh in F and O if you set keys differently wrongly.

00:10:48.879 --> 00:10:56.480
I I I think any system will sweat if you set it up improperly or use it improperly.

00:10:56.559 --> 00:11:04.159
Uh you know, it's a lot of times they you know permission and performance to me, performance is uh one, it's relative because how fast should something go?

00:11:04.240 --> 00:11:09.600
I mean, i I tell everyone you can only fly from here in the United States from Boston to Los Angeles so fast.

00:11:09.759 --> 00:11:15.759
I mean, you could say I'd like to be there in five minutes, but the reality is you have an entire continent you have to span.

00:11:15.840 --> 00:11:17.679
So that will definitely take some time.

00:11:18.000 --> 00:11:21.360
But yes, oftentimes it can be misconfigured.

00:11:21.440 --> 00:11:31.600
And any system, I'm not trying to say that um any system is poor in that case, because you can code yourself into um sleep or stoppage.

00:11:32.000 --> 00:11:47.200
And I mean, so so primarily uh uh because I I get this question from time to time, especially when we have uh prospects that are moving, you know, whether they do business central or another ERP, it could be uh other uh ERP, it could be Net Suite and so forth.

00:11:47.360 --> 00:11:52.799
And um, you know, a lot of the questions like when do we go to F and O.

00:11:53.279 --> 00:12:16.960
And you know, I I think my understanding, correct me if I'm wrong, is that typically around the localization, especially if you have multiple entities that uh spans across different locations where you have localization requirements and but they want to keep at the same tenant rather than multiple tenants and then having it talk to each other uh for consolidation.

00:12:17.440 --> 00:12:24.000
Is that the key factor of why you why the I mean one of the big reasons why you would want to go to FNO at that point?

00:12:24.559 --> 00:12:27.840
Yeah, that was that was the reason because of the consolidation.

00:12:28.080 --> 00:12:36.159
But then uh over the time we grow so much that even now consolidation cannot run in the let's say uh time that we want to that we want to.

00:12:36.320 --> 00:12:53.600
And what we are now trying to achieve, and this is the project for uh this year and maybe next year, consolidated all the data from both systems in one data warehouse known as Microsoft Fabric, and then on top of that implement proper consolidation tool.

00:12:53.919 --> 00:13:02.000
Because many times I hear from Microsoft support, Microsoft Engineer, look, this is the ERP, it's accounting software, it's processing tool.

00:13:02.159 --> 00:13:06.240
It's not consolidation tool, it's not meant that primary focus is consolidation.

00:13:06.399 --> 00:13:22.399
And for consolidation, we have uh various tools, even they are saying you can use Power BI together with Fabric and consolidate all your uh statements, all your transactions on that way rather than having a load on the production of database.

00:13:22.639 --> 00:13:24.879
Yeah, that is a that's a good point.

00:13:25.279 --> 00:13:26.320
That's another interesting point.

00:13:26.559 --> 00:13:35.039
It's again your ERP software is for your transactional data, and then you have other tools that give you the analysis portion of it.

00:13:35.200 --> 00:13:39.120
So instead of trying to use the same tool for everything, offload some of that.

00:13:39.360 --> 00:13:40.159
See, I like all these things.

00:13:40.639 --> 00:13:45.440
No, I do like that because a lot of times there's maybe some confusion, and I I could be wrong from an accounting.

00:13:45.519 --> 00:13:49.200
I'm not an accounting person, uh, but you know, we work with a lot of accounting.

00:13:49.519 --> 00:13:50.720
But you play one on TV, don't you?

00:13:51.039 --> 00:13:55.360
Or I play one, I play one on TV and uh or behind the teams meeting.

00:13:55.519 --> 00:14:06.320
But like if you were to look at when they say, you know, uh we need a consolidating company, and so they typically create a company in Business Central or F and O.

00:14:06.480 --> 00:14:17.519
And then, but in reality, consolidation is really just for them to report against um to you know appease the maybe some of the requirements for the consolidating, all the different companies.

00:14:17.759 --> 00:14:31.120
So you're what you're doing right now, it's rather than putting it into an entity in itself just to consolidate all the different places, uh, instead you're putting it in fabric and then presenting it in a uh Power BI report.

00:14:31.279 --> 00:14:32.559
I mean, that's really what it is, right?

00:14:32.639 --> 00:14:34.879
That's that's what that's what consolidating is.

00:14:35.039 --> 00:14:36.080
It's just a reporting answer.

00:14:36.399 --> 00:14:37.759
And then it's a report, report.

00:14:37.919 --> 00:14:40.720
And the end of the end of end product of consolidation is a report.

00:14:40.799 --> 00:14:42.559
Yeah, it's not some translation or so on.

00:14:42.879 --> 00:14:58.879
And then when I now go back from that perspective, uh if I take a look at the process wise, I could I could say that every all the countries that we implemented in F and O, for example, we can split them into multiple BC instances and nothing will break, you know.

00:14:59.279 --> 00:15:06.399
Everything will work, users will have the even better maybe UI, uh, and some advanced AI capabilities.

00:15:06.720 --> 00:15:09.039
Uh and we will be able to achieve the same.

00:15:09.200 --> 00:15:16.879
Because as I said, the process is not that complex in our F and O systems that we cannot support with BC currently.

00:15:17.120 --> 00:15:21.840
But of course, we don't have warehousing production, manufacturing, and so on.

00:15:22.320 --> 00:15:26.000
So that's why I would say uh I have this opinion.

00:15:26.320 --> 00:15:26.960
Yes, okay.

00:15:27.039 --> 00:15:32.399
So that from the manufacturing distribution point of view, maybe uh a different scenario.

00:15:32.639 --> 00:15:43.039
You had mentioned, and I was going to try to go the entire episode or recording, whatever we call these things, without saying AI, but you said more advanced AI features.

00:15:43.600 --> 00:15:44.240
Yes.

00:15:44.559 --> 00:15:53.600
So did you uh infer that Business Central has more advanced AI features today than FNO, or do you think they're relatively the same?

00:15:53.840 --> 00:15:54.879
I'm putting you on the spot.

00:15:56.720 --> 00:15:58.240
They both have MCPs.

00:15:58.399 --> 00:15:59.039
Woo-hoo.

00:16:00.559 --> 00:16:01.120
There you go.

00:16:04.639 --> 00:16:10.559
That's one, but uh, if I mean if you take numbers, like I like to be you know uh strict.

00:16:10.720 --> 00:16:11.679
Let's take a numbers.

00:16:11.840 --> 00:16:18.480
If you open the BC and search for co-pilot and agent capabilities, you will get 11 or 12 copilots, right?

00:16:18.960 --> 00:16:24.799
You have data analysis, you have chat, you have summarization, marketing text, bank reconciliation, and so on.

00:16:24.960 --> 00:16:27.919
If you go to F and O, you will find up to 10.

00:16:28.159 --> 00:16:30.240
So not more than BC.

00:16:30.639 --> 00:16:35.919
So, and that's I would say the benefit of VC, because BC is more agile tool.

00:16:36.000 --> 00:16:41.919
You know, we can implement more features, more AI features without interrupting the core standards.

00:16:42.000 --> 00:16:50.799
And F and O being Beast, uh, in my opinion, that's why they're somehow lacking of behind the BC of having those copilot capabilities within the tool.

00:16:51.039 --> 00:16:52.720
Yeah, BC does have a lot.

00:16:52.879 --> 00:17:02.399
I think they're up to I think I just did a presentation on AI uh within BC, and it's over 17 AI features.

00:17:02.559 --> 00:17:04.319
Not necessarily just copilot, but AI features.

00:17:04.400 --> 00:17:11.119
If you talk about uh the purchasing agent, sales order agent, uh, you know, let's talk about the expense agent.

00:17:11.359 --> 00:17:17.200
Now you have the agent preview, which came out 27.4, uh that you can work with.

00:17:17.359 --> 00:17:28.400
Uh you have the MCP service, like you said, you have the co-pilot chat, copilot summary, uh ask co-pilot for the co-pilot fields, uh bank reconciliation.

00:17:29.200 --> 00:17:30.079
I can keep going on.

00:17:31.119 --> 00:17:42.640
Yeah, BC is yeah, it's because I said, because I this is my opinion, uh because they are like smaller, they're better to innovate uh and team is investing a lot.

00:17:42.799 --> 00:17:47.039
I'm not saying that F and O is not doing it, but I think it's much harder for them to achieve that.

00:17:47.359 --> 00:17:48.079
No, I understand.

00:17:48.160 --> 00:17:59.440
It's it's much it's much more difficult to ship shift a large vessel when it's moving than it is something that may be a little bit smaller and has the ability to do it.

00:17:59.519 --> 00:18:00.720
So I and I understand what you're saying.

00:18:00.799 --> 00:18:09.039
It's it's um the business central team is doing a great job and they have the opportunity because of just the way the architecture works and uh uh the way it's going through.

00:18:09.279 --> 00:18:11.279
So you work with business central fabric.

00:18:11.359 --> 00:18:15.599
Fabric's another topic that people talk about.

00:18:16.079 --> 00:18:18.319
Just from an overview, what is fabric?

00:18:18.400 --> 00:18:22.160
Because I hear when it's data warehousing, you know, it's I'm an old guy.

00:18:22.319 --> 00:18:26.640
People went from you know, um SQL analytics, right?

00:18:26.960 --> 00:18:34.319
Um with uh reporting server, SQL reporting server, you know, as their data warehouse.

00:18:34.559 --> 00:18:39.440
And then now I hear like One Lake, Data Lake, Fabric, all these other things.

00:18:39.599 --> 00:18:42.480
So what is fabric in essence?

00:18:42.960 --> 00:18:50.400
I mean, in I as I'm calling it to my finance team, and I'm explaining, it's like one-stop shop for all your financial data in our case.

00:18:50.640 --> 00:18:59.759
So we are bringing all the data from various finance systems like F and O and BC into Data Lake, and from there we can manipulate with those data.

00:18:59.839 --> 00:19:06.079
So we are extracting data, you can transform, and you can of course load this data to someone else, somewhere else.

00:19:06.559 --> 00:19:18.960
Uh so I would say uh Fabric will ultimately become like main repository for your data when we are talking about reporting and uh building uh analytics and dashboards on top of finance finance data.

00:19:19.680 --> 00:19:26.240
So for the from the FNO point of view, how do you get the data into Fabric?

00:19:26.319 --> 00:19:30.799
And from the business central point of view, how do you get the data into Fabric?

00:19:31.599 --> 00:19:33.519
I uh this is where I like FNO.

00:19:33.680 --> 00:19:35.279
It's much easier than in BC.

00:19:35.680 --> 00:19:46.480
Uh in FNO you have a uh a link between uh uh F and O and Fabric, so you are usually using two datavers and then uh pushing data to uh to Fabric.

00:19:46.960 --> 00:20:08.240
Uh for BC, we still don't have a connector uh natively that we can use, so we are relying to uh some community solutions like Bert has uh or you can use uh business central, uh how is called data flows to import the data uh with data flows to fabric workspace and then consume it, consume it from there.

00:20:08.640 --> 00:20:11.279
So those are the two ways that you can do now.

00:20:11.599 --> 00:20:13.759
There are third way which I don't like.

00:20:14.160 --> 00:20:18.960
It is like you know that there is like native integration between business central and dataverse.

00:20:22.240 --> 00:20:31.440
So you can somehow that way uh use the bring data from BC to Fabric, but this is not the purpose of that connector between BC and Dataverse.

00:20:31.920 --> 00:20:32.720
Uh yeah.

00:20:32.960 --> 00:20:38.960
So I hope that soon we will have some data down for something like uh to Fabric.

00:20:40.960 --> 00:20:49.359
So you can report off of FNO, external systems and business central within Fabric, so you can do your data analysis.

00:20:49.440 --> 00:20:53.039
So if you have disparate systems or even historical data, right?

00:20:53.119 --> 00:21:01.279
It's I think a lot of times individuals, if they're going through a new implementation or an upgrade, even the challenge is what do I do with my data?

00:21:01.440 --> 00:21:05.440
Do I convert everything and bring it into my ERP software?

00:21:05.759 --> 00:21:09.119
Or do I leave my existing system functional?

00:21:09.359 --> 00:21:13.279
But or even from the reporting point of view, I have multiple systems.

00:21:13.359 --> 00:21:14.480
How do I get them all together?

00:21:14.640 --> 00:21:21.920
You know, do I do I do interfaces to import data into one system so I can do all my reporting in one place?

00:21:22.079 --> 00:21:34.720
But now we can take it up a layer, like you said, let the ERP software manage the transactions and the data reside somewhere for you to be able to do reporting on.

00:21:35.279 --> 00:21:35.759
Exactly.

00:21:35.920 --> 00:21:40.640
Yeah, I mean, this is like always, you know, as we said on upgrades for new implementations or the implementation.

00:21:40.799 --> 00:21:50.079
Should I bring 10 years of my uh GL to a new system or should I bring this outside and then connect both the systems uh in fabric?

00:21:50.400 --> 00:21:52.079
Yeah, I'd have to look at some analysis.

00:21:52.160 --> 00:21:56.960
I wonder how much of an upgrade or an implementation has to do with data management.

00:21:57.200 --> 00:21:59.759
You know, no, not even an upgrade necessarily, or even like if you move.

00:22:00.160 --> 00:22:01.039
To a new system, right?

00:22:01.119 --> 00:22:09.359
If you really are trying to take that data, how much of the effort is really in bringing that data over and why?

00:22:09.519 --> 00:22:09.680
Right.

00:22:09.839 --> 00:22:13.680
So I mean, I can understand open transactions, right?

00:22:13.839 --> 00:22:29.200
Open sales orders, open purchase orders, open receivables, open payables, you know, even maybe a couple years worth of GL information so that you can do some uh financial reporting you know in that system without having to go externally.

00:22:29.279 --> 00:22:30.799
But again, you could still go externally.

00:22:31.039 --> 00:22:32.960
But I really am curious to know or think.

00:22:33.200 --> 00:22:39.680
I'd like to see that how much of a uh how much of an upgrade implementation uh goes with data management.

00:22:40.000 --> 00:22:41.039
The the value in itself.

00:22:43.680 --> 00:22:43.920
Yeah.

00:22:44.160 --> 00:22:44.720
Yeah, Chris.

00:22:45.359 --> 00:22:50.720
I said in previous uh when I was a consultant, I mean I never we never move transactional data.

00:22:50.799 --> 00:22:53.519
It's always like open transactions, like the mentioned bread.

00:22:53.759 --> 00:23:00.400
And then you either do some BI uh bring this data to some BI dashboards and so on.

00:23:01.359 --> 00:23:06.880
I don't see value uh of bringing all transactions in the business central or any database.

00:23:06.960 --> 00:23:09.759
You're just growing the the old database.

00:23:10.160 --> 00:23:15.279
Yeah, and well you know there's a cost to space uh you know from the business central point of view.

00:23:15.359 --> 00:23:19.039
I don't know how it's licensed within F and O, but I know Business Central.

00:23:19.200 --> 00:23:31.599
Um, you know, you you get with the system in the number of users you have uh uh large capacity uh for data, and uh why consume that with nothing?

00:23:31.920 --> 00:23:33.519
You know, I call it nothing, you know.

00:23:33.839 --> 00:23:34.319
Yeah.

00:23:34.640 --> 00:23:44.640
And it's I mean FNO, you have like uh you're buying uh licenses and you're getting some capacity, and off top of that you can buy as well capacity uh if you need uh, of course.

00:23:45.200 --> 00:23:46.640
I wonder where this will all go.

00:23:46.799 --> 00:23:48.319
Like there's just a lot, right?

00:23:48.400 --> 00:23:52.160
It's I I I keep saying, and I'll say this on every episode almost like a broken record.

00:23:52.240 --> 00:23:53.279
I just miss like the simple days.

00:23:53.359 --> 00:24:05.599
I wonder if we'll ever get back to the simple days because now I don't know how you do it with the the you know, understanding and managing all that, because the the technology is just expanding.

00:24:05.759 --> 00:24:11.599
And then now, forget it, you throw AI and models and all this stuff into the mix, and it's like, which way am I going?

00:24:11.759 --> 00:24:16.000
Or uh how do I manage uh all of that?

00:24:16.799 --> 00:24:19.680
I I think there is no point of returning back.

00:24:19.759 --> 00:24:25.839
Uh so we are just need to embrace AI uh in our day-to-day life, building reports and and so on.

00:24:26.160 --> 00:24:27.599
Oh, you have to embrace it.

00:24:27.759 --> 00:24:32.640
It's um I think I I've been reading a lot of interesting articles, even with some of the new models that came out.

00:24:32.880 --> 00:24:36.480
I do quite a bit with it each night or each evening, and even use it several times during the day.

00:24:36.559 --> 00:24:42.480
But I think um what you can do with it if you use it properly is amazing.

00:24:42.720 --> 00:24:46.400
And even I'm excited about the features within Business Central.

00:24:46.480 --> 00:24:50.160
I'm really excited to work with the agent playground to be able to create my own agents.

00:24:50.240 --> 00:25:00.240
That's my fun for this weekend, is I'm going to work with uh the new agent preview to say create some agents to see what I could do and have some fun.

00:25:00.880 --> 00:25:13.200
Yeah, I mean uh I like this stuff, uh, what we saw already about policies that you can upload the policy and for example see if uh your customer is always uh overdoing their payments.

00:25:13.839 --> 00:25:19.599
So do we have somebody are compliant, not compli uh compliant to our policies and so on.

00:25:20.480 --> 00:25:30.559
No, it's it's uh it's amazing what it can do, and it's it's getting so much better because it is almost like having uh an employee or uh an assistant.

00:25:30.720 --> 00:25:36.480
So, you know, the word co-pilot from the Microsoft, you know, platform is truly what it is.

00:25:36.559 --> 00:25:39.440
It's like Chris, you had mentioned it several episodes ago and something.

00:25:39.519 --> 00:25:48.960
It really is like a co-pilot that's helping you uh get your tasks done, which is um it's uh it's breathtaking, I guess you could say.

00:25:49.119 --> 00:25:51.279
It's awesome, it's my overwhelming monstruck.

00:25:51.440 --> 00:25:52.720
I don't even know what to say.

00:25:53.039 --> 00:26:00.960
Um it's even now pushing back in a sense, where it's saying, Oh, did you want to do this?

00:26:01.119 --> 00:26:03.599
You know, because you can see like when you put it in the mode, you can read the text.

00:26:03.759 --> 00:26:05.759
Oh, the user wants to do this, the user wanted that.

00:26:05.839 --> 00:26:09.200
And I asked it to do something and it said, Oh, do you sure you want to do this because you could do it this way?

00:26:09.359 --> 00:26:10.079
I was like, What?

00:26:10.240 --> 00:26:10.880
Yeah.

00:26:11.680 --> 00:26:14.480
It gives you suggestions to do something different and better.

00:26:14.559 --> 00:26:17.680
And sometimes you don't realize, like, oh yeah, I didn't think about that.

00:26:17.839 --> 00:26:31.279
It's like it's it's making you be more efficient in in uh thinking about more the intent of what you're trying to accomplish rather than just actioning against what the prompt you you've given it.

00:26:31.759 --> 00:26:34.799
Yeah, and that that's what I like, that's follow-up questions.

00:26:34.960 --> 00:26:39.920
I mean, just uh some uh example from uh my personal life.

00:26:40.079 --> 00:26:41.680
I started to like work out.

00:26:42.000 --> 00:26:45.039
Uh and I said, okay, give me like I want to do this.

00:26:45.200 --> 00:26:49.519
Uh I have 30 minutes, give me the exercises that I and then he kind of follow-up.

00:26:49.599 --> 00:26:52.079
Do you want the images of how this exercise should look like?

00:26:52.240 --> 00:26:54.640
I was like, Yes, I never thought of that.

00:26:54.880 --> 00:27:01.680
Because I was already in my mind that okay, he will give me the exercise, I don't know, uh push-ups, and I will go and Google how to do push-ups, you know.

00:27:02.559 --> 00:27:09.599
That's such a perfect example because when you say push-ups, right, there's you people don't realize there's different ways to do push-ups.

00:27:09.839 --> 00:27:11.440
You don't just do normal push-ups.

00:27:11.599 --> 00:27:20.000
And so, like, well, to be more efficient, you should do this kind of push-ups if you want, you know, like bigger upper body strength, right?

00:27:20.079 --> 00:27:33.359
Like, it's it's pretty interesting that it's allowing you to be more focused in what you're trying to accomplish, more intentional, rather than just like, oh yeah, go do a push-up, and you maybe you'll uh improve.

00:27:35.200 --> 00:27:37.920
But you bring up a good point with that.

00:27:38.079 --> 00:27:39.759
One, I wonder how all this stuff works.

00:27:39.839 --> 00:27:47.279
I might wonder, but I've given up trying to uh you know understand how it can be like talking to a person.

00:27:47.359 --> 00:27:52.000
Uh you know, uh, like I said, I'm going to start hooking voice up to it and have it just talk back to me.

00:27:52.319 --> 00:27:56.000
But you can use it for so much more than just code, right?

00:27:56.160 --> 00:28:01.359
Because a lot of people talk about AI and coding and being able to produce all this stuff.

00:28:01.599 --> 00:28:08.000
On a side note, yes, you can do it with AL for Business Central, but people making all these apps for a lot of things.

00:28:08.079 --> 00:28:10.319
I'm wondering where all these apps go, by the way.

00:28:10.559 --> 00:28:17.599
Because I see all these people online, like, oh, I, you know, I spent this much long, coded this app, did all this, I'm doing all this.

00:28:17.839 --> 00:28:19.599
Like, who's going to use all these apps?

00:28:19.839 --> 00:28:22.240
And I'm going to go on a little tangent right now.

00:28:22.559 --> 00:28:32.559
All these apps that are created with AI, if we don't have quality standards for it, then we're going to have we're going to lose our trust in the applications, right?

00:28:32.640 --> 00:28:35.920
Because now people think, oh, I'm going to buy the software application, it's going to do something for us.

00:28:36.079 --> 00:28:37.119
History repeats itself.

00:28:37.279 --> 00:28:41.039
People used to write their own applications, and then everyone started purchasing applications, right?

00:28:41.119 --> 00:28:44.480
Remember when people, even with ERP software, a lot of people would write their own ERP software.

00:28:44.640 --> 00:28:55.039
And then they realized, well, it's not cost effective, and we can have somebody else maintain it, get feedback from all these other users, and then write it, and then we purchase it, and uh, we have the business value from it.

00:28:55.119 --> 00:29:01.599
But now, if everybody's vibe coding, as they call it, all these different applications, what are you going to download and install and use?

00:29:01.759 --> 00:29:10.160
And if it's not trustworthy, people are going to like, okay, it's easier for me just to do it myself because at least I know what I'm getting and I can fix it quickly.

00:29:10.400 --> 00:29:12.160
So that was my side thing.

00:29:12.240 --> 00:29:16.640
But to go back to your point, you can use it for so much more than just coding.

00:29:17.359 --> 00:29:19.599
It's and you said vibe vibe coding.

00:29:19.680 --> 00:29:22.319
And I I I think I read yesterday or two days ago.

00:29:22.400 --> 00:29:25.440
It's not there anymore live coding, it's now vibe working.

00:29:25.599 --> 00:29:25.839
Yeah.

00:29:26.880 --> 00:29:28.880
It's a good way to that's a good way to put it.

00:29:28.960 --> 00:29:31.279
It's not just for development.

00:29:31.680 --> 00:29:32.240
It's not.

00:29:32.880 --> 00:29:33.599
It's not.

00:29:33.680 --> 00:29:36.720
I I uh I see it used in many ways.

00:29:36.880 --> 00:29:42.720
And it's like I said, you're almost you are if you haven't started using it, you need to start using it.

00:29:42.799 --> 00:29:44.319
I mean, the people have been saying that for months.

00:29:44.480 --> 00:29:54.240
Uh you know, and months in AI terms is like decades and maybe even centuries in human terms because the the turnaround every two three months is is is crazy.

00:29:54.480 --> 00:30:02.720
But to use it even for like you said, if your person who's to help you come up with a workout, yes, you can validate and come up with a workout, but at least it brings exposure to you for a workout plan.

00:30:02.880 --> 00:30:05.039
I've known people who've used it for financial plans.

00:30:05.119 --> 00:30:18.640
I've known people who've used it to um uh create other types of plans um for themselves and in documentations and even you know researching and summarizing um topics.

00:30:19.039 --> 00:30:23.359
Yeah, I mean what I also like, I mean, on top of that, uh workout plan.

00:30:23.519 --> 00:30:35.200
Uh it was also that you you know that you can connect uh uh Spotify and so on to to uh ChatGPT, like an app, and then you ask, please suggest me uh Spotify playlist on top of that.

00:30:35.519 --> 00:30:36.559
No, I did not know that.

00:30:37.119 --> 00:30:40.960
Yeah, yeah, you can so it's it's crazy.

00:30:41.359 --> 00:30:43.680
I mean I also using it sometimes for for hiking.

00:30:43.759 --> 00:30:49.440
You can also connect app that is all trails, it has all trails, all kinds of trails uh for hiking.

00:30:49.599 --> 00:30:52.640
And they just say, okay, I want to go there and there, give me that hike.

00:30:52.799 --> 00:30:55.279
I want that this is like medium really.

00:30:56.319 --> 00:30:57.039
I use all trails.

00:30:57.200 --> 00:31:01.359
I mean when I'm when I'm up north and I do the hiking up north, I use all trails and I use it to track all myself.

00:31:01.519 --> 00:31:03.200
So you can use AI with that now?

00:31:03.599 --> 00:31:08.000
Yes, you can use it AI within the uh all trails when you are creating a route.

00:31:08.240 --> 00:31:14.960
So you have like, okay, I want to go, I don't know, to Monteveras, give me the shortest route and with the less uh uh steep, you know.

00:31:15.119 --> 00:31:17.200
And it will create a route like that for you.

00:31:17.440 --> 00:31:20.079
And it tells you how to prepare for it at the same time.

00:31:20.400 --> 00:31:20.640
Yeah.

00:31:21.119 --> 00:31:24.720
Where are we going to be without AI?

00:31:24.960 --> 00:31:26.640
Is there anything that doesn't have AI in it?

00:31:27.119 --> 00:31:30.319
There's gonna be dependency on this uh AI down the road.

00:31:30.400 --> 00:31:36.160
I would say probably in three years, that there's gonna be a lot of dependency on AI and the things that we just want to do.

00:31:36.319 --> 00:31:36.720
Three years.

00:31:37.359 --> 00:31:39.279
Three years AI won't even be AI anymore.

00:31:39.359 --> 00:31:40.559
It will be something completely different.

00:31:40.880 --> 00:31:43.839
That's like a lifetime several lifetimes away.

00:31:44.160 --> 00:31:47.839
I mean, I saw it this week, Notepad even has AI now.

00:31:48.079 --> 00:31:49.839
That was a big problem with Windows and the update.

00:31:50.000 --> 00:31:54.319
Like I was and I said to myself, for a simple text editor, like that's what you want sometimes.

00:31:54.400 --> 00:31:55.920
Like just a jot a quick note.

00:31:56.079 --> 00:31:57.759
Why do you need AI and Notepad?

00:31:58.319 --> 00:32:00.799
It's like we're getting AI in everything.

00:32:01.119 --> 00:32:01.599
Yeah, yeah.

00:32:01.680 --> 00:32:05.680
Yes, I I like to say, I think this is just a beginning, you know.

00:32:05.839 --> 00:32:08.799
It was like two years ago it became mainstream.

00:32:08.960 --> 00:32:21.680
Uh, and it's I I I have it's just a beginning when you see when you say agent playground, what it can do just by you typing the words and what it can do in the BC that I think the agent playground.

00:32:21.839 --> 00:32:23.359
The MCP was exciting.

00:32:23.599 --> 00:32:26.880
Um, I think there's a certain space for that, right?

00:32:26.960 --> 00:32:30.720
For certain types of organizations for interconnectivity and stuff.

00:32:30.960 --> 00:32:37.119
But I really do see the agent playground to me, or agent preview, I think they they named it now.

00:32:37.200 --> 00:32:41.759
I I pay attention to the GitHub repo for documentation, and I think it was February 6th.

00:32:41.920 --> 00:32:47.359
They did change it to uh agent preview, I believe, right before the update for 27.4.

00:32:48.160 --> 00:32:49.519
I think that would get a lot of use.

00:32:49.599 --> 00:32:59.119
It was almost going to be like what it won't be as exciting to me as the analysis mode was on the list pages, because to me that's still by far like one of the best things that were added to the application.

00:32:59.359 --> 00:33:06.640
But I think the agent uh preview or agent playground is what it was called before, is going to be another big one for even small tasks.

00:33:06.720 --> 00:33:12.000
I'm not necessarily saying end-to-end processing like the sales order agent or purchasing agent.

00:33:12.079 --> 00:33:17.279
I'm saying, like you said, even go through, take a look at all my customers with an overdue balance and block them.

00:33:17.440 --> 00:33:17.599
Right?

00:33:17.759 --> 00:33:23.359
Little simple tasks like that to help you um here's manage stuff.

00:33:24.079 --> 00:33:26.160
Here's the thing that I'm actually pretty excited about.

00:33:26.240 --> 00:33:31.039
So you so Copilot has this uh two tools that I actually really love.

00:33:31.279 --> 00:33:36.240
Uh uh one is the analyst mode, why you feed data to it.

00:33:36.319 --> 00:33:47.200
And remember how not too long ago we were like, oh, Chat GPT or uh AI couldn't crunch numbers or couldn't really grasp the numbers that you provide, right?

00:33:47.519 --> 00:33:50.640
Now the analyst mode, you can you can do that.

00:33:50.880 --> 00:33:55.200
You you give it some Excel data and it's going to give you some trends and all that stuff.

00:33:55.440 --> 00:33:56.799
There's also research mode.

00:33:57.599 --> 00:34:01.759
I would love to see, and I don't even know if I don't know if this is something that they're working on.

00:34:01.839 --> 00:34:05.039
So you know how you have analysis mode in Business Central?

00:34:05.519 --> 00:34:10.960
If they slap analyst agent within that game changer.

00:34:11.280 --> 00:34:21.840
Because it's just going to give you the trends and uh and uh things to look out for and look at patterns from your analyst mode or analysis mode in business central.

00:34:21.920 --> 00:34:29.840
So if you if they marry that together, man, that would be one of the biggest exciting features if they are going to push that.

00:34:29.920 --> 00:34:31.119
Because eventually it'll get there.

00:34:31.840 --> 00:34:33.440
Have you played have you guys played with that yet?

00:34:33.760 --> 00:34:35.440
The analyst mode and co-pilot?

00:34:36.480 --> 00:34:37.360
Uh no, not yet.

00:34:37.440 --> 00:34:40.400
I played only with analysis mode, but I I saw some videos.

00:34:40.480 --> 00:34:42.079
Uh on the co-pilot, yeah.

00:34:42.239 --> 00:34:43.280
You should check it out.

00:34:43.440 --> 00:34:55.840
So you you've you fed it with you know, it has to be like a um a database structure, uh, you know, and and you feed it and you'll say, hey, tell me, can you analyze this report?

00:34:56.000 --> 00:35:04.880
And it gives you a pretty good summary of trends and patterns and so forth, and makes you suggestion as well.

00:35:05.440 --> 00:35:12.320
And so if you could do it that way, I'm sure you could do it in Business Central at some point in the near future.

00:35:13.360 --> 00:35:25.599
I would say that real real stuff, uh this is yeah, we're using it compiled, and this is when things will explode, when you will be able to on a single click bring all your data uh under one UI.

00:35:25.840 --> 00:35:32.079
Because I was thinking, you know, if I need to go to BC to run some data analysis view, and then go to Power BI to some run some reports.

00:35:32.320 --> 00:35:36.800
I mean it's again, you know, changing the focus, changing the what I'm doing.

00:35:37.039 --> 00:35:46.480
But if I would be able, like to ask and compilate, uh, create me a report and give me an underlying data set and uh I can trust to this, that would be like crazy.

00:35:46.719 --> 00:35:51.119
Yeah, so Rita, from from your perspective, I'm curious what you think about this.

00:35:51.280 --> 00:35:57.360
So, you know, the the idea is for us to remove friction uh when someone interacting with Business Central.

00:35:57.760 --> 00:36:07.519
And a lot of times what happens is somebody has to go to an external application, for example, Power BI, or they may have a data warehouse and things like that.

00:36:08.400 --> 00:36:16.880
So if but we also have clients that, especially in the SMB space, that are it's like, why can't I just do everything within Business Central?

00:36:17.440 --> 00:36:22.960
Do you see at some point where you just do everything in Business Central, including the report?

00:36:23.039 --> 00:36:37.039
Because we know we know that there's Power BI reports now in Business Central, so you don't have to go too far, you can just have a single place to go to and just give me everything I need, including uh agents, interactions, and so forth.

00:36:37.840 --> 00:36:44.400
I mean, uh for the you end user, I think this is the way to go that I have everything under one tool.

00:36:44.559 --> 00:36:50.079
Uh either it's called business central or I can access to my uh business central data inside Power BI.

00:36:50.159 --> 00:36:55.760
And like I think that we already have this in one of the Power BI reports where you can drill down back to the BC.

00:36:56.000 --> 00:36:58.880
So I would say this is the uh the good path.

00:36:59.039 --> 00:37:00.800
Uh yes, Brent.

00:37:01.039 --> 00:37:02.239
No, no, I'm I'm waiting.

00:37:02.320 --> 00:37:06.079
I'm I'm thinking, I uh I definitely think you'll get to that point.

00:37:06.159 --> 00:37:15.360
I think this is probably where the extension of the MCP comes into play because now you'll have disconnected systems that can communicate with each other and pull the information back.

00:37:15.599 --> 00:37:19.920
And I don't know if necessarily again, this is just my thought, right?

00:37:20.079 --> 00:37:21.119
Because I do agree with you.

00:37:21.199 --> 00:37:25.840
It's almost like we have all this data, I just need one place to go to get it.

00:37:26.079 --> 00:37:32.320
Therefore, for the most part, this is why I keep saying like software becomes faceless.

00:37:32.400 --> 00:37:38.559
You're almost going to build the interface that you need at that time, if you follow what I'm saying.

00:37:38.719 --> 00:37:50.239
So if I need to do analysis, if I have a warehouse management system and I have an ERP system, because I'm I'm not using my ERP for the warehouse management system, people have disparate systems for many different reasons.

00:37:50.400 --> 00:37:52.559
But I need to do cross-reporting.

00:37:52.880 --> 00:38:05.679
Maybe you could have that, like you said, like it this is where some of that MCP um uh functionality will come into play, because now you have that information exposed in the systems who know how to speak with each other to work with it.

00:38:05.840 --> 00:38:11.360
I'll be curious to see how performance works with all these with some large data sets, and you know, everything works great with one or two records.

00:38:11.440 --> 00:38:18.480
I'd like to be curious to see when you have you know organizations that span continents and do a number of transactions.

00:38:18.960 --> 00:38:44.960
But yeah, but if you also take a look, like if you have AP agent, accounts payable agent, you receive an invoice and it will be if it will be able to process all these documents for you automatically in Business Central, and you out of output of that will be some analysis of vendor payments uh payment to our vendors, you know, you will not be able you will not need to log into BC, you will just and get a report in our BI or whatever automatically.

00:38:45.440 --> 00:38:47.119
You won't even have to go to work.

00:38:47.519 --> 00:38:50.880
You just sit on the beach and open up your phone and look at the report.

00:38:51.199 --> 00:38:54.719
Yeah, and and you will get a report, like uh you had you received 15.

00:38:54.960 --> 00:38:58.159
What says we processed successfully, oh 50, enjoy your day.

00:38:58.320 --> 00:38:59.679
You don't you are done for today.

00:39:00.079 --> 00:39:07.519
I mean, even from a report perspective, too, like you don't have to because a lot of times you look at the dashboard, a report, and you're like, okay, how do I translate this?

00:39:07.760 --> 00:39:09.199
What am I supposed to get out of this?

00:39:09.440 --> 00:39:23.840
You know, I I a lot of times I I'm sure you guys have across this too, like I've come across this too, where you interact with a C suite and it's like I want this kind of report, but at the end of the day, they don't always necessarily read it or understand it.

00:39:24.000 --> 00:39:28.800
They just want to see dashboard and they still need to be translated of okay, what am I looking at?

00:39:28.880 --> 00:39:32.639
What what do I need to do to make adjustments based upon this report?

00:39:33.199 --> 00:39:41.920
It's uh eventually you just have uh co-pilot tell you, okay, this is what it's telling you in natural language, and here's what you need to do.

00:39:42.079 --> 00:39:43.280
What do you want me to do with that?

00:39:43.360 --> 00:39:51.519
And you can just say co-pilot, go ahead and action those things, and then it'll just you know, it just works with other agents to make those adjustments.

00:39:51.920 --> 00:39:54.159
At that point, you're just gonna be a decision maker.

00:39:54.480 --> 00:39:56.960
Yes, no, I'm not sure.

00:39:57.119 --> 00:40:06.159
I mean, this is what I usually present on uh on the on my sessions at the conferences, like you know, you need to know who are your audience for the reports, and we know we have this from Kenny, right?

00:40:06.239 --> 00:40:07.360
On the Microsoft Learn.

00:40:07.519 --> 00:40:11.679
You cannot, you you know, C suite is not interested in tables and so on.

00:40:11.760 --> 00:40:13.679
They need a dashboard, as you said, Chris.

00:40:14.000 --> 00:40:19.519
And reason why is that number there, yeah, you know, and how to fix it if need to be fixed.

00:40:19.840 --> 00:40:20.320
Exactly.

00:40:21.039 --> 00:40:21.840
Yeah, yeah.

00:40:22.480 --> 00:40:24.239
Knowing your audience is important.

00:40:24.480 --> 00:40:26.159
I I start thinking about this stuff.

00:40:26.320 --> 00:40:28.480
I I almost stopped talking about it.

00:40:28.639 --> 00:40:42.320
Uh in this context, I do speak um on the podcast with it and stuff, but outside of it, sometimes I stop talking about because I think people think I'm crazy or they won't understand like what you can do with AI in a sense.

00:40:42.559 --> 00:40:46.639
Um it's uh the world is changing fast.

00:40:46.719 --> 00:40:49.519
And sometimes I go to bed and I wake up and something news here.

00:40:49.760 --> 00:41:00.159
But yes, um, like you said in the sessions, know your audience uh when it comes to anything uh that you're working on, uh whether it's reporting or even interface or functionality or usage, which is important.

00:41:00.800 --> 00:41:03.840
Um yeah.

00:41:05.920 --> 00:41:10.960
I mean, usually on our session, uh, for example, when we are doing tele, I'm doing telemetry with my colleague Milan.

00:41:11.280 --> 00:41:14.400
We ask our audience, I mean, are you developers, are you consultants?

00:41:14.480 --> 00:41:19.360
Because you know, some topics are important equally for developers and for consultants.

00:41:19.440 --> 00:41:20.000
Uh yeah.

00:41:20.320 --> 00:41:22.000
And AI is one of that as well.

00:41:22.800 --> 00:41:30.719
Well, everyone well, AI almost levels a lot of that stuff out because even if you look at like some analysis with telemetry, right?

00:41:30.880 --> 00:41:33.599
Now, you know, Waldo has his tool for telemetry.

00:41:33.679 --> 00:41:39.840
I've seen other people, you know, create some AI um uh stuff, instructions, I guess you could call them.

00:41:40.079 --> 00:41:47.440
The term changes, you know, instructions, agents, um, prompts, skills, you know, tomorrow will be something else, tasks.

00:41:47.599 --> 00:41:51.920
And you keep coming up with all the different words, but to be able to help you with analysis and consolidate it.

00:41:52.000 --> 00:42:02.800
Like I've done it, even taking logs from um my internal VPN here and just throwing it to analyze these logs and tell me what you see.

00:42:03.039 --> 00:42:08.639
You know, simplicity, and it comes back and it tells you certain information about those logs.

00:42:08.719 --> 00:42:13.280
So I don't know anything about it, I just know what it tells me it it analyzed.

00:42:13.440 --> 00:42:19.679
So and it will even be practical and give you an explanation that you even didn't think about it.

00:42:20.079 --> 00:42:23.920
Yeah, and if it doesn't have one, it will it will come up with a good sounding one too.

00:42:25.440 --> 00:42:32.159
Even if it doesn't have it, which is um um I I got a quick question for you, Renata.

00:42:32.400 --> 00:42:36.800
On on uh you know, you working in Business Central and Fabric.

00:42:37.360 --> 00:42:47.440
Um you know, clearly there's some SB folks that wants to tap into kind of a data warehouse um capability from Business Central.

00:42:48.239 --> 00:42:56.960
Do you have any uh preference in terms of like in terms of how do they, you know, what's the best way to get them into a data warehouse?

00:42:57.039 --> 00:42:58.079
Is it fabric still?

00:42:58.159 --> 00:43:05.920
I know people have said it's expensive uh or it can get it pretty expensive depending on and and how uh it gets done.

00:43:06.400 --> 00:43:13.519
Uh is there any other way for SMBs to get um a good data warehouse to get them started at least?

00:43:13.840 --> 00:43:40.639
I mean I mean to get started, I always I mean how we started uh back then when it was not fabric, we started with pulling our data uh to uh Power BI service through data flows and then building our uh let's say small warehouse for analyzing uh AP stuff in data uh through data flows in Power BI service and then building our reports on top of data flow data sets in Power BI service.

00:43:41.039 --> 00:43:42.960
So that's I would say the good approach.

00:43:43.039 --> 00:43:52.960
Uh and I can share, for example, uh one million of transactions of GL transactions we loaded from BC to uh Power BI in less than five minutes.

00:43:53.360 --> 00:43:59.679
So it's very performing well uh if you need also huge data set of one million transactions.

00:44:00.320 --> 00:44:03.920
Uh so yeah, that's uh my recommendation how to start.

00:44:04.159 --> 00:44:19.840
So Power BI service, I don't think uh it's too expensive like uh to have Power BI pro license or better use a premium and start with uh with uh building Aquarius queries and then exposing data from BC to Power BI.

00:44:20.960 --> 00:44:21.760
Okay, yeah.

00:44:22.000 --> 00:44:27.840
It's a good way to get them started because a lot of times we're like you know they want to be able to slice and dice data quickly.

00:44:28.000 --> 00:44:41.599
I mean obviously you have analysis mode and business central to get what you need, but if they want to be able to crunch numbers or maybe even pulling data from other external systems, uh you're saying it's a good way to start with just Power BI uh services.

00:44:44.800 --> 00:44:47.840
You have data full of that are working very well and reliable.

00:44:47.920 --> 00:45:02.960
We are using it like for I would say one and a half year or two, uh without public perfectly fine for for our needs, which we is analyzing general ledgers, accounts available, accounts receivables uh inside Power BI.

00:45:03.760 --> 00:45:04.400
Yeah.

00:45:05.360 --> 00:45:06.000
Excellent.

00:45:06.159 --> 00:45:07.519
There's a lot to that there.

00:45:07.679 --> 00:45:08.159
Well, Mr.

00:45:08.320 --> 00:45:13.679
Ronaldo, sir, thank you very much for taking the time to speak with us today, this morning.

00:45:13.840 --> 00:45:17.760
Uh I look forward to seeing you at some of the upcoming events.

00:45:17.920 --> 00:45:22.079
Are you going to come to Directions North America this year?

00:45:22.400 --> 00:45:22.559
No.

00:45:22.800 --> 00:45:24.800
No, no, Directions North America, no.

00:45:25.039 --> 00:45:34.079
No, uh my my trip will start with uh days of knowledge in uh in UK, and then hopefully we'll see each other.

00:45:34.320 --> 00:45:36.239
If not in Europe, then in Nashville.

00:45:36.480 --> 00:45:37.280
Oh, Nashville.

00:45:37.360 --> 00:45:38.400
Are you going to Nashville?

00:45:38.480 --> 00:45:40.639
Uh I hope I hope I will be there.

00:45:40.880 --> 00:45:42.000
Oh, I hope you'll be there too.

00:45:42.159 --> 00:45:44.400
I'm looking forward to going to Nashville in October.

00:45:45.039 --> 00:45:49.199
Um I I heard there are some promises about cost-picking engagement and so on.

00:45:51.360 --> 00:45:53.360
Yes, yes, yes.

00:45:54.400 --> 00:45:58.559
Um yeah, we'll have to get together on that uh to see.

00:45:58.719 --> 00:46:08.639
So um if anyone has any other questions or like to learn more about the content that you speak or where you'll be presenting and the content you're presenting, uh geez, we talked about a lot.

00:46:08.800 --> 00:46:11.199
FNO, Business Central, Fabric, Power BI.

00:46:11.280 --> 00:46:13.440
What's the best way to get in contact with you?

00:46:13.840 --> 00:46:19.440
I mean, it's either through LinkedIn or uh I can share my email uh with you.

00:46:19.519 --> 00:46:21.760
But as I say, I'm on LinkedIn X.

00:46:22.000 --> 00:46:24.480
Uh, you can contact me and I'll reply to your messages.

00:46:24.880 --> 00:46:25.599
Excellent, excellent.

00:46:25.679 --> 00:46:30.400
We'll put a link to your profile as well with the show on the website.

00:46:30.559 --> 00:46:31.360
Uh, thank you again.

00:46:31.599 --> 00:46:32.880
Look forward to seeing you.

00:46:32.960 --> 00:46:37.679
Uh if I don't see you before I'm gonna see you at the end of the year in Nashville, we'll have uh a lot of fun.

00:46:37.840 --> 00:46:39.039
Uh thank you again.

00:46:39.440 --> 00:46:39.679
Thank you.

00:46:43.840 --> 00:46:49.039
Thank you, Chris, for your time for another episode of In the Dynamics Corner Chair.

00:46:49.119 --> 00:46:51.199
And thank you to our guests for participating.

00:46:51.440 --> 00:46:53.039
Thank you, Brad, for your time.

00:46:53.199 --> 00:46:56.719
It is a wonderful episode of Dynamics Corner Chair.

00:46:56.880 --> 00:47:00.239
I would also like to thank our guests for join joining us.

00:47:00.400 --> 00:47:03.199
Thank you for all of our listeners tuning in as well.

00:47:03.360 --> 00:47:07.280
You can find Brad at developerlife.com.

00:47:07.440 --> 00:47:11.920
That is D V L P R L I F E dot com.

00:47:12.079 --> 00:47:17.599
And you can interact with them via Twitter, D V L P R L I F E.

00:47:18.239 --> 00:47:30.960
You can also find me at mattalino.io, m-a-t-a-l-in-o.io, and my Twitter handle is mattalino16.

00:47:31.760 --> 00:47:34.719
And see you can see those links down below in the show notes.

00:47:34.880 --> 00:47:36.079
Again, thank you everyone.

00:47:36.239 --> 00:47:38.000
Thank you, and take care.