Episode 329: In the Dynamics Corner Chair: Business Central AL Development for OGs

WEBVTT

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

00:00:06.166 --> 00:00:16.266
Whether you're a seasoned expert or just starting your journey into the world of Dynamics 365, this is your place to gain insights, learn new tricks and make development fun.

00:00:16.266 --> 00:00:18.231
I'm your co-host, chris.

00:00:18.719 --> 00:00:19.461
And this is Brad.

00:00:19.461 --> 00:00:22.908
This episode was recorded on July 5th 2024.

00:00:22.908 --> 00:00:24.591
Chris, chris, chris.

00:00:24.591 --> 00:00:30.324
Yes, I'm done with Fridays, by the way, I just have to put that out there.

00:00:30.385 --> 00:00:32.290
Another Friday, it's another Friday.

00:00:32.920 --> 00:00:35.756
But this Friday we had a great conversation.

00:00:35.756 --> 00:00:45.442
Great conversation we had the opportunity to talk with two OG dinosaurs from the community about being OG dinosaurs With us today.

00:00:45.442 --> 00:00:48.359
We had the opportunity to speak with Waldo and AJ Koffman.

00:00:48.359 --> 00:01:15.337
Good afternoon, hello.

00:01:15.337 --> 00:01:17.477
Hi how are you Great?

00:01:17.477 --> 00:01:20.447
You're not at the resort.

00:01:21.289 --> 00:01:23.245
No, no, I'm at work at the moment.

00:01:23.746 --> 00:01:30.182
Oh, I was expecting to see the fabulous background.

00:01:30.201 --> 00:01:35.112
Well, I wish I was there yeah, I do too.

00:01:35.112 --> 00:01:43.168
Christopher seems to be at some resort yes, yeah, I mean my in-laws.

00:01:43.649 --> 00:01:49.736
They have a nice setting background so it's nice and warm.

00:01:49.736 --> 00:01:53.289
Except this morning it's a little chilly.

00:01:54.400 --> 00:02:01.185
And he has the mountains, which is a nice view too, the mountains up here yeah, hello, hello, good afternoon.

00:02:01.185 --> 00:02:02.209
How are you doing?

00:02:02.359 --> 00:02:03.790
Doing fine oh wait, wait.

00:02:03.811 --> 00:02:05.040
If it's doing Hello, I'm fine, great.

00:02:05.040 --> 00:02:05.841
Oh, wait, wait.

00:02:05.841 --> 00:02:07.888
Is AJ joining, then I'm off.

00:02:10.900 --> 00:02:13.965
Okay so nice to see you, valdo Hi, aj, how are you?

00:02:17.062 --> 00:02:18.425
You never know who will show up.

00:02:18.425 --> 00:02:20.961
It's always a surprise, okay.

00:02:21.723 --> 00:02:23.028
Are there more surprises like this?

00:02:24.800 --> 00:02:25.804
We may have more.

00:02:25.804 --> 00:02:29.965
Should be honest with you, uh, I may have surprises even more.

00:02:30.246 --> 00:02:31.729
Okay, yes, yes, that's.

00:02:31.889 --> 00:02:38.330
That's what we do on friday afternoons is have a full uh, a show full of surprises or an episode full of surprises.

00:02:38.330 --> 00:02:43.788
Well, it's a friday recording chris, so I don't know, I know to see what happens.

00:02:43.807 --> 00:02:44.750
it's a Friday recording, chris, so I don't know.

00:02:44.750 --> 00:02:45.411
I don't want to see what happens.

00:02:45.431 --> 00:02:53.908
It's already started off poorly before the two of you joined, so we'll see Nothing well ever happens on Fridays when it comes to doing podcasts, I found, but we'll charge through anyway.

00:02:54.670 --> 00:02:57.431
I'd like to thank you both for taking the time to speak with us today.

00:02:57.431 --> 00:03:06.503
I've been looking forward to this conversation and I wanted to have a conversation about this for a long time and even have some more questions after seeing some things I saw posted this morning.

00:03:06.503 --> 00:03:09.561
You know you probably saw them a long time ago, but we're a little bit behind you.

00:03:09.561 --> 00:03:19.646
But I was excited to talk to you about AL developers for OGs or dinosaurs, which I saw that you were.

00:03:19.646 --> 00:03:33.064
You guys both had presented a session together at BC Tech Days recently and I thought no other perfect time to talk to somebody about that and people to talk with about that than the two of you, so I appreciate it.

00:03:33.460 --> 00:03:34.725
Because we are dinosaurs.

00:03:38.866 --> 00:03:47.180
I think you may fall into that dinosaur class, but dinosaurs are great Define dinosaurs then, but dinosaurs are great Well define dinosaurs then I mean they're extinct.

00:03:47.180 --> 00:03:52.412
True, true, true.

00:03:52.412 --> 00:03:54.948
Well, some dinosaurs still exist.

00:03:54.948 --> 00:04:02.977
Aren't alligators dinosaurs, or aren't there other animals that they consider dinosaurs, some of the other reptiles that they say have been around?

00:04:02.997 --> 00:04:03.300
for a long time.

00:04:03.300 --> 00:04:04.405
I heard they're related to chickens.

00:04:05.221 --> 00:04:07.205
They're not chickens exactly.

00:04:08.026 --> 00:04:08.306
Okay.

00:04:08.306 --> 00:04:41.848
So maybe we're not chickens, uh, but before we jump into it, for those that don't know of the dinosaurs that we are, uh, would you please take a moment to tell everyone a little bit about yourself, mr waldo sir um, I'm baldo, uh, from belgium, from Belgium, development manager at Effective Business Solutions, being in the community, or, let's say, contributing to the community for quite some time, being MVP for somewhat like 16 years.

00:04:44.744 --> 00:04:46.005
Yeah, I'm still doing what.

00:04:46.045 --> 00:04:47.848
I do Excellent.

00:04:47.848 --> 00:04:49.690
16 years, that's a long time.

00:04:50.411 --> 00:04:51.052
Or 17.

00:04:51.533 --> 00:04:53.216
17 years, 17 years Wow.

00:04:53.959 --> 00:04:55.305
There must be, something like that yeah.

00:04:55.846 --> 00:04:58.608
That's a very long time, so when did you start working with AL development?

00:04:59.961 --> 00:05:01.846
I started in 2001.

00:05:02.346 --> 00:05:03.269
2001.

00:05:03.269 --> 00:05:04.312
Wow, that is a long time.

00:05:04.351 --> 00:05:06.665
Yes, and then I ran away from it.

00:05:07.901 --> 00:05:08.685
Why did you run away from?

00:05:08.745 --> 00:05:08.785
it.

00:05:08.785 --> 00:05:10.826
This was not what I wanted to do.

00:05:10.826 --> 00:05:15.651
I actually wanted to do like C-sharp kind of development.

00:05:15.651 --> 00:05:22.553
So I ran away and then my new company asked me hey, you have experience in Navision, do you want to do it?

00:05:22.553 --> 00:05:27.509
In my company I was like, okay, I, I'll try.

00:05:27.528 --> 00:05:32.144
So that's kind of like yeah, it seems that happens to all of us.

00:05:32.144 --> 00:05:42.759
I ran away to go for a year to go work at a company managing a c-sharp development group and product and then after a year I got pulled back into it as well.

00:05:42.759 --> 00:05:47.351
It seems like it's one of those things once Once you join, you can never leave, as they say.

00:05:47.351 --> 00:05:52.550
Mr AJ, sir, you tell us a little bit about yourself please.

00:05:54.319 --> 00:06:06.869
I joined the business Central World, I think about one year later it was in 2002.

00:06:06.869 --> 00:06:09.533
Rookie, sorry.

00:06:09.533 --> 00:06:11.225
So what was that, waller?

00:06:11.225 --> 00:06:11.968
Sorry?

00:06:11.968 --> 00:06:15.949
By the way, everybody calls me AJ.

00:06:15.949 --> 00:06:31.065
My official name is Arjen Jan, but it seems to be difficult outside of any Dutch-speaking countries countries, and there are not so many of them, so they renamed me into AJ.

00:06:31.065 --> 00:06:35.514
That's fine, I listen to AJ as well.

00:06:38.300 --> 00:06:53.029
I'm currently working as a CTO for Lumos 365, a UK-based company, and we are, of course, an ISV partner in the business central world.

00:06:53.029 --> 00:07:16.211
I started back in 2002 and, yeah, quickly found out about the community and started contributing a couple of years later, actually encouraged by the famous luke van vugt, who actually taught me cal development back in 2002.

00:07:16.211 --> 00:07:26.591
I was in his classes, wow, and actually my my hometown like where he was at that time an employee of Navision Netherlands.

00:07:26.591 --> 00:07:46.127
So, yeah, actually I came in the Navision world back then as being a C-sharp developer and the idea was that I was going to do something about integrating web shops, portals, whatnot.

00:07:46.127 --> 00:07:54.846
But yeah, actually I was dragged away into the CL world and I'm still here.

00:07:55.680 --> 00:07:57.005
Yeah, well, happy that you're here.

00:07:57.005 --> 00:08:10.581
It's odd to hear someone come from the C-shop world at least in my experience into Navision way back in the day, because I know a lot of people came from Pascal or Delphi or they worked with those types of languages.

00:08:10.581 --> 00:08:22.052
You know, at least when I started, back when I was a young a young boy so going from C sharp at that point to Navision must have been quite an adjustment for you, to say the least.

00:08:22.701 --> 00:08:33.634
I did my traineeship in 2000 in um in c++ I think it was portland c++ 4 or something like that.

00:08:33.634 --> 00:08:36.720
I did my traineeship and I absolutely loved it.

00:08:36.720 --> 00:08:42.423
Uh, and that was where I was like, yeah, this is what I'm gonna do like the rest of my life and day one.

00:08:44.889 --> 00:09:00.437
It was decided differently, so it's good we're happy that you're both uh in the community and working with, and the al language has been an evolving language rapidly, or had been evolving rapidly over the past several months.

00:09:00.437 --> 00:09:14.596
It took several years for them to get to this, but the momentum seems to go, gets moving, and, uh, one of the things to talk about is we talk about and I had conversations with you before about um, you know what are the changes to the al language.

00:09:14.596 --> 00:09:17.102
You know how rapid they're coming, where's the language going?

00:09:17.102 --> 00:09:22.453
And then also, for us ogs, how do you keep up with it?

00:09:22.453 --> 00:09:41.292
You know, how do you keep up with a language that's been more or less Pascal-based for its entire existence and now, over the past couple of years, it seems to be moving more and more towards a NET language or a C-sharp type language if you look at what they're adding to it.

00:09:41.852 --> 00:09:45.847
In my opinion, it's starting to look really cool.

00:09:45.847 --> 00:09:48.274
Yes, yeah, absolutely.

00:09:48.274 --> 00:09:53.371
Actually, I don't know if you know Stefan Maron.

00:09:53.371 --> 00:10:11.032
He started some kind of series on YouTube or live coding thing and I attended actually yesterday because I was triggered in the tweet that he did and he did some clever things with something that's coming up with the disk keyword.

00:10:11.032 --> 00:10:20.214
It was pretty interesting to see where AL is going on that as well.

00:10:20.214 --> 00:10:21.216
Yeah, absolutely.

00:10:21.657 --> 00:10:23.340
Yeah, I saw that too and I saw your comments.

00:10:23.340 --> 00:10:26.004
I did watch that with the EverInfo rapper.

00:10:26.004 --> 00:10:35.392
Rapper, I think is what he was talking about yesterday, and then I saw this morning that you know the message that's in the preview for al about the tyranny, tyranny.

00:10:35.392 --> 00:10:36.761
How do you say that tyranny?

00:10:37.563 --> 00:10:42.573
I can't even pronounce it, uh you know there are any conditions, or what is it?

00:10:42.720 --> 00:10:44.345
yes, yes, within al.

00:10:44.345 --> 00:10:50.725
So now you'll be able to do the question mark like the C-sharp language and I'm just I think it's going more.

00:10:50.725 --> 00:10:56.808
So let's go back to what you had talked about at BC Tech Days with AL development for OGs.

00:10:56.808 --> 00:11:08.082
What are some of the most recent enhancements, or enhancements that you like, about AL, the AL language and development as it's gone through, as you kind of talked about with your presentation?

00:11:11.511 --> 00:11:24.191
AJ, the idea is actually to go over a number of topics not actually related to each other.

00:11:24.191 --> 00:11:45.191
Well, they are related because they are all about AL and business central development, but topics that actually change for those who bridge the gap between seaside and CIL development to business central and AL development.

00:11:45.191 --> 00:11:48.408
You have a number of changes there.

00:11:48.408 --> 00:11:55.991
It's not just a different language, but the whole development experience is changing.

00:11:55.991 --> 00:12:24.192
So Waldo and I were actually kind of listing topics that are changing over time and changing for those who take that, the step towards IELTS development, and we came up with a list that we could probably talk for a whole day, more than maybe even two days, if you give us the time.

00:12:25.019 --> 00:12:26.446
Oh, we have two days' worth of time.

00:12:26.446 --> 00:12:27.328
It's Friday.

00:12:29.380 --> 00:12:33.667
And we have done this session now a couple of times and we always run out of time.

00:12:33.667 --> 00:12:41.225
The first session, it happens because I took too much time on one of the topics.

00:12:41.225 --> 00:12:42.509
Second as well.

00:12:42.509 --> 00:12:48.543
Second time, it happened to Waldo taking too much time because we switched the topics a little bit.

00:12:48.543 --> 00:12:54.489
Okay, now, waldo, you go first because I'll take the remaining time, whereas there was none.

00:12:56.461 --> 00:12:57.525
That happens whenever.

00:12:57.525 --> 00:13:01.008
Who has the word first, he has most time.

00:13:01.909 --> 00:13:24.246
Yeah, but those topics are both in AL, like what is changing in AL we have a lot more in AL you can use than you had in the past with CAL but also about the overall development experience.

00:13:24.246 --> 00:13:29.230
We have a completely different development environment.

00:13:29.230 --> 00:13:33.609
Vs Code the process is different.

00:13:33.609 --> 00:13:37.250
You're not changing the base code anymore.

00:13:37.250 --> 00:13:41.940
You're extending the base code but you don't touch the base code.

00:13:41.940 --> 00:13:44.052
It was completely different in the past, where you don't touch the base code.

00:13:44.052 --> 00:13:59.644
It was completely different in the past around everything that you have in automated tests, in pipelines, dev ops and all of that and I have the feeling of it just spreads the surface in our session.

00:14:00.440 --> 00:14:05.100
No, I can imagine there are so many changes now that you're putting it in a list like that.

00:14:05.100 --> 00:14:15.716
Just to think from someone who has been working with it since back in early 2000s or the late 1990s when the language was really there.

00:14:15.716 --> 00:14:28.750
I know when it first came to the US was in the late 1990s when developers started working with it, when you had the optic designer built within the application, and now, as you'd mentioned, you're over now into using VS Code to develop an AL extension.

00:14:31.081 --> 00:14:43.653
And the nice thing is, in a session like that, it's very recognizable to touch whatever we are coming from, because everyone who is there, or most of the people who is there, is an OG, is a everyone.

00:14:43.653 --> 00:14:48.110
Everyone who was there, or most of them, most of the people who was there is an OG, is a dinosaur right.

00:14:48.110 --> 00:14:56.687
And whatever you talk about, like do you remember the object designer and do you remember how we did source control?

00:14:56.687 --> 00:14:57.610
We didn't.

00:14:58.591 --> 00:14:58.971
Or who did.

00:14:59.011 --> 00:15:22.110
I was going to say and so that is actually always a very nice touch point, like to uh to emphasize how much we progressed since back in the days and it's I mean I just came to it during the session but uh, it was always called the object designer or the way we did our stuff.

00:15:22.110 --> 00:15:42.736
Uh, it was always called simplicity and that was I was always called simplicity and that was I always hated that word, always, like from the first day that I did Navision, or because I mean whatever is simple to do, probably we are doing something wrong at that point or we are not doing enough.

00:15:42.736 --> 00:15:52.039
And the reason why it was simple it was simply because we were not able to do the basic stuff we should be doing as software developers.

00:15:52.039 --> 00:16:13.315
So it was not simplicity, it was stupidity kind of thing, right, and now we have progressed so much already it is actually quite interesting to keep looking back to, okay, but do you remember, like like 15 years ago, like we weren't evil, we didn't even have like intellisense, right?

00:16:13.315 --> 00:16:18.163
Um, so, yeah, how, how we have progressed.

00:16:18.183 --> 00:16:30.346
This is it makes it an interesting session and it's, like AJ says, like we had an insane amount of topics and our first challenge was what do we take what.

00:16:30.346 --> 00:16:31.669
What are we going to talk about?

00:16:31.669 --> 00:16:45.245
Because we can talk about pretty much many days about this um and the idea lives that we would be doing and following up session maybe next year or two year after, something like that.

00:16:45.326 --> 00:16:53.158
What I find interesting, though, is there are also many new developers.

00:16:53.158 --> 00:17:40.568
Many people are new in the channel, new to AL development, and you would maybe think that those who maybe think that those who, let's say, the OGs, who work with Business Central, they are kind of behind because they need to learn new technologies, but I find that people who join Business Central today or, let's say, two or three years ago, they are kind of lagging behind on knowledge about knowledge of the product behind it, about Business Central how does Business Central work, and I see many questions that are actually around topics that we all were used to as OGs, and that still applies to today.

00:17:40.568 --> 00:17:44.426
I don't know if you have the same experience well, over there.

00:17:44.426 --> 00:17:58.465
It's a question about how do I create a record, or how do I work with a customer record versus a contact, versus a sales head, or whatever these kind of things.

00:17:58.465 --> 00:18:00.432
It's obvious now.

00:18:02.969 --> 00:18:09.144
It's the old question like how functional should the developer be and how technical should the consultant be?

00:18:09.144 --> 00:18:19.246
I think that's kind of like I'm less abstract in that, to be honest, or maybe even more abstract in that.

00:18:19.246 --> 00:18:21.045
You are abstract in that.

00:18:21.045 --> 00:18:36.256
Yeah, in my opinion, there should be a very thick line that I should not cross as a developer, as being a consultant, you know, because I would not like consultants to cross the development line either.

00:18:36.256 --> 00:18:59.067
That doesn't mean we shouldn't have knowledge, right, I need to know what an invoice is and how an invoice is posted and how, what a ledger entry is, and now I can get to the data, how much I normalize my data and how I shouldn't be doing that and why and that's all an ERP kind of reason on doing stuff.

00:18:59.067 --> 00:19:03.431
But yeah, it's hard to explain.

00:19:03.471 --> 00:19:05.933
But no, I understand that.

00:19:05.933 --> 00:19:11.364
That is a challenge that I see and it's also, I think, the line.

00:19:11.364 --> 00:19:23.573
When we first started there really wasn't a line because the application itself, as you said, was simple and there weren't that many, you know, people implementing it or working with it.

00:19:23.573 --> 00:19:27.471
So a developer and a functional consultant did cross that line.

00:19:27.471 --> 00:19:30.148
So you kind of did all of the same roles.

00:19:30.148 --> 00:19:51.746
I know early on when we first started, the partner I started at there was a few of us that worked on this and we had to do pretty much everything, and it wasn't until years had progressed where they started to become more and more users of the application, which involved, which therefore led to having more need for someone to implement or develop or work with it.

00:19:51.746 --> 00:19:58.749
I think that line again, if you deal with the OGs, a lot of people still don't have that line.

00:19:58.749 --> 00:20:06.365
They think that a lot of the functional consultants or technical consultants may think that they can develop the same way like they did years ago because they knew enough then.

00:20:06.365 --> 00:20:09.186
But I think now Enough.

00:20:09.449 --> 00:20:13.709
right, that's the simplicity that I'm struggling with, you know.

00:20:13.709 --> 00:20:19.028
Just as an example, yesterday I had a meeting with a customer.

00:20:19.028 --> 00:20:24.767
He was seeking advice to someone who had knowledge on NAV5.

00:20:24.767 --> 00:20:40.088
And I mean, I'm part of an organization uh, I'm, I'm actually a small company in a bigger hall kind of thing and the bigger hall found that customer and if was trying to find some knowledge in the bigger organization.

00:20:40.088 --> 00:20:47.348
So that came to me like I was like no, no, please, no, okay, I'll have a talk with the customer.

00:20:47.348 --> 00:20:58.859
And the first thing he says, like look, we are very happy with our NAV5 database, but now we want to do Power Automate.

00:20:58.859 --> 00:21:07.526
And I was like no, you're not happy with your five database or NAV5 database, because functionally it might work but you cannot extend it, so you're not happy.

00:21:07.526 --> 00:21:12.306
The bottleneck is exactly what you're happy about and you're not happy about it.

00:21:12.306 --> 00:21:13.945
The answer would be pretty simple.

00:21:14.421 --> 00:21:18.286
I'm going to make you not happy by saying Power Automate is out of the question.

00:21:19.789 --> 00:21:20.912
Yeah, I did that.

00:21:20.912 --> 00:21:25.247
And then I just asked let me have a look.

00:21:25.247 --> 00:21:29.131
And I mean I shouldn't have asked.

00:21:29.131 --> 00:21:31.180
So you see the object design.

00:21:31.180 --> 00:21:42.913
You just see basically every single object being touched at some point by a developer and you see very physically the simplicity that we don't have anymore.

00:21:42.913 --> 00:21:45.631
And he asked me, like you're the expert, how can you upgrade this?

00:21:45.631 --> 00:21:46.103
And the simple answer is we can't have anymore.

00:21:46.103 --> 00:21:46.448
And he asked me, like you're the expert, how can you upgrade this?

00:21:46.448 --> 00:21:51.210
And the simple answer is we can't, we cannot help you anymore.

00:21:51.210 --> 00:21:54.107
And the reason is simplicity.

00:21:54.107 --> 00:21:55.290
You know what I mean?

00:21:55.290 --> 00:22:04.865
Because we have been able to do what we shouldn't have been able to do for years and years and years and years on your database.

00:22:04.865 --> 00:22:11.480
And people did that, and now it's completely a big mess, so you're helpless yeah, but.

00:22:11.760 --> 00:22:11.921
But?

00:22:11.921 --> 00:22:33.467
But here the point is that those developers who were used to that simplicity are struggling with moving towards business central, where you do not have the same level of simplicity, or should I maybe say, uh, flexibility?

00:22:33.467 --> 00:22:48.188
Um, because, yeah, you simply cannot touch the database, not that the, the base application, and that is a concept that they need to get used to, which was actually part of the session that we have.

00:22:48.188 --> 00:22:54.048
And for some, for some, it's, it's, it's hard.

00:22:54.048 --> 00:23:00.228
Others are like finally, now I don't have to.

00:23:00.228 --> 00:23:19.682
But yeah, I mean, okay, I'm going to admit that in the beginning, in the very beginning of al and creating extensions, it took me some time to get used to the idea that I cannot touch the base application.

00:23:19.682 --> 00:23:21.945
I had to get used to that.

00:23:21.945 --> 00:23:24.551
Now I cannot imagine how.

00:23:25.981 --> 00:23:26.703
I need to shut up.

00:23:26.703 --> 00:23:30.886
Say again Now I'm going to try to not.

00:23:32.321 --> 00:23:33.246
No, no, don't hold back.

00:23:33.246 --> 00:23:36.489
It's Friday, we need to get it all out, don't hold back at all.

00:23:36.661 --> 00:23:37.605
Don't be honest, Waldo.

00:23:37.605 --> 00:23:39.465
You're not in the same position.

00:23:39.988 --> 00:23:42.463
No, yes, yes and no.

00:23:42.463 --> 00:23:59.211
The thing is, I have been one of the big adversaries or how do you say it in English of anything hybrid and anything that comes close to changing the base app right.

00:23:59.211 --> 00:24:19.509
So the code-customized base app or hybrid development, where you had some AL and some CAL in one implementation, I've been like from the starters being advocating like don't do it, don't ever do it, do not go that way, ever, ever.

00:24:19.509 --> 00:24:50.930
If you just want to do AL just because it's cool and back in the days like NAV 2018, bc14, it was just cool Because it didn't contribute to the complete supportability of an implementation very well actually, because it was actually quite hard to do I would say don't do it, just everything C-AL and then make it convertible toL at some point when you can, but don't mix and match, don't do the code customized base at some point.

00:24:50.930 --> 00:25:00.134
And I remember distinctively in the entire community that I was quite alone in that space.

00:25:01.061 --> 00:25:02.386
I remember that a lot as well.

00:25:02.386 --> 00:25:04.867
We had some discussions.

00:25:05.299 --> 00:25:14.434
Yes, isn't that caused by OG dinosaur developers that are just like, hey, I can still do it.

00:25:14.434 --> 00:25:17.965
I might as well just do it for now, worry about it later.

00:25:18.508 --> 00:25:27.101
I think that was a common thing, yeah, and that's where I started to uh shout like, just because you can doesn't mean you should.

00:25:27.101 --> 00:25:28.987
And now there is a sticker.

00:25:28.987 --> 00:25:30.490
I have a sticker on that on my lap.

00:25:30.490 --> 00:25:31.773
I need one of those.

00:25:33.703 --> 00:25:37.613
I've always been an advocate of that people want to do things because it's cool.

00:25:37.613 --> 00:25:42.587
It's the new shiny object, but it may not be the most practical solution or the best solution at the time.

00:25:44.191 --> 00:25:48.308
It was also something about feeling to be in control.

00:25:48.308 --> 00:25:56.327
You're not always happy with what the base app does or what the code is doing there.

00:25:56.327 --> 00:26:05.164
You will always be able to change that behavior, out-of-the-box behavior.

00:26:05.164 --> 00:26:17.353
Now you're depending on what Microsoft delivers as an event possibilities to override or bypass certain pieces.

00:26:17.353 --> 00:26:29.327
If there is no possibility for that, for whatever reason, you need to ask for it and hopefully they're going to grant you that request.

00:26:29.327 --> 00:26:37.303
Or you're just blocked from accessing certain tables because it's on-prem and you cannot touch it.

00:26:37.303 --> 00:26:40.290
I mean, I ran into that today.

00:26:40.290 --> 00:26:44.541
I wanted to do something that I really cannot imagine by.

00:26:44.541 --> 00:26:55.971
Microsoft would have this particular table as on-prem, but hey, it is on-prem and there is no interface that helps me doing something with the data in that table.

00:26:57.220 --> 00:26:59.528
Yeah, it's a daily challenge for many people.

00:27:02.662 --> 00:27:12.314
Yeah, and for a moment I was thinking, okay, if I could only have this database on-prem for 10 minutes, I could do what I needed to and then go off.

00:27:12.314 --> 00:27:14.643
It's a one-time thing anyway.

00:27:14.643 --> 00:27:19.535
But yeah, it is what it is.

00:27:19.535 --> 00:27:29.028
We have to live with the hardcomings, the limitations.

00:27:29.028 --> 00:27:29.510
I would say.

00:27:30.925 --> 00:27:33.974
Yeah, but it's also they do add a lot to it.

00:27:33.974 --> 00:27:38.432
I mean, I do like the simplicity of what we had with the vision and the development.

00:27:38.432 --> 00:27:42.777
I also greatly appreciate and enjoy what we can do with AL.

00:27:42.777 --> 00:27:44.592
I'm a big fan of the extension base.

00:27:44.592 --> 00:27:55.586
It does allow you to migrate from version to version and do quite a bit more with source control management pipelines a lot of things that back before we kind of just, you know, simply threw in.

00:27:55.586 --> 00:28:04.090
You know, just threw some code into some stuff and, you know, had it worked, you didn't like the functionality, you didn't understand the functionality.

00:28:04.090 --> 00:28:04.446
It goes back to.

00:28:04.467 --> 00:28:08.750
What we were talking about is how much should a developer understand about the functional areas of the application?

00:28:08.750 --> 00:28:12.352
You know, in order for you to develop it, you do have to have some level of understanding.

00:28:12.352 --> 00:28:15.565
With flow, I know over the years I worked on some limitations.

00:28:15.565 --> 00:28:28.612
Somebody didn't clearly understand how the sales order processing worked within the vision or dynamics nav and they just created their own sales order entry process because somebody wanted one small feature and they didn't, you know, want to modify that.

00:28:29.433 --> 00:28:29.595
Um.

00:28:29.595 --> 00:28:38.712
So but with all of the changes that are occurring, um, how do you keep up with it?

00:28:38.712 --> 00:28:41.096
You know, how can someone keep up with it?

00:28:41.096 --> 00:28:43.000
How can someone keep up with it?

00:28:43.000 --> 00:28:54.895
There's younger talent that's now coming into the community that we have, that is, they sit side by side with some of the dinosaurs and they don't understand or they don't even know.

00:28:54.895 --> 00:28:56.612
I know I talk with some of the younger talent.

00:28:56.612 --> 00:29:01.105
I mentioned some things and they've never even heard of it before or they never even thought of it before.

00:29:01.105 --> 00:29:03.534
So they're used to working and developing a contemporary manner.

00:29:03.534 --> 00:29:14.980
So then you have some of the, the OG guys that you need to understand the application and how to work with it.

00:29:16.746 --> 00:29:20.976
Well, I'm curious, though, because I'm seeing this quite a bit.

00:29:20.976 --> 00:29:38.948
Well, I'm curious, though, because I'm seeing this quite a bit, and while Brad's doing, his thing.

00:29:38.968 --> 00:29:39.169
do you see?

00:29:39.169 --> 00:29:42.143
Some OG developers and even some functionals that used to be able to do development fall out or fall off of the wagon as AL progresses.

00:29:42.143 --> 00:29:48.690
Honestly, not really Okay, I think I.

00:29:48.711 --> 00:29:57.695
So, yeah you go, let me say that it's not more than I witnessed in the CAL world.

00:29:57.695 --> 00:30:10.972
I remember a developer who, in the CAL world, I remember a developer who in the CAL world, actually at some point said I'm done, there are so many different changes.

00:30:10.972 --> 00:30:14.794
Every release which then back in the days, came out every two years.

00:30:14.794 --> 00:30:22.675
But he could not follow and he said, well, I'm going to be a functional consultant instead.

00:30:22.675 --> 00:30:29.846
And today he's still an application manager for Business Central and a customer.

00:30:29.846 --> 00:30:33.497
But there is just an exception.

00:30:33.497 --> 00:30:44.699
I mean, most of the developers keep up, or at least partly, but what I see is that most of them are more and more specialized.

00:30:44.699 --> 00:31:06.512
You have the developers who specialize in everything around projects, jobs, or everything around manufacturing, or around inventory and item tracking and whatnot, or finance or reporting, if there is any developer who likes it.

00:31:06.512 --> 00:31:14.471
So they're more specialized in a certain area, or two or three areas, but not all of it.

00:31:14.471 --> 00:31:19.756
Okay, that used to be different in the past, okay.

00:31:21.529 --> 00:31:22.071
I agree with that.

00:31:22.585 --> 00:31:30.493
Because I've come across some developers that are just struggling to yeah, like even right now keep up with some of the new features.

00:31:30.493 --> 00:31:36.913
But I think just knowing, based on their history, are typically where they can do all of it.

00:31:36.913 --> 00:31:40.154
Now they're having to pick in one area to be good at.

00:31:40.154 --> 00:31:49.693
I think that's what you're saying, aj is that you've got to be more of a specialist with the modern AL.

00:31:51.857 --> 00:31:52.259
Absolutely.

00:31:52.259 --> 00:32:01.630
Actually, when Brad asked the question how you keep up, we don't, or at least I don't.

00:32:01.630 --> 00:32:04.054
I don't keep up with everything.

00:32:04.054 --> 00:32:05.570
It's as simple as that.

00:32:05.570 --> 00:32:13.351
I just pick my things that I try to be good at and that's where I will specialize in.

00:32:13.351 --> 00:32:19.173
You pick your battles Mostly stuff that I need in my daily job.

00:32:19.173 --> 00:32:25.832
Like last year, I've been diving a lot into telemetry because simply, I needed it.

00:32:25.832 --> 00:32:41.991
We had a big problem at a customer and now we are extending that to following up on the product and all that performance, but also just application stability and all that with telemetry, and try to now make that available to the entire team as well.

00:32:41.991 --> 00:32:44.192
So yeah, then you need to dive into that.

00:32:45.144 --> 00:32:50.096
Yeah, just based on the need is when you're diving into.

00:32:50.096 --> 00:32:54.497
Okay, what are the features based on my need and what can I do with it?

00:32:54.497 --> 00:32:56.383
Okay, All right.

00:32:57.045 --> 00:32:58.873
This is the funny thing, actually.

00:32:58.873 --> 00:33:10.972
So, while there'll be an example here, but I've seen that with more people For a while, I think, more and more involved with telemetry.

00:33:10.972 --> 00:33:30.976
And now you're appointed kind of an expert and I mean, yeah, look at your session at Tech Days.

00:33:30.976 --> 00:33:39.191
I mean that means that you quickly evolved over, let's say, a year, while telemetry was already there.

00:33:39.191 --> 00:33:40.974
For what is it?

00:33:40.974 --> 00:33:41.817
Two, three years.

00:33:43.748 --> 00:33:44.932
So in the beginning you ignore it.

00:33:44.932 --> 00:33:45.714
I think BC16.

00:33:45.714 --> 00:33:55.935
In the beginning you ignore it and now you're jumping onto it and I see that personally.

00:33:55.935 --> 00:34:11.795
I mean there are topics that I ignored for a while and then at some point it becomes relevant and then I jump onto it and say, okay, now I'm going to learn everything that is around this, which means that you have to leave other things go.

00:34:11.795 --> 00:34:28.233
I mean you have a certain number of hours in a day, right, but yeah, there are so many other topics that I would love to learn more about, and I think that goes for every developer and every technical person in the Business Central world.

00:34:28.233 --> 00:34:35.831
Yeah, it could be that next year you're doing something completely different still in Business Central.

00:34:37.065 --> 00:34:38.030
Just a different focus.

00:34:38.030 --> 00:34:44.744
Have you guys gotten into designing your extension that could work with Power Platform?

00:34:44.744 --> 00:34:54.876
It seems that you know we've had some I've come across some of the developers where they're starting to think about Power Platform.

00:34:54.876 --> 00:34:58.615
How can a Power Platform consume my extension?

00:34:58.615 --> 00:35:00.532
Have you guys gotten into that space yet?

00:35:11.224 --> 00:35:12.467
Actually the last couple of months.

00:35:12.467 --> 00:35:16.393
Uh, we have because we, we are developing a product for another company involving power platform.

00:35:16.393 --> 00:35:19.920
Uh, power apps, if I, if I'm not mistaken, could be canvas apps.

00:35:19.920 --> 00:35:31.027
I think, canvas apps with business central and a quite high level or quite no, not high level deep down integration to it.

00:35:31.027 --> 00:35:37.076
So, yes, learn new stuff.

00:35:43.244 --> 00:35:44.347
Yeah, I've been in the same place.

00:35:44.347 --> 00:35:52.019
A couple of years ago, I actually created a Canvas app from scratch with Business Central data.

00:35:52.019 --> 00:36:01.235
Back in the days we did not have synchronization to Dataverse, so everything was working with APIs directly on Business Central.

00:36:01.235 --> 00:36:03.159
Yeah, I've been there, so everything was working with API directly on Business Central.

00:36:03.159 --> 00:36:12.369
And these days I'm quite deep into Power, automate and approval flows and many things.

00:36:12.369 --> 00:36:12.771
You think.

00:36:12.771 --> 00:36:18.233
How could I even think that this is a good idea?

00:36:20.711 --> 00:36:28.230
I spent the better half of the day on Wednesday in Power Automate and my conclusion is not my happy place.

00:36:30.648 --> 00:36:55.376
I have a session that goes like lessons learned from using Power Automate with especially focused on approvals, and one of the first slides is like because you can does not mean you should, and what I'm saying there is hey, look, you can do a lot in Power Automate.

00:36:55.376 --> 00:36:56.851
You can in Power Automate.

00:36:56.851 --> 00:37:06.733
Maybe you can maybe replace a complete code unit of kind of functions in Power Automate and you can maybe replace a complete code unit with kind of functions in Power Automate and expose the APIs and do everything in Power Automate.

00:37:06.733 --> 00:37:11.831
But because you can do that, it doesn't mean that it is a good idea to do that.

00:37:11.831 --> 00:37:19.730
But hey, if you are a Power Automate developer, then you're doing it in a way.

00:37:19.730 --> 00:37:23.873
I mean, if you have a hammer, every problem looks like a nail.

00:37:23.873 --> 00:37:24.576
That's simple.

00:37:27.425 --> 00:37:48.318
Yeah, I'm always curious about that, for, you know, I struggled in getting into part automate myself because then at that time I didn't know how to manage diversions of it and because it was such an easy access to many I mean, it was kind of sold.

00:37:48.318 --> 00:37:52.891
You know, it's like, hey, anyone can do this, right, it's just plug and play.

00:37:52.891 --> 00:37:56.333
And it created a bunch of different power automate that you.

00:37:56.333 --> 00:37:59.494
You know, people didn't have visibility of who created what.

00:37:59.494 --> 00:38:03.384
You know, people didn't have visibility of who created what.

00:38:03.384 --> 00:38:09.525
And then whenever someone leaves, then it would, you know, someone would complain that, hey, something stopped working.

00:38:09.525 --> 00:38:13.710
Well, someone created a Power Automate, so you didn't get that visibility.

00:38:13.710 --> 00:38:27.711
You know, of course there's some methods around that now, but you know, but it kind of created that just like similar to what you're saying Waldo, nav 2018 in BC14, where you could do it.

00:38:27.711 --> 00:38:36.570
I mean, it was a habit that many had and now they have to kind of break out of that and just build in extensions.

00:38:38.034 --> 00:38:40.576
But yeah, A funny question, or funny just an observation maybe.

00:38:40.576 --> 00:38:40.938
But if you have.

00:38:40.938 --> 00:38:43.945
But yeah, funny question, just an observation maybe.

00:38:43.945 --> 00:38:58.313
But if you have AL developers not knowing a lot about Power Automate, for example, and you have a Power Automate, they're not called developers because there's no code, right?

00:38:58.313 --> 00:39:02.657
Citizen, developers Citizen developers but the citizen developer has developer because there's no code right.

00:39:02.677 --> 00:39:03.442
Citizen developer.

00:39:03.461 --> 00:39:03.804
Citizen developer.

00:39:03.804 --> 00:39:11.951
But the citizen developer has no clue about AL code, and now you need to come up with something.

00:39:11.951 --> 00:39:37.342
If you would ask the two persons individually how you're going to solve this problem, you are going to get completely different solutions, and if you put them together in a room, it will probably still be hard for them to come up with something that they both feel confident in and confident in.

00:39:37.342 --> 00:39:39.170
This is a lot of.

00:39:42.172 --> 00:39:43.358
That would be a fun exercise.

00:39:43.358 --> 00:39:49.411
That would be a fun exercise for anything, for anything.

00:39:49.431 --> 00:39:53.315
Solution Christopher actually put the finger on the wound.

00:39:53.315 --> 00:39:54.967
I don't know if that's an English expression.

00:39:54.967 --> 00:40:00.550
That's how we say it in Dutch salt in the wound yes, salt in the wound, or finger in the wound?

00:40:00.570 --> 00:40:02.664
no, not really, or finger in the wound.

00:40:02.664 --> 00:40:20.264
The thing is that whatever you do, power related just as a citizen developer, and a citizen developer only you basically make it break the moment you leave the company.

00:40:20.264 --> 00:40:40.088
And if you do not make sure that you set it up correctly and then we're already talking more technical than the average citizen developer is capable of well, then then yeah, if you want to set it up correctly, then you have a decent setup.

00:40:40.088 --> 00:40:42.795
You need to set up, I mean and maintain and all that.

00:40:42.795 --> 00:40:44.289
It's not easy.

00:40:45.469 --> 00:41:05.735
I always compare it with Word, like if any customer wants us to do anything power, I'm always telling them no, simple, I can help you, but it's your solution and you're going to have to maintain it and all that.

00:41:05.735 --> 00:41:07.771
Right, it's the same as Word.

00:41:07.771 --> 00:41:09.552
I'm not going to write your document.

00:41:09.552 --> 00:41:14.552
I can tell you how to write the document, but I'm not going to write it, you know.

00:41:14.552 --> 00:41:23.496
So your Power Automate solution, your whatever solution, power App, whatever you come up with, it's your solution.

00:41:23.496 --> 00:41:29.010
I can create a template for you, whatever, but that's it, and you're going to deploy it.

00:41:29.010 --> 00:41:35.585
You're going to have to maintain it and if someone leaves, you're going to have to manage it you know what I mean and that is.

00:41:35.606 --> 00:41:38.527
I mean there are ways around that.

00:41:38.527 --> 00:41:49.657
I mean there are ways around that With DevOps you can set up pipelines implementing on a decent way the deployment of Power Apps and Power Automates.

00:41:49.657 --> 00:41:50.777
It's not easy.

00:41:50.777 --> 00:41:56.902
The Power Platform is getting there, is really getting there, but it's not easy at the moment.

00:41:56.902 --> 00:42:03.766
But it is possible and you can get your way around that so that things are managed in a certain way.

00:42:03.766 --> 00:42:13.898
But I can, I can promise you out of the box are are mostly at companies.

00:42:13.898 --> 00:42:39.887
This is not managed and this is very much unmanaged, and there are things running at local accounts that you don't know of and things happen to go very well and then all of a sudden they don't, and then figuring out why it doesn't run anymore when there are a gazillion power automates spread over multiple accounts running and not running anymore.

00:42:39.887 --> 00:42:39.947
I don't know.

00:42:39.947 --> 00:42:42.016
And that's what we are creating in that, if we are not careful, power Automate spread over multiple accounts running and not running anymore.

00:42:41.971 --> 00:42:48.880
I don't know, yeah, and that's what we are creating in that if we are not careful, if they are not careful because we actually don't know, right?

00:42:49.501 --> 00:42:52.974
No, you see, people leave and everything stops working.

00:42:52.974 --> 00:42:56.675
I can't tell you how many times I hear those questions that this stopped working.

00:42:56.675 --> 00:42:58.251
You found out, somebody set something up.

00:43:00.088 --> 00:43:00.751
So it goes back to.

00:43:00.751 --> 00:43:02.271
I totally agree with Waldo.

00:43:03.277 --> 00:43:05.893
Yeah, oh, we have to mark this on the calendar.

00:43:05.893 --> 00:43:12.295
The day that you two agree, but it goes back to what you had mentioned before about simplicity.

00:43:12.295 --> 00:43:17.952
Sometimes, in this case, you talked about the power platform and be able to power automate instead of some of those tools.

00:43:17.952 --> 00:43:45.490
The simplicity or the perception of simplicity of setting it up, where somebody could just set something up, actually can come back to hurt you as well exactly, exactly, it's the same story it's, it's just moved yeah simplicity and easy can sometimes create chaos in long term because it's anybody can just jump in and do whatever I put it on twitter somewhere, somewhere last couple of days, like I multiply everything by 300 always

00:43:46.110 --> 00:43:48.472
no, it was not on Twitter, but our.

00:43:50.009 --> 00:43:50.552
WhatsApp group.

00:43:50.552 --> 00:44:14.617
And then I try to ask myself am I still able to support, if this would be 300 cases, like 300 records maybe, or 300 customers, or or 300 users, or 300, whatnot Would I still be able to do the job that I do today, the same way that this would be 300 cases?

00:44:14.617 --> 00:44:19.614
Hybrid development Would I be able to maintain 300 hybrid customers?

00:44:19.614 --> 00:44:20.275
I don't think so.

00:44:20.275 --> 00:44:22.826
That's why I don't want to do it Right.

00:44:22.826 --> 00:44:28.840
Would I be able to maintain 300 spread power automate solutions?

00:44:28.840 --> 00:44:29.523
I can't.

00:44:29.523 --> 00:44:32.786
I would never be able to do that, so maybe that's not a good solution.

00:44:32.786 --> 00:44:35.228
Can I maintain 300 pipelines?

00:44:35.228 --> 00:44:41.197
Yes, I can, because that's very centralized, very templated thing to do.

00:44:41.197 --> 00:44:51.239
So that's what I always try to convince myself Is this a good idea or is this not a good idea?

00:44:51.989 --> 00:44:56.797
No, it is a good strategy, because what is it you made me think of the other saying?

00:44:56.797 --> 00:45:02.996
It's like sometimes the most permanent solution is the temporary solution where somebody will put something in just to get through today.

00:45:02.996 --> 00:45:15.262
And then that ends up becoming the process, and you know, then everybody has to work around and try to fix that and instead of fixing the process of what they originally put in it's that temporary fix becomes the permanent fix.

00:45:15.262 --> 00:45:20.382
And it's that fixing things around that itself, you know and it builds for years.

00:45:21.172 --> 00:45:26.376
I think you don't want to know how many business-critical processes are running on prototype code.

00:45:29.032 --> 00:45:31.099
I think we all come across those, oh yeah.

00:45:31.889 --> 00:45:34.239
I'm my own as well, but yeah absolutely.

00:45:35.110 --> 00:45:43.684
There is that decathlon or a complex machine and a very tiny part of it in the bottom.

00:45:43.684 --> 00:45:45.250
You think that is important.

00:45:45.250 --> 00:45:51.463
When you pull it away, everything is uh, is uh, it's not well, certainly not working anymore.

00:45:51.463 --> 00:46:03.465
Everything falls apart yeah, I don't remember that, yeah, and that that is also maybe historical knowledge.

00:46:03.465 --> 00:46:09.963
If somebody new comes in and thinks that's not important, why would I do that?

00:46:09.963 --> 00:46:22.121
That is the other story where you have a couple of monkeys in a cage and there is a banana hanging in the top.

00:46:24.744 --> 00:46:26.065
That's a long story, by the way.

00:46:26.065 --> 00:46:28.018
I can't make that quick.

00:46:29.711 --> 00:46:31.478
It actually applies to Business Central.

00:46:31.478 --> 00:46:40.777
It goes like one monkey reaches to that banana and then they get a shower.

00:46:40.777 --> 00:46:44.014
Another monkey tries to do it, they get a shower.

00:46:44.014 --> 00:46:46.726
So another monkey tries to do it, he gets a shower.

00:46:46.726 --> 00:46:49.318
And everybody all monkeys get a shower right.

00:46:49.318 --> 00:46:52.797
And then at some point they find out.

00:46:52.797 --> 00:46:56.936
So if we reach out for the banana we get wet and we don't like it.

00:46:56.936 --> 00:47:08.398
So what they do is when a monkey tries to reach out for the banana, they pull him back, they stop him and then they replace a monkey.

00:47:09.152 --> 00:47:09.835
There's a new one in.

00:47:09.835 --> 00:47:13.880
He has no idea about the banana and the shower.

00:47:13.880 --> 00:47:20.697
So first thing he does is grabs the banana and then the whole group is jumping on him.

00:47:20.697 --> 00:47:21.641
Don't do that.

00:47:21.641 --> 00:47:27.014
And then at some point the whole group is jumping on him don't do that like, and then at some point the whole group was replaced.

00:47:27.014 --> 00:47:39.740
Nobody of the original gangsters, original monkeys, are in the group and they're still stopping each other from grabbing the banana, but nobody has an idea why.

00:47:39.740 --> 00:47:42.545
Nobody experienced the shower.

00:47:42.545 --> 00:47:54.534
So that kind of goes in the business center world as well, I think, like we are doing something but nobody has an idea anymore why.

00:47:54.534 --> 00:48:00.547
It has always been that way until somebody says why, what the heck?

00:48:00.547 --> 00:48:02.010
What is this, what is this?

00:48:02.010 --> 00:48:05.094
What is this piece of code, what is it doing, what is it meant to do?

00:48:05.094 --> 00:48:12.094
And then we always say, oh yeah, we never thought about it, we always did it this way.

00:48:14.954 --> 00:48:21.159
That's a good point because you know, when we have younger talents, they do ask more questions and you realize that's right.

00:48:21.159 --> 00:48:21.581
I don't know.

00:48:21.581 --> 00:48:23.096
That's how I've always been taught.

00:48:25.811 --> 00:48:32.637
Well, I think Waldo said it best at one point in a previous conversation about the knowledge that you have, or what you know is the poison.

00:48:32.637 --> 00:48:33.793
What did you say before?

00:48:33.793 --> 00:48:34.617
The poison, yeah.

00:48:38.873 --> 00:48:41.617
Not knowledge but experience.

00:48:41.617 --> 00:48:57.298
Experience is basically a poison to your whatever you're going to do in an IT world right, because you know probably the right thing to do is probably something that we didn't learn yet to do.

00:48:57.298 --> 00:49:08.518
And yeah, it evolves so fast that it's basically every single upgrade.

00:49:08.518 --> 00:49:14.056
I have the same conversations like yeah, we are doing an upgrade.

00:49:14.056 --> 00:49:18.918
Customer goes from a version, let's say CAL, to AL, but has an interface.

00:49:18.918 --> 00:49:22.936
Oh, that interface is a file-based interface, so let's do that again.

00:49:22.936 --> 00:49:24.380
Why?

00:49:24.380 --> 00:49:26.463
Because we know how to do that.

00:49:26.463 --> 00:49:28.173
It's a file-based interface and it worked.

00:49:28.173 --> 00:49:29.512
Yeah, but you're upgrading.

00:49:29.512 --> 00:49:33.599
Maybe you could upgrade the way you're interfacing with this piece of software.

00:49:33.599 --> 00:49:49.619
And the concept of upgrade sometimes is just a version number of the software you're upgrading and not the process that was implemented in the previous version of the upgrade.

00:49:49.619 --> 00:49:57.041
It's an ongoing conversation every single time that I have with customers, with even consultants.

00:50:00.311 --> 00:50:03.864
So with all this, I always have the age-old question.

00:50:03.864 --> 00:50:07.876
I keep asking it, rhetorically or not how can you keep up with all of this?

00:50:07.876 --> 00:50:12.010
Technology is going so quickly and it can be so rough.

00:50:13.012 --> 00:50:14.835
I don't even know, it's just.

00:50:14.835 --> 00:50:16.318
I find it difficult.

00:50:16.318 --> 00:50:24.422
You know, even just with the al language, never mind also with the business central and the functionality and technology.

00:50:24.422 --> 00:50:29.742
Before we had everything encompassed or encapsulated within the application.

00:50:29.742 --> 00:50:32.117
Now you expand it out to power platform.

00:50:32.117 --> 00:50:34.739
Now you expand it out to APIs.

00:50:34.739 --> 00:50:36.494
Now you expand it out all over the place.

00:50:36.494 --> 00:51:00.503
If you're somebody who worked with development in Cal back before, where we talked about you had that blurred line of functional consultant and developer, in a sense because of the simplicity of it, how do you start to one keep up with the application and still continue to work, whether you're talking about development or functionality, but then also draw boundaries around what you know?

00:51:00.503 --> 00:51:10.461
Because if I spend more time trying to learn Power Platform and AL development and the functionality of the application, do I know a lot of a little about a lot.

00:51:10.461 --> 00:51:11.806
And is that enough?

00:51:11.806 --> 00:51:20.735
Or should I start focusing on AL development and keeping up with the language, keeping up with the functionality and letting someone else keep up with the other stuff?

00:51:21.175 --> 00:51:26.804
I think Waldo had a really good strategy he had mentioned earlier is that you keep up with it.

00:51:26.804 --> 00:51:29.077
That's at least how I interpret it.

00:51:29.077 --> 00:51:37.059
You keep up with it when you need it, or when you're working on something and you actually need it, and that's when you keep up with okay, I'm working on this.

00:51:37.059 --> 00:51:42.342
What are the features around this that I can do to solve this problem or create a solution?

00:51:43.690 --> 00:51:46.398
Yeah, that seems to be, and AJ pointed it out.

00:51:46.398 --> 00:51:51.900
It seems to be what I do, that whenever I need it, I'll dive into it.

00:51:51.900 --> 00:51:54.952
But how do you know?

00:51:54.972 --> 00:51:55.472
what you need.

00:51:57.077 --> 00:52:01.221
This is where it gets into that question is because, if you're in, a space.

00:52:01.260 --> 00:52:02.329
Go back to your file management.

00:52:02.329 --> 00:52:07.983
If I'm not aware of the new functionality of an API to exchange data or to you know you pick any of that.

00:52:09.050 --> 00:52:11.699
Yeah, but awareness is something different than knowledge, right?

00:52:11.699 --> 00:52:23.911
So I think it's easy to be aware of stuff, like it's easy to be aware of what a power app and a power automate and power bi can do.

00:52:23.911 --> 00:52:28.757
It's a little bit less easy to be aware of what it cannot do.

00:52:28.757 --> 00:52:30.661
Uh, and I?

00:52:30.661 --> 00:52:36.014
I try to ask that question always, like even with the co-pilot.

00:52:36.014 --> 00:52:41.744
Now there is cop out all over the place, okay, and you have these crazy ideas from all people.

00:52:41.744 --> 00:52:47.239
But the first question we need to ask okay, but what can it not do?

00:52:47.239 --> 00:52:50.778
What can't we do with co-pilot?

00:52:50.778 --> 00:52:52.175
What are the limitations?

00:52:52.175 --> 00:52:53.675
What will we be hitting?

00:52:54.170 --> 00:52:59.523
Very obvious answer there for co-pilot is data interpretation is an obvious limit at the moment.

00:52:59.523 --> 00:53:09.081
It doesn't understand my gln3, it doesn't understand my two terabytes of data that I have in in in the database.

00:53:09.081 --> 00:53:10.463
Just able to talk to me.

00:53:10.463 --> 00:53:12.514
That's it so and that's all.

00:53:12.514 --> 00:53:16.083
Do I need to have the knowledge on how to talk to it?

00:53:16.083 --> 00:53:21.242
No, do I need to be aware what it can and cannot do?

00:53:21.242 --> 00:53:29.219
Yes, I think that's still easier to make those, let's say, choices from the moment you try to talk to it.

00:53:29.219 --> 00:53:30.737
I mean, same with Power Platform.

00:53:30.737 --> 00:53:41.621
I'm pretty well aware what it cannot do, which makes me being reluctant to do too much with it as a partner.

00:53:41.621 --> 00:53:45.190
I'm always talking as a partner.

00:53:45.210 --> 00:54:02.824
By the way, partner, I'm always talking as a part by the way I'm not talking yes, that you at least make a choice between technology a, technology B, because you are aware of the possibilities, you can make at least a calculated decision.

00:54:02.824 --> 00:54:11.197
And Brad is right, if you don't know that it exists a certain technology, you're not taking it into consideration.

00:54:11.197 --> 00:54:13.458
You probably do it in a less optimal way.

00:54:13.458 --> 00:54:37.152
So, yeah, you need at least to be aware of other options and I agree again with paulo, you need it is not so difficult to be aware.

00:54:37.152 --> 00:54:40.559
I mean, if you take in your, let's say, weekly, a number of blog posts, news etc.

00:54:40.559 --> 00:54:41.740
Um, watch some videos.

00:54:41.740 --> 00:54:44.554
You don't have to dive into every detail.

00:54:44.554 --> 00:54:52.496
If I look at the watch new videos from Microsoft around the release, I don't watch all of them.

00:54:52.496 --> 00:55:12.663
I pick those that I think are relevant and for others I probably do a quick view or say well, I know that there is something around this or this topic, so I hope I remember that next time that I may need it, but that's it.

00:55:15.351 --> 00:55:18.900
So that is a way to keep up and it's the awareness point of it.

00:55:18.900 --> 00:55:21.981
That's something that I tried to follow because I found I couldn't keep up, and it's the awareness point of it.

00:55:21.981 --> 00:55:26.536
That's something that I tried to follow because I found I couldn't keep up with it, and it is to at least have awareness.

00:55:26.536 --> 00:55:27.440
To say how I remember.

00:55:27.440 --> 00:55:32.942
Now, how I remember what I'm aware of is another story, because sometimes I forget what I'm aware of.

00:55:33.021 --> 00:55:52.775
But you know, the dinosaur brain doesn't have it, because at one point I know, personally, I tried to keep up with it all, in a sense of you know, knowing how to do it, how to work with it, and you just end up running yourself in a circle, I think, because the change comes too fast and it's, you know, not practical to know how to do it all, but at least if you know, ok.

00:55:52.775 --> 00:55:59.393
Well, if we come across a file transfer, now there's a new way, maybe there's another way to use an API to send the data or something Right, just as an example.

00:55:59.393 --> 00:56:04.878
So it is a challenge, it is a struggle and, again, how far do I go?

00:56:04.878 --> 00:56:05.840
You know?

00:56:05.880 --> 00:56:06.739
and that's why I'm at now.

00:56:06.739 --> 00:56:09.963
And maybe you set your bar higher than I.

00:56:09.963 --> 00:56:23.559
I mean, when I tell people, hey, there is going to be contract management and subscription billing in the next version of Business Central, then people might think, oh wow, he's an expert.

00:56:23.559 --> 00:56:30.177
No, that's all I know, Nothing more at all.

00:56:30.177 --> 00:56:34.494
Yeah, no, it is good.

00:56:34.494 --> 00:56:35.476
The awareness is good.

00:56:36.119 --> 00:56:49.074
Yeah no, I started sleeping better at night, going with that kind of philosophy, where I'll even say I started messing around with power automate and power platform and creating some of those flows early on, and then I finally said you know what?

00:56:49.074 --> 00:56:49.998
I know they exist.

00:56:49.998 --> 00:56:53.739
If it comes into a place, I'll say, hey, can we use one of those for this?

00:56:54.289 --> 00:57:08.583
And then talk to somebody who knows a little bit more about it than I do you know to see if it works, to see if it works, and I find that's a better way, at least for me, to work through all of this from a dinosaur perspective, or even from someone who would be new to it, because again, for them it'd be the same case.

00:57:08.583 --> 00:57:12.166
The sea is getting bigger with technology.

00:57:15.137 --> 00:57:17.809
It's not getting smaller.

00:57:17.809 --> 00:57:22.612
So I'm thinking what is knowledge?

00:57:22.612 --> 00:57:39.548
I mean knowledge that you can recall immediately the moment you need it, Like you know exactly how to start a new app, you know how to work with events Just these things, the daily development tasks.

00:57:39.548 --> 00:57:42.824
Just these things, the daily development tasks.

00:57:42.824 --> 00:57:51.150
But in the past I have done my work with, for example, item tracking.

00:57:51.150 --> 00:57:57.615
But that knowledge is at least outdated, it's rusty, it has vanished maybe.

00:57:57.615 --> 00:58:00.579
But I know there is something like item tracking.

00:58:00.579 --> 00:58:03.461
I still know, I'm still aware of it.

00:58:03.882 --> 00:58:19.541
I've not used it for maybe two or three years now, but the moment that I need it, I need to dive in because I know it is there and the first thing I will do is maybe look up any changes.

00:58:19.541 --> 00:58:22.405
Did something, was something released?

00:58:22.405 --> 00:58:30.974
It will take some time to gain the knowledge the moment you need it, but I cannot carry it along all those years.

00:58:30.974 --> 00:58:36.172
I mean your memory, what you need for your daily job.

00:58:36.172 --> 00:58:38.782
I think it's quite limited.

00:58:38.782 --> 00:58:40.456
You cannot remember everything.

00:58:40.456 --> 00:58:41.001
You're not a hard drive.

00:58:41.001 --> 00:58:42.050
You don're not a hard drive.

00:58:42.050 --> 00:58:44.018
You don't have a hard drive in your head.

00:58:46.853 --> 00:58:53.742
Now we have central Q, so the knowledge is actually the ability to decently prompt these days.

00:58:53.802 --> 00:59:07.181
Right yeah, the knowledge to prompt you hit on another point and that's what I started to focus on, and even with others I was talking about with the mb820 test, where you could use learn right.

00:59:07.181 --> 00:59:14.871
Sometimes it's not a matter of memorization, it's a matter of knowing where to go to find the information you need when you need it right.

00:59:14.871 --> 00:59:19.972
So it's the same thing with, like I said, with development, development in a language, a language to me.

00:59:19.972 --> 00:59:21.001
You can learn a language if I language to me.

00:59:21.001 --> 00:59:24.074
You can learn a language If I wanted to learn Spanish.

00:59:24.777 --> 00:59:31.161
You know, if I'm a native English speaker, I can't, but I still need to understand the fundamental concept of what am I trying to say.

00:59:31.161 --> 00:59:39.878
So I think, even with development is understand what you're trying to do logically, and then you can learn how to do it if you know where to go to get the information.

00:59:39.878 --> 00:59:44.027
I'm not saying you have to go look at code and copy it, but at least you can learn how to do it if you know where to go to get the information.

00:59:44.027 --> 00:59:51.340
I'm not saying you have to go look at code and copy it but at least you can go and learn how to understand the syntax of a language.

00:59:51.360 --> 01:00:03.347
Yeah, it's more than just syntax, of course but yeah, yeah, well, I'm keeping it simple, just for my simple mind, this morning, it's Friday anyway.

01:00:03.347 --> 01:00:07.478
Yeah, it's Friday and it's already been a disaster for me, so, uh, you know it's power for the course.

01:00:07.539 --> 01:00:35.931
it wouldn't be a friday if it wasn't right um, I must say now I was thinking about this earlier uh, all of this, dinos, dinosaurs, things haven't been easy right the last couple of years, because I mean, there was a new language and we had to take this extensibility into account, and then all of a sudden, um, there is like something like source control that is mandatory because we cannot work in team without source control anymore.

01:00:36.594 --> 01:01:04.239
And then now also, microsoft is applying all these new things, like every month an upgrade, breaking changes, and now all of a sudden, we need to learn all that new stuff and apply it all at once as well because of these changes, of these breaking changes and all these things.

01:01:04.239 --> 01:01:16.923
So, yeah, I can't say we are not struggling like with that, trying to implement our own product, try to be made that's repeatable, trying to be, uh, next major compliance, try to not break.

01:01:16.923 --> 01:01:22.878
But in, in, in the same thing, try to align with microsoft breaking stuff, our stuff.

01:01:22.878 --> 01:01:27.905
Uh, in the same thing, try to align with Microsoft breaking stuff, our stuff, in the line, implementing all of these things.

01:01:27.905 --> 01:01:40.603
Now, just imagine Microsoft would not do that, that the product would just be the product and we would get the time to align ourselves with all this new stuff.

01:01:40.603 --> 01:01:49.699
It's not just aligning ourselves, it's also just implementing that because we have to, because Microsoft is doing stuff along the way as well.

01:01:49.699 --> 01:01:53.440
So I mean, yeah, give us a break.

01:01:54.170 --> 01:01:55.496
Yes thank you.

01:01:56.271 --> 01:01:57.235
A one-year pause.

01:01:57.750 --> 01:02:00.259
There is something to be said, with slowing down a little bit.

01:02:00.259 --> 01:02:05.663
Do you really need to go that fast to keep up with the competition?

01:02:05.663 --> 01:02:11.402
And what I mean by fast is put in a lot of these things that they're doing Exactly.

01:02:13.911 --> 01:02:18.298
One year it's power all over the place and the other year it's co-pilot all over the place.

01:02:18.298 --> 01:02:19.514
What is next year right?

01:02:20.630 --> 01:02:21.757
It will be something different.

01:02:21.757 --> 01:02:23.094
Scary.

01:02:23.094 --> 01:02:25.487
The boat shifted, the boat shifted, the boat shifted.

01:02:25.487 --> 01:02:34.304
Co-power next year be some sort of remote control robot or something, I don't know.

01:02:34.304 --> 01:02:37.434
Um, so that's wild.

01:02:37.434 --> 01:02:42.643
Well, waldo and aj, I know it's Friday afternoon, it's almost beer time.

01:02:42.643 --> 01:02:49.161
I know you drink a lot Wine time, coffee time, whatever you have over there in the afternoon Beer time.

01:02:49.161 --> 01:02:51.615
It's going to be beer time this evening.

01:02:51.655 --> 01:02:55.193
yes, yeah well I wish, I could, I'm ready for a beer right now.

01:02:55.193 --> 01:03:00.295
To tell you the truth, I'm sorry, just pretend you're on the other side.

01:03:00.295 --> 01:03:00.659
I think I'm sorry.

01:03:00.659 --> 01:03:01.829
Just pretend you're on the other side.

01:03:02.873 --> 01:03:03.597
I think I'm about to.

01:03:03.992 --> 01:03:05.449
I think I'm about to pull myself a whiskey.

01:03:05.690 --> 01:03:06.918
It's five o'clock somewhere right.

01:03:08.197 --> 01:03:10.150
I can change my clock on the time zone.

01:03:10.150 --> 01:03:13.155
Thank you both for taking the time to speak with us.

01:03:13.155 --> 01:03:14.492
I really do appreciate it.

01:03:14.492 --> 01:03:15.195
It was insightful.

01:03:15.195 --> 01:03:16.259
I always enjoy talking with you.

01:03:16.259 --> 01:03:31.237
I always enjoy talking with you and appreciate the comedy too, and I also look forward to seeing you both at Days of Knowledge in Atlanta, which will be coming up in September.

01:03:32.351 --> 01:03:33.117
Looking forward to that.

01:03:33.710 --> 01:03:36.059
September 12th to 14th in Atlanta, Georgia.

01:03:36.059 --> 01:03:45.480
Everybody else should attend and participate and then be able to sit down and have a beer after 5 o'clock with everybody and have continued conversation.

01:03:45.661 --> 01:03:46.282
At Atlanta time.

01:03:46.282 --> 01:03:48.797
At Atlanta time.

01:03:49.429 --> 01:03:54.981
Well for you, you could have it earlier, because you could say it's five o'clock back home.

01:03:55.001 --> 01:03:56.023
I'm staying on the time zone.

01:03:57.271 --> 01:03:58.175
Let's start our workshop.

01:03:59.313 --> 01:04:00.034
Let's start our workshop.

01:04:00.034 --> 01:04:16.701
Until then, if anybody would like to contact you or see more about some of the great things that you're doing.

01:04:16.701 --> 01:04:18.809
How can they contact you or see some of the great things you have been doing?

01:04:18.809 --> 01:04:22.876
Oh, my website, waldobe and on Twitter.

01:04:22.936 --> 01:04:25.003
Excellent, we'll put the links in the show notes.

01:04:25.690 --> 01:04:26.932
How about you.

01:04:26.932 --> 01:04:30.302
Aj Twitter, linkedin, my website LinkedIn.

01:04:30.302 --> 01:04:38.260
Yeah, kaufmannl, double F, double N, but yeah, linkedin Twitter works pretty good.

01:04:39.231 --> 01:04:40.956
Yeah, I'm a big Twitter fan these days.

01:04:40.956 --> 01:04:41.398
I like it.

01:04:41.398 --> 01:04:42.436
A lot of people don't like it, but it's like a place to let loose, it's good.

01:04:42.436 --> 01:04:42.679
Yeah, I'm a big Twitter fan these days.

01:04:42.679 --> 01:04:42.742
I like it.

01:04:42.742 --> 01:04:45.646
A lot of people don't like it, but it's like a place to let loose, it's good.

01:04:46.489 --> 01:04:56.536
You know, what's amazing is that CentralQ also reads tweets and the amount of actually answers it gets from Twitter is actually quite amazing.

01:04:56.536 --> 01:04:58.797
Wow, really, wow, yeah.

01:04:58.797 --> 01:05:02.155
So yeah, let's keep on tweeting.

01:05:02.737 --> 01:05:04.735
Yeah, absolutely, maybe we can put some code in there.

01:05:04.735 --> 01:05:06.277
I had some things I wanted to try on Twitter.

01:05:07.311 --> 01:05:08.233
Yeah, collective memory.

01:05:08.976 --> 01:05:09.920
No, that's good, I have to.

01:05:10.170 --> 01:05:14.780
And maybe one of the places you should go to if you want to know something that you don't know.

01:05:14.780 --> 01:05:17.811
Twitter Like how do?

01:05:17.811 --> 01:05:20.076
I ask that question to Central Q.

01:05:20.076 --> 01:05:21.498
You will at least get an answer.

01:05:24.463 --> 01:05:24.905
That's good.

01:05:24.905 --> 01:05:26.711
I'll have to try that Well again.

01:05:26.711 --> 01:05:29.670
Thank you both, and I hope you have a great weekend.

01:05:30.132 --> 01:05:32.353
Thank you, you too Thank you, thank you for having us.

01:05:32.672 --> 01:05:33.094
It's all right.

01:05:33.094 --> 01:05:35.275
Ciao, ciao, bye-bye, see you soon, bye.

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

01:05:43.740 --> 01:05:45.282
Thank you, brad, for your time.

01:05:45.282 --> 01:05:48.784
It is a wonderful episode of Dynamics Corner Chair.

01:05:48.784 --> 01:05:52.226
I would also like to thank our guests for joining us.

01:05:52.226 --> 01:05:57.661
Thank you for all of our listeners tuning in as well.

01:05:57.661 --> 01:06:09.757
You can find Brad at developerlifecom, that is D-V-L-P-R-L-I-F-Ecom, and you can interact with them via Twitter D-V-L-P-R-L-I-F-E.

01:06:09.757 --> 01:06:23.177
You can also find me at matalinoio, m-a-t-a-l-i-n-o dot I-O, and my Twitter handle is mattalino16.

01:06:23.177 --> 01:06:26.831
And see, you can see those links down below in their show notes.

01:06:26.831 --> 01:06:28.195
Again, thank you everyone.

01:06:28.195 --> 01:06:29.740
Thank you and take care.