Nov. 19, 2024

Episode 348: In the Dynamics Corner Chair: Source Code Management and You in Business Central

Apple Podcasts podcast player icon Spotify podcast player icon Youtube Music podcast player icon RSS Feed podcast player icon Amazon Music podcast player icon Audible podcast player icon YouTube Channel podcast player icon
Apple Podcasts podcast player icon Spotify podcast player icon Youtube Music podcast player icon RSS Feed podcast player icon Amazon Music podcast player icon Audible podcast player icon YouTube Channel podcast player icon
Season 3 Business Central Partner

👨‍💻Join hosts Kristoffer Ruyeras and Brad Prendergast in the latest episode of the Dynamics Corner Chair, where they pick Steve Endow's brain on risk mitigation and source code management in the #BusinessCentral ecosystem. From the essentials of training to the key responsibilities of partners and customers in implementations and documentation, get ready for some must-know insights for all BC enthusiasts.💻

 

You don't want to miss:

 

🏅The ERP COE: Learn about Steve's groundbreaking center of excellence initiative in El Salvador and the critical need for top-tier training in Latin America.

 

⌨Source code management: An in-depth discussion of the importance of source code maintenance and documentation for Business Central extensions and the risks of improperly managed code.

 

💰Tech debt: Why and how technical debt can lead to significant business risks.

 

🥊Real-world challenges: Engage in the complexities faced by partners and customers alike, and how continuous learning and effective documentation can make or break your implementation.

 

🔌Customer empowerment: Learn why it's essential that customers take charge of their ERP systems, questions to ask of your partner, and why ERP success is ultimately owned by the customer.

 

🤝Partner accountability: Explore why partners must uphold high standards of service & support, while maintaining policies and ethics around code management.

Send us a text

#MSDyn365BC #BusinessCentral #BC #DynamicsCorner

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

00:01 - Business Central Development in El Salvador

14:27 - Risks of Missing Source Code

24:14 - Responsibilities and Education in Business Central

35:01 - Managing Business Central App Source Issues

43:40 - Business Central Education and Source Code

53:19 - Responsibility in ERP Implementations

01:04:47 - Learning and Sharing in Business Development

WEBVTT

00:00:01.020 --> 00:00:04.852
Welcome everyone to another episode of Dynamics Corner.

00:00:04.852 --> 00:00:07.783
Brad, do you have your repo?

00:00:07.783 --> 00:00:10.108
No, perhaps you should.

00:00:10.108 --> 00:00:11.833
I'm your co-host, chris.

00:00:12.861 --> 00:00:13.542
And this is Brad.

00:00:13.542 --> 00:00:17.672
This episode was recorded on November 14th 2024.

00:00:17.672 --> 00:00:21.306
Chris, Chris, Chris, Repo.

00:00:21.306 --> 00:00:22.949
What's a repo?

00:00:22.949 --> 00:00:23.890
Someone taking your car?

00:00:23.890 --> 00:00:25.134
It could be.

00:00:25.134 --> 00:00:27.237
It's Someone taking your car it could be.

00:00:28.501 --> 00:00:29.766
It's almost like taking your car.

00:00:32.161 --> 00:00:33.768
Business Central is a great application.

00:00:33.768 --> 00:00:41.390
You have the opportunity to extend Business Central application, but have you ever wondered how those applications are made?

00:00:41.390 --> 00:00:42.840
What happens to the source code when it is?

00:00:42.840 --> 00:00:43.761
How those applications are made.

00:00:43.761 --> 00:00:45.603
What happens to the source code when it is?

00:00:45.603 --> 00:00:50.192
Today we had the opportunity to speak with one of my business-centric community favorites.

00:01:13.760 --> 00:01:14.042
Steve Endo.

00:01:14.042 --> 00:01:15.147
I wish I he does have that voice.

00:01:16.009 --> 00:01:17.040
I wish I had that recorded.

00:01:17.040 --> 00:01:20.224
I'd have that as something on repeat Every time my phone rang.

00:01:20.224 --> 00:01:20.909
It would be Steve Senn.

00:01:20.909 --> 00:01:22.025
You have a sultry voice.

00:01:25.167 --> 00:01:27.572
I don't have to edit his audio too much.

00:01:27.572 --> 00:01:34.171
It's like that natural radio podcast voice that's it.

00:01:34.512 --> 00:01:35.352
That's what I have.

00:01:35.352 --> 00:01:46.094
That's why I'm here, steve um, I'm okay, no quieres hablar español conmigo?

00:01:51.123 --> 00:01:51.986
You're far ahead of me.

00:01:55.022 --> 00:01:58.260
You're speaking a little too fast yeah exactly no.

00:01:58.381 --> 00:02:02.072
I listen to Steve's weekly Spanish lessons on Fridays.

00:02:02.072 --> 00:02:03.566
Well, I try to listen to it.

00:02:03.566 --> 00:02:06.528
It's the coffee hour that you have.

00:02:06.528 --> 00:02:08.986
Can you move it please?

00:02:09.920 --> 00:02:13.025
It's lunchtime for me it's lunchtime, so it's not real.

00:02:13.665 --> 00:02:14.598
I can't enjoy it with coffee.

00:02:14.740 --> 00:02:17.866
It's 8.30 for me, bro, Like 8.30 or 9.

00:02:17.866 --> 00:02:19.586
I don't even know what time it is.

00:02:19.586 --> 00:02:22.102
So, yeah it's.

00:02:22.102 --> 00:02:30.175
I drop the kids off, I come right back and I frantically get everything set up and try to get everything working and go live.

00:02:30.175 --> 00:02:32.908
It's um, yeah, it's just a madhouse.

00:02:33.741 --> 00:02:34.683
No, it works well.

00:02:35.085 --> 00:02:35.828
I join it, man.

00:02:35.828 --> 00:02:38.120
I love it, though it's that's also Fridays.

00:02:38.120 --> 00:02:41.468
I typically do not have anything on Friday morning.

00:02:41.468 --> 00:02:46.606
Awesome, I sit there, make my Americano listen to your stuff, so you're one of the 12 people.

00:02:46.606 --> 00:02:57.906
I'm sure there's a lot of people who've used after, like you know, if Brad doesn't want to miss his lunch or something, I fully appreciate that.

00:02:58.240 --> 00:03:05.807
No, I try, I try, but I've been looking forward to speaking with you about this topic that we want to talk about.

00:03:05.807 --> 00:03:13.054
Before we jump into it, though, we talked about your weekly Coffee with Steve podcast.

00:03:13.054 --> 00:03:14.585
I think it's a podcast, what do you call it?

00:03:16.040 --> 00:03:16.965
I call it a live stream.

00:03:18.961 --> 00:03:20.086
It's so sophisticated.

00:03:20.086 --> 00:03:26.328
It's a weekly live stream, but would you tell everybody a little bit about yourself?

00:03:29.223 --> 00:03:30.587
I am Steve Endo.

00:03:30.587 --> 00:03:32.707
I live in Los Angeles.

00:03:32.707 --> 00:03:36.450
I have been working with Business Central.

00:03:36.450 --> 00:03:40.050
I found some old blog posts that shocked me.

00:03:40.050 --> 00:04:12.187
It was quite a while ago, pre-business Central whatever they called it financials and so I think I've been working with it since 2018, something like that, and then 2019, if I got that right in earnest focused on development, learned AL development and Docker and all the technical backend stuff, but prior to that I worked with Dynamics GP since 2004.

00:04:12.187 --> 00:04:18.202
Prior to that, peoplesoft, solomon4, development, you name it.

00:04:18.202 --> 00:04:19.649
So I've been around.

00:04:20.353 --> 00:04:20.735
It does.

00:04:20.735 --> 00:04:27.413
It sounds like you've been around here with great ERP background and you're doing something excellent with the center of excellence as well, too.

00:04:29.379 --> 00:04:32.571
Yes, that has been a crazy adventure.

00:04:32.571 --> 00:04:36.129
Sorry, un momento, por favor, let me.

00:04:36.129 --> 00:04:45.166
I'm turning off, my robot vacuums because they're making noise, so I apologize.

00:04:48.180 --> 00:04:48.903
Hopefully you can edit this.

00:04:48.903 --> 00:04:49.725
We can't hear it.

00:04:49.725 --> 00:04:51.850
We can't hear it, but we'll have to leave that in there.

00:04:51.850 --> 00:04:53.321
Which robot vacuums do you have?

00:04:54.101 --> 00:04:58.930
I have robo rock vacuums that are a few years old.

00:04:58.930 --> 00:05:00.814
They were the fancy ones at the time.

00:05:00.814 --> 00:05:06.892
They are now considered, um you know, ancient by today's standards.

00:05:06.892 --> 00:05:12.052
But okay, I have told my fleet of robot vacuums to stop vacuuming.

00:05:12.052 --> 00:05:14.807
Quit interrupting my important podcast here.

00:05:14.987 --> 00:05:15.870
Sorry, that's it.

00:05:16.781 --> 00:05:18.507
So my apologies.

00:05:18.507 --> 00:05:24.829
So ERP Center of Excellence started as this zany idea.

00:05:24.829 --> 00:05:29.622
Like something got into me and I came up with this absolutely crazy idea.

00:05:29.622 --> 00:06:05.990
I had no plan, I knew no one in El Salvador and I just went over there and started banging on doors just nonstop, had meetings, found people, tracked people down, bug people, contacted them and it's a lot of dead ends, just dead end after dead end, and eventually got connected with some people that were doing a kind of like a community economic revitalization of a small town and they were open to having me start something there.

00:06:05.990 --> 00:06:14.069
They didn't really know, I didn't really know, and jumping to today, it is truly amazing.

00:06:15.072 --> 00:06:33.829
We now have, I believe we have five people in Berlin, el Salvador, town of like 15, 18,000 people, site of a volcano, relatively remote town relative to El Salvador standards, and they're blossoming.

00:06:33.829 --> 00:06:35.807
They're doing a great job.

00:06:35.807 --> 00:06:48.048
They're learning Business Central, they're doing training of Business Central, they're doing RDLC reports, word layouts, config packages, someone's learning AL development, someone else is learning Power Automate.

00:06:48.048 --> 00:06:54.132
We just agreed to have an 18-year-old come on board.

00:06:54.132 --> 00:07:13.196
He just graduated from high school and he is going to be building internal systems for a full network operations center there, for a full network operations center there and he's going to be ingesting customer telemetry, doing a full NOC dashboard, proactive telemetry, monitoring, support tickets, the whole bit.

00:07:13.937 --> 00:07:35.387
Wow, that's excellent, and I do think that sometimes, doing what you did, you had the end in sight or an idea in sight, but having no plan, sometimes I think it works out better because you kind of adapt as you go and what sticks works, but at least you know you wanted to do something with Business Central and you don't get hung up in the planning, you just go.

00:07:36.410 --> 00:07:41.127
Yes, and I can't even credit myself with having an end goal in mind.

00:07:41.127 --> 00:07:46.564
I had this very, very small idea I'm going to go to El Salvador and offer a week of training.

00:07:46.564 --> 00:07:47.548
How nice would that be?

00:07:47.548 --> 00:08:08.946
Right, we can have a few people who know Business Central in Latin America because there seems to be a just massive lack of resources, training opportunities, you know, in the entire region and it is a massive region right, like how can we not have any business central presence there?

00:08:08.946 --> 00:08:23.605
I know there are partners implementing business central, but to ask them to attend a one thousand fifteen hundred dollar training for business central for their consultants is economically infeasible.

00:08:23.605 --> 00:08:30.062
Literally it it's like asking me to spend $20,000 to send someone for a week of training.

00:08:30.062 --> 00:08:32.206
Just the economics don't work.

00:08:32.947 --> 00:08:40.067
So I thought, oh, this would be cool to train some people and get some more people in Business Central in the region.

00:08:40.067 --> 00:08:59.791
And that every single step of the way, kind of as you mentioned, changing left, right, zigging, zagging, coming up with new things, finding roadblocks, pivoting in an entirely new direction, and that's everything we do every single day.

00:08:59.791 --> 00:09:02.668
Laptop dies great, get a new laptop.

00:09:02.668 --> 00:09:03.049
Right.

00:09:03.049 --> 00:09:05.524
Like internet goes out.

00:09:05.524 --> 00:09:19.721
We now have cell phones and ups like every little impediment is like cool, work around it, move on, and they're doing a great job no, that's excellent I remember when you first thought of that and I was talking with you, I think it's.

00:09:19.760 --> 00:09:20.945
I still have to get down there with you.

00:09:20.945 --> 00:09:24.423
I keep saying this, but we'll have to get on the same schedule.

00:09:24.423 --> 00:09:28.432
Somewhere you can fly by and pick me up I'll be there next week.

00:09:29.315 --> 00:09:37.096
I fly down on thursday and I'll be there for um nine days how long is that flight for you, by the way, uh, from los angeles.

00:09:37.096 --> 00:09:40.664
It's about five hours, uh, from miami.

00:09:40.664 --> 00:09:44.272
I think it's only like three or something, two and a half hours.

00:09:44.272 --> 00:09:45.094
It's much closer.

00:09:46.864 --> 00:09:47.788
Brad, that's like nothing.

00:09:48.080 --> 00:09:50.466
We'll have to get together, steve because I would like to go.

00:09:50.486 --> 00:09:51.571
Texas is also very close.

00:09:52.059 --> 00:09:54.850
I would like to go down there for a short period.

00:09:54.850 --> 00:09:58.293
Next week is a little too soon and I have another trip planned.

00:09:58.293 --> 00:09:59.837
Well, not, unfortunately.

00:10:00.340 --> 00:10:03.206
No, cancel all of that, Brad Just go.

00:10:03.245 --> 00:10:06.253
If I could, I would, but I can't, so I won't.

00:10:07.539 --> 00:10:09.287
It's an inexpensive short trip down there.

00:10:09.287 --> 00:10:12.366
Yeah, pop in the airport.

00:10:12.366 --> 00:10:14.167
Very efficient, small airport.

00:10:14.167 --> 00:10:15.148
Head right out.

00:10:15.148 --> 00:10:17.004
We can have a driver waiting for you.

00:10:17.004 --> 00:10:17.807
You can run a car.

00:10:17.807 --> 00:10:19.302
You name it.

00:10:19.302 --> 00:10:20.244
Is it direct flight?

00:10:20.244 --> 00:10:23.202
Usually from LA.

00:10:23.202 --> 00:10:24.126
It is a direct flight.

00:10:24.126 --> 00:10:30.466
There are alternatives, but like hard to beat a five-hour flight no, that's great.

00:10:30.586 --> 00:10:31.730
I I do want to see that.

00:10:31.730 --> 00:10:41.672
I would like to go down there I'm interested in and I'm getting at the point in my life where I want to see more and I I've been years of consulting and I've been everywhere, but I've been nowhere, so I'd like to do it.

00:10:41.672 --> 00:10:44.404
Uh, but no, great job on that, congratulations.

00:10:44.404 --> 00:10:52.846
And the whole topic of talent isn't what I wanted to talk about, but what you're doing is a great thing because we're struggling and going through it.

00:10:52.846 --> 00:10:59.836
It's just how do you attract individuals to come into the business central space and if nobody wants to hire anybody?

00:10:59.836 --> 00:11:02.703
I think you talked about it and I don't know if you and I talked about it in person.

00:11:02.703 --> 00:11:11.643
I mean, we've had a lot of conversations about this, but if nobody wants to hire anybody without experience and everybody wants people with experience, but nobody's hiring anybody without experience how does somebody get experience?

00:11:12.445 --> 00:11:22.570
so I'm on that initiative now too, and I'm willing to spend some time to train individuals to go down the path of getting into it, because we need it.

00:11:22.971 --> 00:11:25.394
It's new generation is what we need.

00:11:25.394 --> 00:11:27.788
We need perspective, all that.

00:11:28.519 --> 00:11:34.960
And that was one of the dead ends that I encountered when doing the ERP Center of Excellence.

00:11:34.960 --> 00:11:46.282
I thought, oh, if we train someone, if we get someone certified, they will be of value and might be an opportunity to work remotely for US partners Universally.

00:11:46.282 --> 00:11:48.208
Zero hesitation.

00:11:48.208 --> 00:11:50.947
The answer I got was absolutely not.

00:11:50.947 --> 00:11:59.500
I would never hire a person you've trained, a person that is certified, a person that has three months of experience, universal, like.

00:11:59.500 --> 00:12:04.432
There's zero hesitation in their response to me for every question.

00:12:04.432 --> 00:12:06.467
I was like huh really.

00:12:07.341 --> 00:12:24.750
And what was really fascinating is I could tell their responses were completely unexamined Because, as they tell me, they would say we do not hire remote workers Really, except for these remote workers that already work for you.

00:12:24.750 --> 00:12:29.607
We would not hire someone who doesn't have x, we would not hire someone.

00:12:29.607 --> 00:12:47.544
And these were just excuses, and so it's fascinating to watch this dissonance from what they say compared to what they do, and I was kind of puzzled by that and so, yeah, I'm like, okay'm like, okay, fine, we'll hire them as interns, we'll train them in.

00:12:47.544 --> 00:12:51.471
Maybe they'll be good enough in six months or a year or whatever We'll find out.

00:12:51.471 --> 00:12:53.908
So it's an all grand experiment for me.

00:12:55.342 --> 00:12:57.509
Well, it seems to be like you're making a lot of progress.

00:12:57.509 --> 00:13:00.610
I follow it online and the conversations you and I had.

00:13:00.610 --> 00:13:16.692
But to get into the meat of the conversation, this has been frustrating me and I know you as well for some time and it seems now it's popping up everywhere.

00:13:16.692 --> 00:13:32.352
I experience at least once a week it feels like this type of situation and with Business Central and Business Central development, the architecture changed from Dynamics Nav formerly Navision to where you have extensions.

00:13:32.352 --> 00:13:37.110
Prior to Business Central, the code that you wrote was embedded within the application.

00:13:37.110 --> 00:13:38.153
So it was.

00:13:38.153 --> 00:13:47.514
If you in essence had modifications within your database, as we would call it, the source code for those changes were within your database.

00:13:47.514 --> 00:13:51.791
Now, with AL, you have source files.

00:13:51.791 --> 00:13:54.006
You create an extension.

00:13:54.006 --> 00:14:07.412
That extension then gets and this is not AppSource related, this is a customer that has a partner, a freelance developer or an internal developer creating code for them.

00:14:07.412 --> 00:14:15.150
You have source files that you in essence compile to create an app file which you then load into your Business Central environment.

00:14:15.919 --> 00:14:16.990
As a per-tenant extension.

00:14:17.259 --> 00:14:19.268
As a per-tenant extension, correct, yep?

00:14:19.268 --> 00:14:23.089
And I don't think anybody has any thought to.

00:14:23.089 --> 00:14:24.524
What does that mean?

00:14:24.524 --> 00:14:26.562
And I experienced.

00:14:26.562 --> 00:14:40.027
My first experience with this was when it first came out back when Business Central had just the show my code, true or false, and someone said it to false.

00:14:40.027 --> 00:14:42.547
We're going to get into what all that means.

00:14:42.547 --> 00:14:47.938
And then a customer had an extension installed.

00:14:47.938 --> 00:14:50.668
This developer's laptop died.

00:14:52.547 --> 00:15:17.325
Nobody had access to the source code and because that show my code was set to false, they had to redo the entire thing this goes back further than that, because the first encounter I had was the version one I think it was like NAV 2018, where I was working on a client and they had some things that triggered and I was like, what's triggering this?

00:15:17.325 --> 00:15:30.710
And it was like the first version of extensions and we couldn't get to it, no matter what, and so they had some form of documentation that we had to recreate the whole thing yes.

00:15:31.230 --> 00:15:36.225
So now this brings up the whole question just to kind of the to paint the flow.

00:15:36.225 --> 00:15:40.081
I kind of jumped the gun a little bit because I'll have to be held back, because I get.

00:15:40.081 --> 00:15:42.363
So you recall when we were talking at the conference.

00:15:42.363 --> 00:16:07.629
I get so animated and passionate about this because I don't think a lot of users of Business Central realize the risk to their implementation of not understanding or assuming that the extensions that they're having created for them and again it could be internally it doesn't mean it's just the partners doing it, it doesn't mean that someone that you may contract externally is doing it.

00:16:07.629 --> 00:16:11.532
It could be someone that you're doing it internally as well.

00:16:11.532 --> 00:16:18.412
I don't think they understand the risk of not having that source code available to their business.

00:16:20.620 --> 00:16:34.153
I would agree, and I've seen it in the Dynamics GP world for 20 years and surprisingly, not many customers end up having a problem with that.

00:16:34.153 --> 00:16:35.274
They're very fortunate.

00:16:35.274 --> 00:16:40.633
But a few do have some notable experiences where they do have a problem.

00:16:40.633 --> 00:16:51.861
So yeah, to this day in Dynamics GP world we have the same issue and customers switch as partners.

00:16:51.861 --> 00:17:19.803
Six to 12 to 18 months later they realize they need to upgrade and can't because they don't have the source code and they're left going back to their old partner if that partner is still in business, if that consultant or whoever developed it still has the code, and they are asking very politely if they can get the source code and hopefully they can get it.

00:17:20.843 --> 00:17:37.592
Yeah, and this I tried to not jump all over, because just every sentence that we say to me can shoot off to something else because I have to reel it back.

00:17:37.592 --> 00:17:45.557
File the policy with now you have more.

00:17:45.557 --> 00:17:46.857
You have allowed debugging.

00:17:46.857 --> 00:17:51.005
You know download symbols, show my code, early versions of show my code.

00:17:51.005 --> 00:17:57.067
In essence, what that really means is do I have access to the source code within the app file?

00:17:57.166 --> 00:18:11.513
So if some forget source code management for a moment, so if somebody loads a per tenant extension, if you go into your extension management you click on, if you have list view or it's even's even ellipse, if you have the tile view the three dots there's an option to download source.

00:18:11.513 --> 00:18:20.673
If you have that enabled, to where someone can download the source, anybody who may need to help you, including the partner, because they have another story here.

00:18:20.673 --> 00:18:29.866
I'm going to tell you this wonderful story they can download the source for what you have running to make changes without impacting what you have.

00:18:29.866 --> 00:18:36.444
If you don't have that option enabled, you cannot download the source.

00:18:36.444 --> 00:18:57.951
Therefore, you do not know what's installed in that extension and if somebody were to need to make any changes, you have to go back to get the original source code and hope, as you had alluded to, whomever wrote it has it and hope they have the right version.

00:18:57.951 --> 00:19:10.248
Steve, that you and I have been having about losing the source code, I will tell you about an implementation where someone had the source code.

00:19:10.248 --> 00:19:13.534
It didn't match what was installed.

00:19:13.534 --> 00:19:27.134
Therefore, when they installed a fix, they lost functionality because the source code functionality, because the source code wasn't the correct version.

00:19:27.134 --> 00:19:41.373
So here we go with another risk of you don't have access to the source code in the event that you need to upgrade, or if you have a need to modify the extension, you don't have the proper source code.

00:19:41.373 --> 00:19:46.465
And now everyone will say, well, I don't need to upgrade, or what's the impact on the upgrade?

00:19:46.465 --> 00:20:03.451
Well, let's roll into Microsoft rolling out updates to Business Central monthly and in those monthly updates, through the evolution of the product, as they should, they make changes to the product to enhance the usability for the users.

00:20:03.579 --> 00:20:08.301
So they improve it in essence, by their nature of improving it.

00:20:08.301 --> 00:20:12.088
Sometimes you also have to update your code to work with it.

00:20:12.088 --> 00:20:29.453
And if you get the nice notification saying, well, we have to mod, you know you make your extension compatible with the next version of business Central and again them upgrading and making changes to it to me is not an issue at all.

00:20:29.453 --> 00:20:32.766
I mean, it's just what they need to do to improve or enhance the product.

00:20:32.766 --> 00:20:35.511
I guess you could say to make it more feature-rich.

00:20:35.511 --> 00:20:41.280
But if you don't have the source code, you can't make it compatible.

00:20:41.280 --> 00:20:51.221
Therefore, the end game is it will be uninstalled because it can't work with a newer version, so you lose it.

00:20:52.434 --> 00:21:16.141
And, as we discussed at the Summit conference, I was sitting next to someone on my flight to Texas and she's holding her phone and I'm able to see these messages and she's just deleting all of these messages that say your extension won't upgrade, you need to fix it, and it's just delete, delete, delete.

00:21:16.141 --> 00:21:19.325
And I'm like what, what?

00:21:19.325 --> 00:21:38.556
I would be absolutely terrified if I had an inbox with 30 of those messages and it was just kind of coincidence that I'm sitting next to someone who does microsoft dynamics, both gp and bc, and I'm just watching those uh emails get deleted and I'm like it's a partner.

00:21:38.695 --> 00:21:45.517
So this is a partner yes, now I I mentioned there could be lots of reasons.

00:21:45.517 --> 00:22:03.846
Maybe that wasn't her role and someone else is handling that, but the fact that there are 35 of those things in your inbox like you should have caught that at next minor, next major, right, like you shouldn't get those messages.

00:22:03.846 --> 00:22:07.394
And that's why, when I emailed, you said Brad, do you have a copy of that message?

00:22:07.394 --> 00:22:09.423
Because I've literally never seen it before.

00:22:09.423 --> 00:22:16.765
Like, if we get that email, it is we have dropped the ball, right, it's too late Now.

00:22:16.765 --> 00:22:17.527
We know that.

00:22:17.527 --> 00:22:33.228
But the fact that I'm watching a major partner have dozens of those emails points to some type of systemic problem, right, it's just a symptom, like something's wrong here.

00:22:33.228 --> 00:22:34.396
What's going on?

00:22:34.396 --> 00:22:37.186
And I'll let you guide the conversation.

00:22:37.247 --> 00:22:39.053
No, you don't have to let me guide it.

00:22:39.053 --> 00:22:46.595
I'm doing all I can to be reserved, because I have so much I want to say about this topic from so many different angles.

00:22:46.595 --> 00:22:53.008
It's my 2025 charter to spread the word on this.

00:22:53.795 --> 00:22:55.776
So we can't save the world.

00:22:55.776 --> 00:23:13.606
We've been talking about some of the symptoms, some of the consequences, right, we've been talking about some of the symptoms, some of the consequences, right, and you know, sometimes people will do things and without experiencing the consequences, they may just never understand the reality of that.

00:23:13.606 --> 00:23:22.972
We can talk at the conference, in our sessions, presentations, and say, hey, you need this, and it goes over the heads of 98% of the crowd.

00:23:22.972 --> 00:23:33.602
But there's the 2% sitting there who come to the realization that we're talking about them and they understand because they're in that situation and we've seen this before.

00:23:33.602 --> 00:23:38.083
They're like wait a minute, we can't get the code from our partner.

00:23:38.083 --> 00:23:42.339
They have told us they will not give it to us, or whatever those conversations we've had.

00:23:42.339 --> 00:23:49.388
Yes, now you get it, and they're slowly waking up, but we, we can't.

00:23:49.388 --> 00:23:51.816
There's only so much we can do.

00:23:51.816 --> 00:24:03.810
So if we go from consequence to situation, to up the chain, what is the path for education?

00:24:03.810 --> 00:24:06.842
Not everyone is going to want education.

00:24:06.842 --> 00:24:09.481
Not everyone is going to hear what we're trying to offer.

00:24:09.481 --> 00:24:11.381
What can we offer?

00:24:11.381 --> 00:24:12.640
What can we do about it?

00:24:14.715 --> 00:24:21.861
Because, like the call I had with the customer who spent months getting an internal developer to develop a PTE.

00:24:21.861 --> 00:24:25.905
He cannot find the PTE anywhere in his business central.

00:24:25.905 --> 00:24:28.784
He has one laptop with the source code.

00:24:28.784 --> 00:24:31.762
He didn't know the words GitHub or DevOps.

00:24:31.762 --> 00:24:35.222
When I mentioned it he had never heard of pipelines.

00:24:35.222 --> 00:24:37.102
This is the IT manager I'm helping now.

00:24:37.102 --> 00:24:43.486
At that point he's right on the edge of being too late for me to offer him any help.

00:24:43.486 --> 00:24:49.372
He's got one copy of source code, no version information, so we have no idea what it is right.

00:24:49.372 --> 00:24:54.084
Just as you mentioned, it simply says 1.000 default publisher.

00:24:54.084 --> 00:24:56.249
That's all I've got to go on, right.

00:24:56.249 --> 00:24:58.936
So is this the latest version?

00:24:58.936 --> 00:24:59.439
I don't know.

00:24:59.439 --> 00:25:00.462
And to your point, can we install it?

00:25:00.462 --> 00:25:00.724
I don't know.

00:25:00.724 --> 00:25:01.970
And to your point, can we install it?

00:25:01.970 --> 00:25:15.068
I don't know, it might overwrite like well, actually we couldn't even find the PT in their environment, so yeah, so how do we bring it back to a productive solution?

00:25:16.215 --> 00:25:21.046
I think you have to break that down further of responsibilities or roles.

00:25:21.046 --> 00:25:31.780
You know, I think, what for example years ago when customers were deciding to move to business central.

00:25:31.780 --> 00:25:39.906
One of the key points that we always say is you know, work with your partner to or at least start documenting any of the customizations you have.

00:25:39.906 --> 00:25:43.785
Now nav is fairly easy to identify those.

00:25:43.785 --> 00:25:49.086
It's typically the functionality or how it works is usually the difficult component.

00:25:49.086 --> 00:25:50.401
Now it's a little bit more.

00:25:50.401 --> 00:25:58.007
It's harder because now you can do functional and the code itself that you have to gather.

00:25:58.115 --> 00:26:03.934
It's difficult because, from a customer's point of view right to go to Steve's point where do you start?

00:26:03.934 --> 00:26:12.243
I do have a thing to add to this at the appropriate time A customer using Business Central.

00:26:12.243 --> 00:26:29.869
I don't think they should be expected to understand all of this in a sense, right, unless there's some clear-cut documentation for it, because they're also going to entrust in whomever they hire to do it properly.

00:26:29.869 --> 00:26:34.125
I always equate implementing business central to building a house.

00:26:34.125 --> 00:26:41.505
Either you're building a house for a business or you're going in and you're enhancing a house, you know, to satisfy the changes to the business.

00:26:41.505 --> 00:26:54.829
If I'm going to hire a contractor to come put up a fence around my house, for example, I'm not going to understand all of the rules of fencing until somebody has to come in and fix my fence, for example, or something here.

00:26:54.829 --> 00:26:56.978
So there needs to be some.

00:26:56.978 --> 00:27:07.180
You know, this is where I'm going on this mission of okay, well, if you're going to implement Business Central, think of these gutches, right, just so you're aware of the potential risks.

00:27:07.180 --> 00:27:25.240
So then it leads you to okay, well, let's, you know, go on a mission to ensure that partners fully understand, because a lot of the challenges that you have is a lot of the partners are working with individuals that understood the CAL way of doing it, which is ah, I'll just make my changes in the database.

00:27:25.240 --> 00:27:26.183
They're in the object design.

00:27:26.183 --> 00:27:27.096
I can go back and get it.

00:27:27.096 --> 00:27:29.383
We don't have the ability for source code management.

00:27:29.383 --> 00:27:30.224
We don't have anything like this.

00:27:30.285 --> 00:27:31.875
So, ah, for AL, it's the same way.

00:27:31.875 --> 00:27:33.617
Ah, show my code false.

00:27:33.617 --> 00:27:39.423
Sure, I don't want anybody to see what I'm writing, because I'm not comfortable with my code anyway, so I don't want somebody to look at it and criticize it.

00:27:39.423 --> 00:27:42.467
Then, next thing, you know, someone needs help.

00:27:42.467 --> 00:27:45.029
And now everybody realizes there's a breakdown.

00:27:45.029 --> 00:27:47.876
So to your point, steve, where do you start?

00:27:47.876 --> 00:28:07.344
And also, to mention somebody, a customer can find a contractor as well, and again, not all of this audience is at fault, but it only takes a few to make it difficult for a few or a lot, but you can find a contractor to do it.

00:28:07.344 --> 00:28:10.340
And are they going to?

00:28:10.340 --> 00:28:16.025
Should they be expected to have a repository of your code or something?

00:28:16.025 --> 00:28:16.987
It's a challenge.

00:28:18.015 --> 00:28:19.662
I think the responsibility has to.

00:28:19.662 --> 00:28:21.356
Somebody has to start.

00:28:21.356 --> 00:28:27.888
I mean, initial responsibility needs to come from partners to educate the customers.

00:28:27.888 --> 00:28:37.096
The need Now to what we've been saying is a lot of partners don't even know what those are and it needs to.

00:28:37.096 --> 00:28:56.561
Someone has to mention it at some point of that conversation, at some point in that relationship, even to a point where maybe a partner doesn't do that now, but as long as they have the understanding, like, hey, we should probably let the customer know you need to have a repo established or a GitHub or DevOps.

00:28:56.561 --> 00:29:11.932
That may still be the customer's responsibility to put that up, even if they don't have anybody on staff, but maybe consider hiring somebody that knows it or work with a partner In terms of education.

00:29:11.991 --> 00:29:13.232
You need to break that down further.

00:29:13.232 --> 00:29:22.642
So there's an education from a partner side that any new partners or partners that are coming from NAV or GP that has never done it before, they need to be educated the importance of that.

00:29:22.642 --> 00:29:31.651
The other side of that, the other audience, would be customers that are deciding to move to business central or they were already in business central.

00:29:31.651 --> 00:29:35.142
They just need to make sure that you maintain that environment moving forward.

00:29:35.142 --> 00:29:44.087
So it's almost like you have to break it down beyond that, and some, some customers don't have it managers, they're not going to know, they're just like hey, set me up.

00:29:44.369 --> 00:29:49.023
I need this customization there are many, many levels.

00:29:49.023 --> 00:29:51.409
Right, I was waiting for this.

00:29:51.490 --> 00:29:53.334
I can see steve is like me.

00:29:53.334 --> 00:29:54.036
We're both kind of.

00:29:54.036 --> 00:30:06.116
I'm staring at him because I remember the conversations we've been having and he's fuming just like I am, like I just want to burst well, I burst, well, I guess I'm not apathetic about it, I guess I'm just.

00:30:06.317 --> 00:30:16.125
I've seen it enough where, hey, consequence is a motivator, right, there's positive consequence and there's negative consequence.

00:30:16.125 --> 00:30:22.826
And if I hire the contractor and they do it wrong, guess what I'm still responsible for it.

00:30:22.826 --> 00:30:23.914
And guess what I'm still responsible for it.

00:30:23.914 --> 00:30:26.840
And guess what I'll learn the hard way.

00:30:26.840 --> 00:30:30.608
And could I have possibly known they were doing it wrong?

00:30:30.608 --> 00:30:32.518
Probably not right?

00:30:32.518 --> 00:30:35.242
I haven't studied building code.

00:30:35.242 --> 00:30:37.547
So is that my responsibility?

00:30:37.547 --> 00:30:46.608
No, but in the construction world we have a pretty developed structure for these things.

00:30:46.608 --> 00:30:53.429
We have licensing, insurance, we have permits, we have inspections, right, if you follow those rules.

00:30:53.429 --> 00:30:58.823
Now plenty of people skirt those rules to their own, at their own risk, right?

00:30:58.823 --> 00:31:10.384
I don't necessarily want that level of of bureaucracy in our industry, but maybe it's an offer someone could make.

00:31:10.384 --> 00:31:13.954
But would a partner accept that offer for an outside?

00:31:24.663 --> 00:31:26.145
code inspection?

00:31:26.165 --> 00:31:28.728
probably not, I don't know um, um, where do you start?

00:31:28.728 --> 00:31:33.811
But I I think part of it is I think it's a go back to the, the education point.

00:31:33.811 --> 00:31:43.701
I think that we need to have a you know somewhere where it says, okay, well, if you're going to have custom extensions, this is what you need to do.

00:31:43.701 --> 00:31:47.378
And then, steve, to what you've been saying with me, because I've been having you look at something.

00:31:47.378 --> 00:31:49.996
You need to make it really simple, right, I've come to.

00:31:50.778 --> 00:32:09.259
If you don't have your source code available, if you don't have it within a repository, if something happens, you're not going to get your code period, you know, and your business will be impacted because whatever functionality that is, it doesn't matter what it is, it doesn't be adding just one field, for example, to a table, or it could be writing an entire system.

00:32:09.259 --> 00:32:11.886
That functionality would no longer exist.

00:32:11.886 --> 00:32:20.557
And I think we need to have some sort of you know document on that, which it's it's I want to get to.

00:32:20.557 --> 00:32:27.682
But from the partner point of view, I understand Steve's comment of would you want someone to go through the licensing?

00:32:27.682 --> 00:32:30.363
But I want to get to the?

00:32:30.403 --> 00:32:44.647
But in a moment they also some may look at it as okay, well, I don't want anyone to look at it because someone could comment it, but you know, fine, or now they can get it and do something else with it and not have me service it.

00:32:44.647 --> 00:32:49.936
Right, you know, and almost that like I have it, I'm not going to give it to you, so therefore you need me type approach.

00:32:49.936 --> 00:32:57.384
I'm not saying they all would do that, but there's many reasons why I could see someone not wanting to do it can I go to the?

00:32:57.463 --> 00:32:58.165
licensing thing.

00:32:58.165 --> 00:33:01.118
I was going to jump with this at the end before you go to the licensing brad.

00:33:01.138 --> 00:33:02.201
You were on my session.

00:33:02.201 --> 00:33:07.237
Um, you know what to do before starting your business central implementation.

00:33:07.237 --> 00:33:17.076
You know, I, I, and maybe I need to add this and dive into much more into detail for those that are decision makers or moving to business central.

00:33:17.076 --> 00:33:21.938
I had mentioned about documenting your customizations and things like that.

00:33:21.938 --> 00:33:44.487
I did prior to that session at conversation with others, that you know who owns that customization, who will own it, and I've always pushed back and said you own that and you need to make sure that you have a tool that helps you manage those changes.

00:33:44.487 --> 00:33:46.747
And so we start talking about GitHub To them.

00:33:46.747 --> 00:33:47.928
It's still way over their head.

00:33:47.928 --> 00:33:49.929
They're like I don't even know what that means.

00:33:49.929 --> 00:33:51.368
Who's responsible for that?

00:33:51.368 --> 00:33:52.390
And so you're responsible.

00:33:52.390 --> 00:33:53.809
I don't have somebody that can do that.

00:33:53.809 --> 00:34:03.433
Well, you work with your partner, so it's still alien to this industry of the ownership.

00:34:06.095 --> 00:34:07.057
And of course you get some deeper conversation.

00:34:07.057 --> 00:34:13.469
The ownership is tough because I think that would depend upon the contract of the development Right.

00:34:13.469 --> 00:34:22.860
So I'm not saying it's tough to be inferred, it should be stated I am paying you to develop this, therefore it is mine.

00:34:22.860 --> 00:34:33.465
Or the partner can say on the other side, and I'm okay with it, you're paying us to do this, but it's our intellectual, I mean, that's a negotiation between the two entities at that point.

00:34:33.465 --> 00:34:36.641
So I could you know that's whatever they agree upon.

00:34:36.641 --> 00:34:38.105
But it should be at least stated.

00:34:38.525 --> 00:34:48.581
In my opinion is step one Is who owns the rights to whatever customizations or extensions are being made, right, first of all?

00:34:48.581 --> 00:34:53.820
And then, once you have that clearly identified, then you can determine who's managing it.

00:34:53.820 --> 00:34:56.686
But in essence, I think it still needs to be managed.

00:34:56.686 --> 00:35:00.539
Period, yes, um to the point.

00:35:00.539 --> 00:35:12.420
So if this comes to play right now, as you talked about, you had mentioned next minor, next major, and now someone talks about Chris.

00:35:12.420 --> 00:35:13.262
You talked about GitHub.

00:35:13.262 --> 00:35:15.840
You talked about source control management.

00:35:15.880 --> 00:35:49.355
You know repository for the code, so you can, there's many benefits of source control management as well, or source control repository, version history, access to the code, no-transcript.

00:35:49.355 --> 00:35:53.663
That means either some of the fields changed, some of the events changed or something changed.

00:35:53.663 --> 00:35:55.722
It doesn't necessarily mean your app will work the same.

00:35:55.722 --> 00:36:12.844
It just means that it will be compiled and it can be installed because there isn't a conflict which would help prevent them getting those messages that it will be compiled and it can be installed because there isn't a conflict right which would help prevent them get those messages that you had identified and properly test and review what they need to maybe do with their extension.

00:36:16.318 --> 00:36:22.496
So I see I'm gonna have to bring this back to like, from a customer point of view and a partner point of view, what they need to be aware of.

00:36:22.496 --> 00:36:35.431
One is check your policy for your app files, for the ability to download the source code at a minimum, because at least you can get what is installed and modify and enhance it.

00:36:35.431 --> 00:37:02.164
Second to that is to have a repository that you store this code in, so you have access to it, so you can keep track of it, you can see it's compatibility with the next version and even publish it to an online environment without having somebody touch it, so you know what is installed is what's in the repository.

00:37:02.164 --> 00:37:07.030
Steve, did you want to say something?

00:37:11.655 --> 00:37:15.059
No, I think you can get a lot of directions there.

00:37:15.059 --> 00:37:26.637
And yeah, on the one hand I empathize with the need for education and we do that through conferences and whatever avenues we can.

00:37:26.637 --> 00:37:30.884
On the other hand, there's only so much I can do.

00:37:30.884 --> 00:37:53.467
And when I see partners not attempting to adopt good practices, you know I'm willing to compete with them and in a 30-minute phone call I can make it very clear that their partner is not taking care of them.

00:37:53.467 --> 00:38:00.380
Yes, right, it's not difficult to demonstrate and I'm not going to apologize for that it's.

00:38:00.380 --> 00:38:02.141
And I'm not going to apologize for that it's.

00:38:02.141 --> 00:38:11.148
Hey, the customer's paying thousands of dollars for that service and it's putting potentially millions of dollars of their business at risk.

00:38:11.728 --> 00:38:20.519
If a partner is not responsible, if they're negligent, if they're lazy, if they're whatever, like, make up an excuse.

00:38:20.519 --> 00:38:36.699
I'm sorry, customer, that that happened to you, but here are the 10 things that I can just point out in 15 minutes that these problems are obvious to me as a professional in this industry.

00:38:36.699 --> 00:38:42.728
I am happy to demonstrate my ethics, my morals, my competence and my lack of knowledge in certain areas.

00:38:42.728 --> 00:39:04.806
I'm happy to discuss that, but there's only so much I can do to help the customers who didn't know to ask those questions, or who didn't understand the importance of those things, or who had a partner who did not invest in the knowledge and education and training and reduction of technical debt.

00:39:04.806 --> 00:39:07.503
Like I've seen it for 20 plus years.

00:39:07.503 --> 00:39:22.909
We're going to continue to see it and I'll help, on one hand, with conferences, presentations, webinars, you name it, but on the other hand, I'm ready to talk with those customers who have been neglected or have received poor service.

00:39:24.376 --> 00:39:25.221
You make a good point.

00:39:25.916 --> 00:39:44.684
I like the way that you talked about with the contractors or such, because you can only say so much, but you just have to be able to help out those the best you can at a certain point, because if you're going to look for someone and you have them do work on your house, you're going to deal with the results of it when it happens.

00:39:45.295 --> 00:39:47.083
The only thing you can have is some education.

00:39:47.083 --> 00:40:15.025
Just to throw something into here, with that licensing or that permitting agency right, earlier versions of NAV or Navision, when someone was doing development, or even if an ISV had a solution that they presented to a customer to install, we would merge the objects that code was available within the database.

00:40:15.025 --> 00:40:23.210
There were certain cases where some of those objects were not readable, cases where some of those objects were not readable.

00:40:23.210 --> 00:40:32.894
Or if an ISV had a solution, they would apply to Microsoft for a license to basically hide the source code for those code units.

00:40:32.894 --> 00:40:46.068
Why don't we have the same type of thing for Business Central, where that show my code would only be options for partners that have a special license?

00:40:46.068 --> 00:40:49.351
Or you know, even an app, an app source or something.

00:40:50.775 --> 00:40:56.088
So you're saying essentially require show my code by default.

00:40:56.554 --> 00:41:19.449
Correct and in certain cases, if you're a developer, whomever you may be, right, you can get that to where your per-tenant extensions can have that off for a reason, right, you can apply to Microsoft for the sake of it just to say that you understand the risks of what you're doing.

00:41:19.594 --> 00:41:26.849
You have proper, you know I'm not saying Microsoft would have to you know, govern and ensure and validate that you're doing it properly.

00:41:26.849 --> 00:41:47.601
But in a sense, though, I think doing this would also do well, because by customers potentially running the risk and I hate to say it on the extreme, because you know I talk on the extreme someone could go out of business if they have an extension that doesn't work properly, if it's that important to the process of their business, you really can go out of business.

00:41:47.601 --> 00:41:53.844
If you can't upgrade because in the online environment you can only defer that for so long, right, so you can give yourself some life of five months.

00:41:53.844 --> 00:42:04.063
So maybe you take it back to the agency, the application, because it also makes Microsoft look bad in a sense, if customers can't handle it.

00:42:05.835 --> 00:42:15.619
On the one hand, do we well on the multiple hands the first hand, do we really want Microsoft being the arbiter of that process?

00:42:15.619 --> 00:42:18.226
I don't know, maybe, maybe not.

00:42:18.226 --> 00:42:23.275
It is their platform, maybe, maybe not it is their platform.

00:42:23.275 --> 00:42:23.815
So is that a prudent thing?

00:42:23.815 --> 00:42:41.748
On the other hand, maybe they will be forced to move in that direction if the consequences of these problems become significant enough that they realize, ok, we need to start to manage this for better or worse.

00:42:41.748 --> 00:42:49.603
Like, how, say, apple validates apps that go into their app store right, they kind of control the platform.

00:42:49.603 --> 00:43:00.186
Some people complain about that, but in this sense, they're validating for quality, they're validating for malicious content and all these other specified benefits.

00:43:00.186 --> 00:43:04.467
So is Microsoft going to need to start to arbitrate that?

00:43:04.467 --> 00:43:07.824
I do wonder we've discussed in general.

00:43:08.516 --> 00:43:17.047
If an AppSource app is not being, you know, responsibly maintained and that prevents an upgrade, what would Microsoft do about it?

00:43:17.047 --> 00:43:20.965
Like, the customer doesn't have access to that source code.

00:43:20.965 --> 00:43:24.585
What if an AppSource app vendor, a publisher, goes out of business?

00:43:24.585 --> 00:43:26.922
What if they just abandon the app?

00:43:26.922 --> 00:43:31.282
You just uninstall and move on.

00:43:31.282 --> 00:43:33.007
I don't know.

00:43:33.007 --> 00:43:39.347
We've asked this question for a few years now and I don't know if these situations have happened or not.

00:43:40.556 --> 00:43:47.744
That is tough, because an app could potentially be someone's IP and I think Microsoft then getting involved would be a challenge Again.

00:43:47.804 --> 00:43:48.927
I don't know, so is a PTE.

00:43:49.494 --> 00:43:50.740
A PTE is someone's IP.

00:43:50.740 --> 00:44:00.387
But this is where I'm saying you could have some mechanism of getting it for lack of better terms licensed.

00:44:00.387 --> 00:44:05.876
The way you could hide the code because you can prove it's IP or you claim it's IP or something you know.

00:44:05.876 --> 00:44:07.001
You have to go through a step.

00:44:07.001 --> 00:44:12.443
I'm not saying the step has to be litigious or arduous, it's just, by default, don't allow it.

00:44:12.443 --> 00:44:16.306
In those cases where someone wants to do it, they fill out a form.

00:44:16.306 --> 00:44:22.141
Even if the form just says I acknowledge that no one will have access to the code in the event of an upgrade, something could happen.

00:44:22.141 --> 00:44:28.489
Even if the form just says I acknowledge that no one will have access to the code.

00:44:28.509 --> 00:44:30.530
In the event of an upgrade, something could happen.

00:44:30.530 --> 00:44:31.532
You know, something as simple as that.

00:44:31.532 --> 00:44:33.213
Well, they'll have to step in eventually, you know right?

00:44:33.213 --> 00:44:33.614
I don't know.

00:44:34.295 --> 00:44:35.657
The app source is growing and growing and growing In Apple space.

00:44:35.657 --> 00:44:41.954
It's kind of like they just want to make sure it's not malicious or anything like that, and I'm sure Microsoft can do the same thing make sure it's not malicious or anything like that, and I'm sure Microsoft can do the same thing.

00:44:41.954 --> 00:44:45.461
I think for me to your example, steve.

00:44:45.461 --> 00:45:14.371
Like, if the app is, you know whoever owned it went out of business and several customers are on it and using it and it's a core of their business, I think at some point maybe there's some agreement down the road that if an app has not been maintained or being validated or recertified on the app source let's say, two years, nothing has changed.

00:45:14.371 --> 00:45:22.427
Maybe it comes to a point where whoever is using it would get the source.

00:45:22.427 --> 00:45:24.230
I don't, that's tough.

00:45:26.697 --> 00:45:27.581
That realm right.

00:45:27.581 --> 00:45:29.346
There is a whole other story.

00:45:29.346 --> 00:45:34.840
I'm just trying to go from the front side versus what happens if someone goes out of business and such like that.

00:45:34.840 --> 00:45:42.360
I mean because I could argue if the app was really good and has a wide customer base, they could sell it off as part of their going out of business, right?

00:45:42.820 --> 00:45:43.702
Real-world scenario.

00:45:43.702 --> 00:45:45.003
A customer called me.

00:45:45.003 --> 00:45:55.043
Their IT person had some type of severe, life-threatening medical condition In the hospital.

00:45:55.043 --> 00:45:57.909
They did not expect him to return to work.

00:45:57.909 --> 00:46:06.335
Return to work.

00:46:06.335 --> 00:46:06.936
They were in deep trouble.

00:46:06.956 --> 00:46:15.838
Another one, a developer, a consultant slash, quasi-developer was helping a customer with some extensive, not customizations, but kind of yeah, customizations to their environment.

00:46:15.838 --> 00:46:17.981
We can't get a hold of the guy.

00:46:17.981 --> 00:46:23.429
He's disappeared for three months and no one's helping this customer.

00:46:23.429 --> 00:46:26.438
And so it happens.

00:46:26.438 --> 00:46:28.943
And then the customer that I'm working with now.

00:46:28.943 --> 00:46:31.528
They spent months on it.

00:46:31.528 --> 00:46:34.440
They hired an internal developer for their BC environment.

00:46:34.440 --> 00:46:45.179
For whatever reason, they let that developer go and now they have this code they think is the code, and I'm like how do I know what this is?

00:46:45.179 --> 00:47:00.039
They spent tens of thousands of dollars on this and so, yes, all sorts of scenarios and we can try on the education front.

00:47:00.039 --> 00:47:03.282
We, we can try on a community.

00:47:03.282 --> 00:47:08.045
You know there's the AL dev practices or whatever the website is.

00:47:08.045 --> 00:47:10.947
We can try to make offers.

00:47:10.947 --> 00:47:17.072
We can't make people listen, we can't make partners improve and reduce their technical debt.

00:47:17.072 --> 00:47:20.255
So there are going to be consequences.

00:47:20.295 --> 00:47:23.119
So there are going to be consequences.

00:47:23.119 --> 00:47:23.920
The risks will be there.

00:47:23.920 --> 00:47:26.764
Yeah, I mean you could really focus on education.

00:47:26.824 --> 00:47:34.695
That risk is alive and well Steve you tell me I should give up on my fight.

00:47:34.695 --> 00:47:38.358
No, I would just say that perhaps you know.

00:47:38.358 --> 00:47:38.820
Let's figure out.

00:47:38.820 --> 00:47:48.628
In what ways can we focus it to be more effective, most effective, and who's listening, who's willing to invest?

00:47:48.628 --> 00:48:00.215
How many partners send their consultants to external training?

00:48:00.215 --> 00:48:01.336
Send their consultants to external training?

00:48:01.336 --> 00:48:07.688
How many partners proactively identify their technical debt and work to address it?

00:48:07.688 --> 00:48:18.681
How many organizations have you worked for that still have bad practices?

00:48:18.681 --> 00:48:20.927
So I don't know how much we can accomplish.

00:48:20.927 --> 00:48:29.432
We can make offers, but the people who are accepting those offers, I would speculate, are the top 10%, right.

00:48:29.432 --> 00:48:34.480
Like I've attended training by AJ, I'm like why isn't this class full?

00:48:34.480 --> 00:48:36.585
Aj Kaufman, yeah Right.

00:48:36.585 --> 00:48:41.382
Why isn't this class on API development not full?

00:48:46.028 --> 00:48:48.634
yeah, the valid questions.

00:48:48.634 --> 00:48:50.918
I agree with you on that.

00:48:50.918 --> 00:48:59.414
It's a and it is a challenge from a business point of view, but there's also a sense of you invest in your talent.

00:48:59.414 --> 00:49:10.510
You reap the rewards of that as well, because with the application changing and and again to even go to your point, it doesn't have to be you send them to external training, like you send them somewhere.

00:49:10.510 --> 00:49:13.193
External training could be you bring someone in.

00:49:13.193 --> 00:49:16.012
External training could be you can pay for an online course.

00:49:16.012 --> 00:49:16.755
I just want to be clear.

00:49:16.755 --> 00:49:21.431
The external training could be even say you take one person, say, hey, learn this research it.

00:49:21.471 --> 00:49:24.505
Talk to people and then hold an internal training class right.

00:49:25.027 --> 00:49:41.260
So, there's all ways for it, but training class right, so there's always far, but not taking the time to do that actually hurts, because the way that they would implement may be different because of it's not keeping in line with the direction of the application.

00:49:41.260 --> 00:49:42.867
And even, like you're talking about, with the coding.

00:49:42.867 --> 00:49:53.813
Don't even get me started on the APIs, because I had a conversation with someone at Summit and they were coming up with this wonderful solution and then you say, well, why don't you just use an API page?

00:49:53.813 --> 00:49:58.072
And they're like, can it do this?

00:49:58.072 --> 00:49:59.394
Yeah, I love that.

00:49:59.394 --> 00:50:04.534
It's a fact and I know you experience it yourselves.

00:50:04.534 --> 00:50:07.786
We have these conversations and it's not easy for someone to know everything.

00:50:07.786 --> 00:50:10.387
I agree, experiencing yourselves, we have these conversations and it's not easy for someone to know everything.

00:50:10.387 --> 00:50:10.668
I would agree.

00:50:10.668 --> 00:50:17.612
I mean, there's a lot of depth to development, but some things you should have a core understanding of they at least exist, if you follow what I'm saying.

00:50:17.612 --> 00:50:23.715
So that external training and the additional training is helpful, which could help in these instances.

00:50:23.715 --> 00:50:26.657
So I think you're right.

00:50:27.117 --> 00:50:28.539
in a sense, You've got to make it simple.

00:50:29.398 --> 00:50:32.121
Well no, steve tells me all the time I have to dumb things down.

00:50:33.081 --> 00:50:36.023
You have to make it simple so that I can understand it.

00:50:36.023 --> 00:50:57.369
Even, for example, if all these conferences are happening, you can even have a session where, like, how to be a good pm on a business central implementation not just a good pm, because project management in general is pretty broad, but how do you manage a business central implementation?

00:50:57.369 --> 00:50:58.492
Because anytime I ask, like, how do you?

00:50:58.492 --> 00:50:59.375
What's your method?

00:50:59.375 --> 00:51:00.617
Someone asked me what's your method?

00:51:00.617 --> 00:51:05.974
Agile, you know waterfall, I'm like hybrid.

00:51:05.974 --> 00:51:08.036
I was like hybrid.

00:51:08.737 --> 00:51:09.318
Wrong answer.

00:51:09.338 --> 00:51:10.179
Where does it fit?

00:51:11.726 --> 00:51:13.090
We just get it done.

00:51:13.090 --> 00:51:14.293
We just get it done.

00:51:14.594 --> 00:51:15.255
Just get it done.

00:51:15.255 --> 00:51:26.576
But even if someone could put a session like that of what a good business central like, how do you prepare a business central and how do you educate your, you know Well, that's a little bit different than this topic.

00:51:27.246 --> 00:51:28.751
But I mean, there's so many of these sessions.00:51:28.751 --> 00:51:36.059


And again to Steve's point, who goes to these sessions and where are they?00:51:36.059 --> 00:51:46.730


I mean, fortunately, I went to Days of Knowledge in the US, which it was its first time there, but it was mostly a technical group, which was good, I think that was even as small as it was.00:51:46.730 --> 00:52:00.112


It was an inadequate size for the first time in the US, but it was full of all technical people, and I don't mean technical from the development point, it was full of developers, it was full of functional consultants.00:52:01.114 --> 00:52:15.666


So the vibe for the conference was just completely different, because everybody was learning and talking about the actual, what I call boots-on-the-ground implementation processes, not the.00:52:15.666 --> 00:52:19.356


I'm up here, this is how I think it works, this is how I think it should work.00:52:19.356 --> 00:52:30.364


So it really was a rich conference for that, for that.00:52:30.364 --> 00:52:37.559


So now, if we go back to Steve on the source code, management for business, central implementation for customers, knowledge and education, how do we start this?00:52:37.559 --> 00:52:43.168


I'd like you you know, just behind the scenes, to say you know, I don't know if you saw my email, but I'm stealing your survival guide.00:52:43.168 --> 00:52:44.755


I'll just put it on there in the recording too.00:52:45.184 --> 00:52:52.751


I like your title from our email discussion yes okay, sorry, it's been a busy few weeks.00:52:52.751 --> 00:52:57.672


I've already forgotten the details of that, but I think I just don't matter.00:52:57.672 --> 00:52:58.355


Do you see that?00:52:58.355 --> 00:53:00.648


I just don't matter would you say?00:53:00.809 --> 00:53:09.153


I think I called it an idiot's guide, though I think I might be your term no, no, you actually said the no.00:53:09.153 --> 00:53:13.543


The formal title was Steve's survival guide, but I took the survival guide.00:53:13.563 --> 00:53:19.114


Okay, well, I guess we've got education, and right now I've.00:53:19.114 --> 00:53:34.273


I guess my frustration has been I'm like, okay, I've accepted it, and I'm also now trying to just lead by example and I talk about what I'm doing, and I talk about Cosmo Alpaca.00:53:34.273 --> 00:53:36.465


Is that the right tool for everyone?00:53:36.465 --> 00:53:45.219


No, but it's a pretty powerful tool that just has us doing good practices by default.00:53:45.219 --> 00:53:47.610


And we had problems.00:53:47.610 --> 00:53:49.090


Now we use this tool.00:53:49.090 --> 00:53:58.847


Our problems, those problems went away and now it's like, wow, look at how much time that has opened up for us to do these other things better.00:53:58.847 --> 00:54:00.311


So we've improved.00:54:00.612 --> 00:54:03.440


And you know, now I just have the call.00:54:03.440 --> 00:54:11.684


We just got the engagement to do a code review for that PTE where there is no documentation, no information.00:54:11.684 --> 00:54:14.635


We just have a pile of code, no source code, control.00:54:14.635 --> 00:54:19.936


We don't even have the PTE to test in an environment, so we don't know how it should work.00:54:19.936 --> 00:54:25.777


And I'm like, hey, best I can do is just offer you an initial eight-hour code review.00:54:25.777 --> 00:54:31.237


We'll see what we find and I'll try to help you.00:54:31.237 --> 00:54:38.755


Not sure that we can help everyone.00:54:39.585 --> 00:54:40.711


No, we can't help everyone.00:54:40.711 --> 00:54:42.672


I think I like your approach.00:54:42.672 --> 00:54:55.775


See, this is I'm going to call you every week for therapy Right before your live stream, so you'll just be frazzled right before he started to throw you off I'll have my coffee.00:54:55.775 --> 00:54:57.018


But I think you're right.00:54:57.018 --> 00:55:07.251


I think it's just a matter of just putting out the message of what you're doing and hopefully enough people see it that you can, you know, instill some change or at least people be aware of good practices.00:55:07.251 --> 00:55:09.992


But even you talked about Cosmo alpaca.00:55:09.992 --> 00:55:10.675


It's the same thing.00:55:10.675 --> 00:55:11.905


It's like some of these tools are built.00:55:11.965 --> 00:55:22.610


I had a conversation with somebody that was recently and they were struggling to install an on-prem business central so that they could test something and do some work.00:55:22.610 --> 00:55:23.750


And I was scratching my head.00:55:23.750 --> 00:55:26.393


I'm going why don't you use a CDX?00:55:26.393 --> 00:55:37.460


And if you need another version or something, well, why don't you just spin up like a cosmo alpaca environment, like you have all these things available, that will.00:55:37.460 --> 00:55:37.971


They'll create them for you.00:55:37.971 --> 00:55:40.157


You don't have to allocate space, you don't have to find the hardware, you don't have to.00:55:40.157 --> 00:55:43.201


You know, worry about competing versions.00:55:43.201 --> 00:55:44.929


But again, it goes with the whole I I.00:55:44.929 --> 00:55:55.297


I'm just coming down now to just tell people what you do, I think, and maybe somebody will get it, because there are many things out there and you can't change everybody, I guess.00:55:56.204 --> 00:55:58.570


And people don't know what they don't know.00:55:58.570 --> 00:56:05.445


And in training people and working in El Salvador, there are people who are willing.00:56:05.445 --> 00:56:06.527


There are people who are eager, they're open to learn.00:56:06.527 --> 00:56:07.347


There are people who are willing.00:56:07.347 --> 00:56:08.568


There are people who are eager, they're open to learn.00:56:08.568 --> 00:56:09.989


They just don't know what to learn.00:56:09.989 --> 00:56:28.306


And once you but once you give them that guidance and you give them a learning path I believe that's a term that you've used it's like wow, here's what I can learn, here's how I, you know, do this properly and that's very effective.00:56:28.326 --> 00:56:45.193


The people who don't think to learn first and who just start writing code, who just start doing implementation, you know they're going to have some bruises and scrapes and hopefully they learn from it.00:56:45.193 --> 00:56:51.894


Hopefully the consequences aren't too significant and hopefully they learn from it.00:56:51.894 --> 00:56:53.255


Hopefully the consequences aren't too significant.00:56:53.255 --> 00:57:06.360


But an IT manager who hires a developer and is not aware of source code management, they may be a little out of their depth and maybe that's the lesson Everyone's got to learn some way.00:57:06.360 --> 00:57:10.221


Yeah, there's consequence there.00:57:10.221 --> 00:57:16.643


I don't go out and put myself out as a professional, you know, dentist or auto mechanic, right?00:57:33.333 --> 00:57:39.067


I don't pretend that that it has to be our responsibility because I could hire a third.00:57:39.067 --> 00:57:42.253


I could hire a third party or an independent consultant.00:57:42.253 --> 00:57:52.277


If I'm not, if, if it's the partner's responsibility, now I got to bring in my independent consultant, bring my partner in to have a conversation.00:57:52.277 --> 00:57:53.659


That may not be realistic.00:57:53.659 --> 00:58:06.052


I may just hire someone, just a quick development fix, but I should be able to tell that independent consultant or developer here's how you access my stuff, here's how you submit my stuff.00:58:06.052 --> 00:58:08.210


That's still my responsibility.00:58:14.085 --> 00:58:16.755


And along the lines of customer responsibility, I totally agree because that applies to the implementation as well.00:58:16.755 --> 00:58:25.297


I'm sure you both have been on implementations where the customer thinks by hiring a consultant they have effectively fully outsourced all the issues.00:58:26.186 --> 00:58:28.686


It never happens, right, never happens.00:58:28.947 --> 00:58:48.152


Exactly, and when that customer is not paying attention to their financial reports, their chart of accounts, their dimensions, their transaction entry, like if they don't have the time to be bothered by all those little details, I can tell you with a high degree of confidence how that project's going to end up right and it doesn't involve a single line of code.00:58:48.152 --> 00:58:51.802


And it project's going to end up right and it doesn't involve a single line of code, and it's not going to be pretty.00:58:51.802 --> 00:58:53.322


We don't have time for training.00:58:53.543 --> 00:59:15.672


Just set it up for us yeah, and I think it creates like if, even if you, if the partner owns that repo and it's first of all, it's going to add costs, because now you're going to bring in your partner, just to bring in an independent developer, and on top of that there's a little bit of buttheads there, because it's like oh, some partners are like, oh, why is this customer bringing in?00:59:15.784 --> 00:59:24.735


It could be the customer's responsibility, but you have to look at the size and the scope of the implementations, right?00:59:24.735 --> 00:59:29.666


Some implementations I'm not saying they're not responsible, but some of the stuff you're saying.00:59:29.666 --> 00:59:32.311


You're expecting someone to know a lot of this stuff.00:59:32.311 --> 00:59:44.956


That goes back to, I think, what steve was talking about if you one, if you have a good partner, right, and a partner doesn't have to be a partner, a partner can be, even if, at this point, if you hire someone independently, right?00:59:44.956 --> 00:59:50.873


I know independent consultants that do a very good job of telling the customers set up a repository.00:59:50.954 --> 00:59:53.358


I'm going to fork the changes, you own it.00:59:53.358 --> 00:59:57.494


So it doesn't necessarily have to be that when I say partner, it's someone you're working with.00:59:57.494 --> 00:59:58.887


I'm not in this case right.00:59:58.887 --> 01:00:06.887


So it's in essence, I think I've given up on the fight in the sense that I'm just going to follow.01:00:06.887 --> 01:00:08.070


I'm a Steve Groupie.01:00:08.070 --> 01:00:22.478


I'm going to just follow Steve's model of I'm just going to tell people what I know and hopefully they see it, they hear it, I'll do, I'll try to do sessions if they, you know, get accepted at places, and if they don't, I'll still write about it, talk about it, do whatever.01:00:22.478 --> 01:00:38.713


But I think it awareness so that, to Steve's point, consultant developers, partners understand the implications of not doing it this way because they may not know, and then customers can be aware of at least saying hey, what happens if I do this?01:00:38.773 --> 01:00:45.786


I get on the size because, like, let's say, for example, I'm a five person company, we're all accountants, you know, but we have some customization.01:00:45.786 --> 01:00:57.253


I would expect my, I would expect my partner to build that up for me, give me the documentation and say, hey, if I need to make changes, you know how do I connect.01:00:57.253 --> 01:01:07.152


I can keep all of that and then so when I do decide that I'm going to hire an independent developer for a small project, then I know how to give the max.01:01:07.152 --> 01:01:09.273


I don't need to know, like all the details.01:01:09.485 --> 01:01:10.509


You're making an assumption there.01:01:10.509 --> 01:01:11.652


To go with what Steve said.01:01:11.652 --> 01:01:13.431


You have to know that you need it.01:01:13.431 --> 01:01:22.306


How do I know that they're not just going to business central and changing something like the posting date and the next person can change the posting date again?01:01:22.306 --> 01:01:26.637


I mean, again, it goes back to yes, they may be responsible.01:01:26.637 --> 01:01:36.664


I mean, ultimately you're responsible for a lot of things that you don't know, you may not know about in your vehicle, in your house.01:01:36.664 --> 01:01:39.210


You know there's a lot of things that you use, a lot of things that you have done that ultimately be your responsibility.01:01:39.210 --> 01:01:43.617


You just need to make sure you have the right person helping you.01:01:44.219 --> 01:01:48.596


I think is what it comes down maybe that maybe the term responsible versus owning it.01:01:51.449 --> 01:01:58.175


Hey, if someone has a $10 million business, it's kind of on the small side for our industry, right.01:01:58.175 --> 01:02:06.474


I mean they might want to be responsible for their business and, yes, that means production, that means delivery.01:02:06.474 --> 01:02:07.525


That means customer service.01:02:07.525 --> 01:02:07.985


That means accounting.01:02:07.985 --> 01:02:08.271


That means paying their.01:02:08.271 --> 01:02:08.599


That means customer service.01:02:08.599 --> 01:02:09.260


That means accounting.01:02:09.260 --> 01:02:11.742


That means paying their taxes, paying their bills, collecting revenue.01:02:11.742 --> 01:02:13.731


That includes their ERP system.01:02:13.731 --> 01:02:22.815


It includes their email, their servers Like I don't like it either, right, but they're responsible for their ERP implementation.01:02:23.706 --> 01:02:33.840


If they hire a partner who doesn't perform well, unfortunately that happens and they're responsible and they're going to learn.01:02:33.840 --> 01:02:45.259


We can be at these conferences, we can do the podcasts, we can do the webinars, the blogs, everything we can, and I just try to demonstrate what I'm learning.01:02:45.259 --> 01:02:49.090


I wouldn't call myself an expert, what I'm learning, I don't even I wouldn't call myself an expert.01:02:49.090 --> 01:03:03.306


It's like, hey, I can ask five questions on a call and if that customer can sense something different, fantastic.01:03:03.306 --> 01:03:06.572


Like wait a minute, my partner didn't discuss any of these things with me.01:03:06.572 --> 01:03:15.311


Oh, really Happy to talk to you about those things and I've seen that glimmer of recognition in the room at our conference sessions.01:03:15.311 --> 01:03:19.226


And you guys were both on a panel with me at DynamicsCon, right?01:03:19.226 --> 01:03:20.688


We mentioned something.01:03:20.688 --> 01:03:28.295


You watch two people in the crowd look at each other because they're co-workers and they're like, oh my gosh, they're talking about us.01:03:28.295 --> 01:03:31.929


And they come to us and said we didn't know.01:03:31.929 --> 01:03:34.012


It's like, well, good, Now you know.01:03:34.012 --> 01:03:37.378


And now they know they have a problem.01:03:37.378 --> 01:03:41.012


Great, that's fantastic.01:03:43.306 --> 01:03:43.907


Yeah, I like it.01:03:43.907 --> 01:03:45.949


No, I mean again.01:03:45.949 --> 01:03:50.759


You are responsible and it's it's in essence you know um from.01:03:50.759 --> 01:04:02.032


For my part, I think I'll just continue to express the risks of not knowing where your source code for your extensions reside I think, is simply put.01:04:02.032 --> 01:04:04.137


I mean, that's all you can do is here's the risks.01:04:04.137 --> 01:04:08.137


Deal with it as you wish or as you may.01:04:08.137 --> 01:04:09.802


However, that saying goes over here.01:04:09.802 --> 01:04:13.213


Yeah, but this has been enlightening for me.01:04:13.213 --> 01:04:13.994


Thank you, you've.01:04:14.295 --> 01:04:25.427


You've enlightened me, um and tomorrow but, there's still a lot of uh questions that still need to be answered around this many questions you.01:04:25.509 --> 01:04:27.713


You guys got two or three more hours there's.01:04:27.974 --> 01:04:30.528


There's a lot to it, but now I'm just like is it?01:04:30.528 --> 01:04:32.637


No, there are a lot of questions.01:04:32.637 --> 01:04:37.512


It's, but it opens up like what is the proper process or what should be a process, what should customers look for?01:04:37.512 --> 01:04:42.894


But I think step one is just awareness and, as steve, as you had mentioned, just being aware that you need this.01:04:42.894 --> 01:04:47.454


Then you can ask the questions, because there are many, many ways to do this that are not complicated.01:04:47.454 --> 01:05:05.054


Like some I've talked with, they think it sounds complicated and it always goes back to my it's complicated to do it, it's complicated to manage it and you don't have time to manage it, but you have time to redo it three times, three months from now when your business is on fire.01:05:05.054 --> 01:05:09.994


Like you know, it's that old saying we don't have time to do it once, but we have time to do it four times down the road.01:05:11.445 --> 01:05:15.956


And I don't know about you, but I'm constantly learning as well.01:05:15.956 --> 01:05:19.175


I'm constantly finding mistakes that I made.01:05:19.175 --> 01:05:22.594


I'm constantly figuring out how to improve.01:05:22.594 --> 01:05:32.030


We have our own internal problems, so we're not immune from this, but I'm more than willing to be open about that, and I don't know if everyone is.01:05:32.030 --> 01:05:42.545


So it may be uncomfortable for some people to talk about this stuff, but I think if we just start talking about it if you've seen my podcast or my webinar, no, what is it?01:05:42.545 --> 01:05:43.186


What did I call it?01:05:43.186 --> 01:05:52.179


A live stream, like every week, I'm like, huh, this is what I didn't know, this is what my mistake that I made.01:05:52.179 --> 01:06:00.123


And I'm like, hey, if someone thinks I'm a fool for talking about that, it's like okay, I'm well over it.01:06:00.123 --> 01:06:01.646


Right, this is my life?01:06:01.646 --> 01:06:08.699


Um, if, if someone's perfect, great, send me that recipe of how you became perfect and I'll follow it.01:06:09.686 --> 01:06:11.373


You should start your live stream.01:06:11.373 --> 01:06:13.990


Do you have your own repo yet?01:06:13.990 --> 01:06:15.755


Do you have a repo?01:06:15.755 --> 01:06:17.208


Well?01:06:17.389 --> 01:06:20.936


that'll be Brad's dedicated SCM live stream.01:06:21.704 --> 01:06:23.192


I'm going to do this now, Steve.01:06:23.385 --> 01:06:24.650


SCM live with.01:06:24.690 --> 01:06:26.530


Brad, I'm doing this now.01:06:26.731 --> 01:06:28.512


I am, I'm going to order that green screen.01:06:28.605 --> 01:06:29.391


I've had a little bit of travel.01:06:29.391 --> 01:06:29.552


I'm doing this.01:06:29.552 --> 01:06:29.512


Now I am.01:06:29.512 --> 01:06:30.237


I'm going to order that green screen.01:06:30.237 --> 01:06:30.563


I've had a little bit of travel.01:06:30.563 --> 01:06:30.625


I can't order it.01:06:30.625 --> 01:06:32.130


I have a.01:06:32.130 --> 01:06:32.632


We'll talk.01:06:32.632 --> 01:06:33.434


We'll talk about that.01:06:34.065 --> 01:06:42.735


But no, I do appreciate what you do and I will say that nobody is perfect and all of us are learning something new.01:06:42.735 --> 01:06:50.880


I've been doing this for a long time and I tell everybody it doesn't matter how long somebody's been doing something, because if I've been doing the same thing for 20 years, I have 20 years of one year's worth of experience.01:06:50.880 --> 01:06:57.998


But even more so, in our environment it's changing rather quickly.01:06:57.998 --> 01:07:03.637


Therefore, somebody who's been doing this for 20 years may not know the best way to do things today.01:07:03.637 --> 01:07:13.878


So, and I can tell you, I've known individuals who've been working on this for two or three years that know and understand an implementation and development far better than someone who says they've been doing it for 15.01:07:13.878 --> 01:07:17.532


Right, and it's not.01:07:17.532 --> 01:07:30.869


I just want to emphasize that it's your experience with what you're doing, not the duration, and that's, I think, a lot of people often overlook, because they assume duration equals experience, where it doesn't.01:07:30.869 --> 01:07:34.077


I could tell you some stories about that as well.01:07:34.117 --> 01:07:44.231


Too Well, mr Steve, I failed on my attempt to get you to change your live stream to be 9 am Eastern, so I still have to call it the.01:07:44.231 --> 01:07:46.856


You know, lunch with Steve.01:07:46.856 --> 01:07:52.130


That's what I call it myself every time you say yeah, I call it lunch with Steve.01:07:52.851 --> 01:08:07.612


And I also now realize that I just have to just get the word out there and let it go, and I don't mean, let it go, not care, just put the word out there and let it fall on the ears that it may and what they do with it.01:08:08.432 --> 01:08:16.141


Yeah, be an offer of help and you know some people listen and those people can be your customers Excellent.01:08:16.725 --> 01:08:17.447


Excellent.01:08:18.831 --> 01:08:19.613


All you need is one.01:08:20.614 --> 01:08:23.813


All you need is one, one at a time, if you can convince one person, yeah.01:08:23.813 --> 01:08:29.756


I just want to make a difference in one person's life and I do want to get that solved with you.01:08:29.756 --> 01:08:31.411


We will have to coordinate that with some runway.01:08:31.411 --> 01:08:34.171


I mean, I don't know, a week is not enough runway for me.01:08:34.171 --> 01:08:36.072


Hey, name the month.01:08:36.072 --> 01:08:38.210


What's the best month to go?01:08:39.364 --> 01:08:43.976


November through April is the peak season or dry season.01:08:43.976 --> 01:08:56.431


If you're feeling extremely adventurous, you do may through um october rainy season, yeah, and bring a boat, waterproof shoes and you'll be.01:08:56.431 --> 01:08:58.435


You'll have an adventure, trust me.01:08:58.435 --> 01:09:02.314


But yeah, we are entering peak season, november through april.01:09:02.314 --> 01:09:06.632


So I'm going down there now gonna hang out there for thanksgiving, but uh, yeah, january I would like to go.01:09:06.632 --> 01:09:07.537


Yeah, yes, maybe after the first of the year.01:09:07.537 --> 01:09:10.407


There now going to hang out there for Thanksgiving, but, yeah, january I would like to go.01:09:10.747 --> 01:09:21.435


Yes, maybe after the first of the year, because November is done with the holiday, we may have some plans, and December I can see, but most likely January.01:09:21.435 --> 01:09:31.399


February it sounds like similar weather to here, because come May to end of October we have those things called hurricanes and rain that just doesn't stop.01:09:31.399 --> 01:09:35.493


Well, thank you, mr Steve.01:09:35.493 --> 01:09:36.576


I appreciate the conversation.01:09:36.576 --> 01:09:37.850


I always look forward to speaking with you.01:09:37.850 --> 01:09:50.671


If you would, how would someone be able to get in contact with you or see some of the great things that you're doing with the center of excellence, your live stream and many of the other, as I'd mentioned, great things and services that you do?01:09:52.534 --> 01:09:53.036


You know what?01:09:53.036 --> 01:10:15.068


I have a links page it is links plural dot steveendocom, and that has my Twitter, YouTube, podcast blog, Twitch and my company website and then I live stream on youtube every youtube and twitter every friday.01:10:15.068 --> 01:10:22.698


Um, and so yeah, I'm around, not hard to find me no, not at all.01:10:23.180 --> 01:10:23.966


Well, thank you very much.01:10:23.966 --> 01:10:25.128


It was a pleasure speaking.01:10:25.128 --> 01:10:26.471


I look forward to speaking with you again soon.01:10:26.912 --> 01:10:27.694


Okay, Take care Steve.01:10:31.125 --> 01:10:38.164


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


Thank you, brad, for your time.01:10:40.048 --> 01:10:43.518


It is a wonderful episode of Dynamics Corner Chair.01:10:43.518 --> 01:10:47.032


I would also like to thank our guests for joining us.01:10:47.032 --> 01:10:50.037


Thank you for all of our listeners tuning in as well.01:10:50.037 --> 01:11:04.557


You can find Brad at developerlifecom, that is D-V-L-P-R-L-I-F-E dot com, and you can interact with them via Twitter D-V-L-P-R-L-I-F-E.01:11:04.557 --> 01:11:17.970


You can also find me at matalinoio, m-a-t-a-l-i-n-o dot I-O, and my Twitter handle is matalino16.01:11:17.970 --> 01:11:21.618


And you can see those links down below in the show notes.01:11:21.618 --> 01:11:22.987


Again, thank you everyone.01:11:22.987 --> 01:11:24.529


Thank you and take care.
Steve Endow Profile Photo

Steve Endow

MVP

Steve Endow is a Microsoft MVP who works with Microsoft Dynamics 365 Business Central, Azure, .NET, SQL Server, and Power Platform