Episode 424: Business Central: Insights from Real-World Implementations

WEBVTT

00:00:00.600 --> 00:00:03.490
Welcome everyone to another episode of Dynamics Corner.

00:00:03.490 --> 00:00:07.530
What does it take to implement Business Central?

00:00:07.530 --> 00:00:09.025
I'm your co-host, Chris.

00:00:09.682 --> 00:00:10.285
And this is Brad.

00:00:10.285 --> 00:00:14.031
This episode was recorded on May 1st 2025.

00:00:14.031 --> 00:00:18.170
Chris, chris, chris, what does it take for a BC implementation?

00:00:18.170 --> 00:00:22.150
Migration, upgrade, re-implementation, whatever you want to call it?

00:00:22.150 --> 00:00:31.021
With us today, we had the opportunity to speak with an end user that recently had gone through a migration from 2013 to a recent version of Business Central.

00:00:31.021 --> 00:00:33.790
With us today, we had the opportunity to speak with Jesse Rama and Pablo.

00:00:33.790 --> 00:00:53.637
Hello, hello, oh, look at that, look at that.

00:00:53.637 --> 00:00:54.576
How are you doing?

00:00:55.378 --> 00:00:58.439
good, yeah, I got my sweater too, but I'm not wearing it right now.

00:00:58.579 --> 00:01:09.370
See that, see that, jesse this is uh this is uh, we're gonna get you one, even though you're not an mvp, oh wow, but you have the fancy hat I like the hat.

00:01:09.370 --> 00:01:12.085
You like my hat I'm not wearing it.

00:01:12.085 --> 00:01:17.966
I just wanted to mess with you you're the host now.

00:01:17.966 --> 00:01:24.688
That would have been a first I was gonna come in with my boston accent and start being like, hey, what's going on?

00:01:25.521 --> 00:01:30.927
That wasn't a Boston accent Get out of the box after this that's a Southern accent.

00:01:32.340 --> 00:01:33.825
Yeah, I do have a Southern accent.

00:01:33.825 --> 00:01:34.305
I'm sorry.

00:01:35.248 --> 00:01:36.691
It's okay, y'all should see me.

00:01:36.900 --> 00:01:42.628
I am tucked away in the corner of my son's bedroom because there is construction going on downstairs in my house.

00:01:42.628 --> 00:01:46.894
And then I got all the way up here and my neighbors are cutting their trees.

00:01:46.894 --> 00:01:51.581
So yeah, this is my life.

00:01:51.602 --> 00:01:52.743
It always happens to me.

00:01:52.743 --> 00:01:56.087
Oftentimes, if you know, you can see me scrambling because we do a recording.

00:01:56.087 --> 00:01:58.810
It is it's always inevitable that somebody comes and bangs on the door.

00:01:58.810 --> 00:02:08.705
Somebody just the lawn team decides to come and cut the lawn or something, yeah, and they stop, so they, they stop hopefully they're done.

00:02:08.725 --> 00:02:10.151
They're doing construction in your house.

00:02:10.191 --> 00:02:20.626
Whatever they're doing they are remodeling my shower and they're putting in a closet for me, a closet, a closet system for me, so like it's just a bunch of people in and out.

00:02:20.626 --> 00:02:21.889
It was supposed to be done by now.

00:02:21.889 --> 00:02:23.322
Are you treating this?

00:02:23.402 --> 00:02:31.759
like a bc implementation where you know staying in budget and, oh, I'm in budget the construction people are over budget.

00:02:32.001 --> 00:02:34.729
They ruined some stuff and I'm like I'm not paying for that.

00:02:34.808 --> 00:03:15.128
You did it, oh yeah well, speaking of the bc implementations, we do appreciate you taking time to speak with us this afternoon because you, as a user of Navision or Dynamics Nav re-implementation, which we hope to speak about how that process went, what you did as an organization to ensure that it went smoothly, some of the pitfalls or challenges that you uncovered that you didn't expect, maybe give some insights to someone who may be listening.

00:03:15.128 --> 00:03:18.020
But before we do that, would you mind telling us a little bit about yourself?

00:03:18.020 --> 00:03:19.043
Jessie, we'll start with you.

00:03:19.484 --> 00:03:19.784
Hi.

00:03:19.784 --> 00:03:21.026
Yes, I'm Jessie.

00:03:21.026 --> 00:03:25.093
I am the senior business central NAV support manager.

00:03:25.093 --> 00:03:33.794
So I've been with Forum for 10 years this year, but I've been in the NAV business central world for about 17 years.

00:03:33.794 --> 00:03:44.026
So other than that, you know, I do all this volunteer fun stuff for the Dynamics Communities Business Central Board and I help run the local user group meetings.

00:03:44.026 --> 00:03:53.514
And not to do a shout out, but we are having our very first local chapter meeting in Houston in June Yep, since 2019.

00:03:53.514 --> 00:03:55.084
So it's all planned in books.

00:03:55.084 --> 00:03:57.790
So just wanted to throw that out there because I'm proud of it.

00:03:58.781 --> 00:04:00.388
Excellent Congratulations which date in June.

00:04:01.640 --> 00:04:05.010
June 24th, from 10 am to 2 pm at the Microsoft Center.

00:04:06.000 --> 00:04:08.127
Excellent, excellent, hope everybody attends Me too.

00:04:08.127 --> 00:04:11.229
Look forward to seeing what the agenda is, pablo.

00:04:11.900 --> 00:04:20.714
Yes, so, pablo Hernandez, I've been with Forum for 17 years with the BC support and BC security admin team.

00:04:22.261 --> 00:04:27.833
Excellent, excellent, rama, would you mind introducing yourself to us as well?

00:04:28.019 --> 00:04:30.487
Sure, my name is Rama Satyapeda.

00:04:30.487 --> 00:04:37.529
I've been doing nav, like the development, for almost like 20 years and I enjoy doing support also.

00:04:37.529 --> 00:04:42.826
But I don't get to do a lot here in Forum, but in my previous companies I do support and develop.

00:04:42.826 --> 00:04:47.607
My background is a developer, but you know, I like doing both uh, development and support.

00:04:47.607 --> 00:04:49.853
And it's been nine years before.

00:04:50.134 --> 00:05:09.048
So in a few months I mean next year I'll be it'll be 10 years for me too excellent and just so you know rama, this is recorded, so I'm gonna go uh sign five support tickets to you right after this that's okay okay that is what you, what you have give me support work but I'm like

00:05:10.411 --> 00:05:11.279
the level 3 support.

00:05:12.826 --> 00:05:20.944
I support the support team basically when everything really goes to hell, give it to Rama.

00:05:20.944 --> 00:05:21.807
Is that how it works?

00:05:22.403 --> 00:05:26.771
oh yeah when we're done everything we can and we're stuck and we're lost.

00:05:26.771 --> 00:05:29.067
We're like Rama, we need you to look at this.

00:05:29.067 --> 00:05:33.630
We have one other internal developer as well who's not on this call that we do the same thing to.

00:05:33.630 --> 00:05:36.269
We're like you're going to have to walk through this with us, yep.

00:05:37.201 --> 00:05:38.139
Nothing ever goes to hell.

00:05:38.139 --> 00:05:41.326
So it sounds like all of you have been working there for quite some time.

00:05:41.326 --> 00:05:45.773
Working there for quite some time, and what were you using before you moved to Business Central?

00:05:45.773 --> 00:05:55.725
Nav13, nav2013r2.

00:05:55.725 --> 00:06:06.117
Nav2013r2, just shortly after you went from the roll-tailed client to out there, and with that, what made you wait to go to the business central?

00:06:05.966 --> 00:06:07.834
upgrade, or why hadn't you upgraded to the previous versions of?

00:06:07.834 --> 00:06:25.790
Nav through the years from 2013 through 2018 so technically, the first, very first project this was in the works before I even started um at this company, they were getting everybody off of nav 5 and nav NAV 2009 onto NAV 2013.

00:06:25.790 --> 00:06:32.440
So when I started, we were still moving people to that, so that just took a very long time.

00:06:32.480 --> 00:06:44.487
We were doing what one company at a time when I started yeah, yeah, we did one company or a couple companies, but there's a lot of companies in NAV 5 and NAV 2009.

00:06:45.113 --> 00:06:46.180
how many companies do you have?

00:06:47.942 --> 00:06:58.444
75 around 70 75 companies, 75 yeah, yeah, I think we tried to merge a few and now we are down to like around 50 or 55.

00:06:59.165 --> 00:07:01.690
Yeah, well, that makes sense why it took a long time.

00:07:01.771 --> 00:07:09.478
Huh, yes, I could see that 50 companies and within those 50 companies, some of them just financial companies.

00:07:09.500 --> 00:07:10.483
Yes, so what features?

00:07:10.543 --> 00:07:13.250
within the application are you using within these companies?

00:07:14.100 --> 00:07:17.952
So I would probably say about half would be finance companies.

00:07:18.012 --> 00:07:27.747
Rama, that we just do general budget, post-general budget, yeah, 25 operational companies, 25, 30 operational companies, and then the remaining 25 are finance companies.

00:07:28.048 --> 00:07:32.459
Yeah, finance companies, and the finance companies very like small.

00:07:32.459 --> 00:07:37.892
We just do like they just post a general journal entry in there once a quarter or once a month.

00:07:37.892 --> 00:07:39.466
Nothing major happens in those.

00:07:39.466 --> 00:07:43.726
The rest of them we do like sales service.

00:07:43.726 --> 00:07:55.387
Jump in anytime, pablo, and tell me more Warehouse, advanced warehousing in some we do basic with bins, in some we have inventory count.

00:07:55.387 --> 00:07:56.831
Time collection module.

00:07:56.831 --> 00:08:00.524
Thank you, what am I missing?

00:08:00.524 --> 00:08:03.552
I feel like there's more Scan guns.

00:08:05.264 --> 00:08:06.153
We're kind of across the board.

00:08:06.173 --> 00:08:08.865
Manufacturing, hello manufacturing.

00:08:08.865 --> 00:08:11.951
I was waiting for that.

00:08:11.971 --> 00:08:36.948
So it sounds like you used a lot of the application and, with having an internal development team, you had also some of your own modifications, or you might have a significant amount of modifications, and when you migrated to Business Central kind of let's walk through the process of what you had done to plan or prepare for it Did you go to Business Central online or you were using Business Central on-premises?

00:08:37.250 --> 00:08:37.671
On-prem.

00:08:37.671 --> 00:08:39.385
We got outvoted on that one.

00:08:40.480 --> 00:08:42.447
You could have voted on that one.

00:08:42.467 --> 00:08:47.351
We tried, we tried so hard and they were like nope, we're staying on-prem and we're like all right.

00:08:49.841 --> 00:08:55.072
A lot of implementations have their reasons for going on-premises and others go online.

00:08:55.072 --> 00:09:13.049
I'm happy to see that, as time is progressing, some of those limitations or reasons why I don't want to use the word limitation, but some of the reasons why some prevented or wanted to go, some of those reasons that prevented some from going online and staying on-premises, are being relaxed a little, which is nice.

00:09:13.049 --> 00:09:16.808
So there are some slight differences.

00:09:17.080 --> 00:09:22.945
Yeah, I do want to go through that process with what your process went Deciding to move to Business Central.

00:09:22.945 --> 00:09:23.547
Brad, and I want to understand.

00:09:23.547 --> 00:09:24.549
You have deciding to move to business central.

00:09:24.549 --> 00:09:26.155
You know Brad wants that, brad and I wants to understand.

00:09:26.155 --> 00:09:29.671
Like such a, you have a lot of entities, right?

00:09:29.671 --> 00:09:31.460
It's certainly a big implementation.

00:09:31.460 --> 00:09:36.445
You use all different modules within business central, I'm sure, using different add-ons.

00:09:36.445 --> 00:09:38.530
It's a lot of coordination that's happening.

00:09:38.530 --> 00:09:49.445
So, as you decide to move to business central, was it a natural path to go to Business Central or did you also look at other ERPs as well?

00:09:49.445 --> 00:09:54.193
And when you decided, what did that committee look like, right?

00:09:54.193 --> 00:09:59.572
So you know, was there change management, project management, all that stuff being put in place?

00:10:01.221 --> 00:10:02.322
So, yes, we did.

00:10:02.322 --> 00:10:15.664
Actually, there was another ERP that was being considered at the time, um, when I me and my boss actually at the time we presented business central because, uh, we have what?

00:10:15.664 --> 00:10:24.591
Seven business central employees, right, that are just specifically for support five or support to our developers and that's what we do and that's our job for this company.

00:10:24.591 --> 00:10:26.400
So we presented it.

00:10:26.400 --> 00:10:30.051
As you know, business central was the best route one because we're already on nav.

00:10:30.051 --> 00:10:47.366
So the functionality is basically the same, right, you're going to enter a sales order, the same way You're going to everything like that, right, we also told them it would be a lot more money to switch ERPs, which we all we did the work on that, obviously it would be, and they wanted to upgrade, they did not want to re-implement.

00:10:48.240 --> 00:10:53.092
So you can't upgrade to SAP or another GP, whatever you pick in the thing.

00:10:53.092 --> 00:10:57.769
You can only upgrade to BC, right, so that was kind of our walkthrough for that.

00:10:57.769 --> 00:11:09.249
And then, once we got the approval, we originally were going to jump to NAV 2018 first, and we did in the background, but we didn't do it for the, you know, for the users.

00:11:09.249 --> 00:11:12.710
Um, so we decided we could get to BC 14.

00:11:12.710 --> 00:11:14.980
Um, so we did that instead.

00:11:14.980 --> 00:11:16.405
So we did the work to get there.

00:11:16.405 --> 00:11:21.330
We started with two companies, right guys?

00:11:22.251 --> 00:11:22.432
Yes.

00:11:23.041 --> 00:11:25.346
Um, yes, we started with two of our companies.

00:11:25.346 --> 00:11:33.553
They were kind of our like test companies who do, who use a lot of the models in the system, also have the best users for us.

00:11:33.553 --> 00:11:37.291
We have a lot of power, we have power users in every ledger, so they have, like, the best users.

00:11:37.291 --> 00:11:43.128
So for that it was like we wanted them because we knew we would get the best testing out of them.

00:11:43.128 --> 00:11:44.730
Right, I have you know.

00:11:44.730 --> 00:11:45.811
So we picked them.

00:11:45.811 --> 00:11:49.196
That project for them was six months.

00:11:49.196 --> 00:11:56.932
For us it was a year, behind the scenes, right when Rama, you can probably talk more about those jumps in the background on the technical side.

00:11:58.399 --> 00:12:00.244
Yeah, I mean more.

00:12:00.244 --> 00:12:02.629
Like you know, we converted the code from.

00:12:02.629 --> 00:12:15.793
I mean, we removed most of the code from Microsoft objects and separated it in preparation for the future upgrades and then we have a script which actually copies the companies.

00:12:15.793 --> 00:12:20.830
As you know, we started with two companies and we cannot go to a different database.

00:12:20.830 --> 00:12:30.749
We started with one database with two companies and then, as we upgrade the other two or three, we just used to copy those companies into the initial upgraded company.

00:12:30.749 --> 00:12:45.606
So, yeah, the first step from NAP 13 to BC 14 took a little longer because we have all these companies and we want to make sure everything is included for all of the companies.

00:12:45.606 --> 00:12:49.250
I think it took around like a year and a half, right?

00:12:49.250 --> 00:12:51.865
Yeah, I think we started yeah a little over.

00:12:52.000 --> 00:12:59.703
We were already doing the refactoring piece right to prepare for it, and I think that was like a year and a half, two years, something like that, yeah.

00:13:00.605 --> 00:13:01.245
But then once yeah, go ahead.

00:13:01.245 --> 00:13:02.187
Yep, but then once yeah, go ahead.

00:13:02.187 --> 00:13:10.875
So you worked on all of this in the back end, using you know two to three companies as your sort of a pilot.

00:13:10.875 --> 00:13:27.985
You know you've identified your subject matter experts when you've decided to move forward and then slowly added all these other companies along the way and then kind of repeated the process to, you know, towards the other companies as well.

00:13:27.985 --> 00:13:34.287
So it created a foundation, it sounds like, for you and then kind of repeated the process slowly with the rest.

00:13:34.908 --> 00:13:35.070
Correct.

00:13:35.149 --> 00:13:39.522
Yeah, so the first one we did we took we were giving a timeline of six months.

00:13:39.522 --> 00:13:42.307
So we have three PMs that helped with this.

00:13:42.307 --> 00:13:45.894
Right, we have three internal PMs, our team and then the SMEs.

00:13:45.894 --> 00:13:49.369
So you know, we we follow the regular phases of a project.

00:13:49.369 --> 00:14:05.133
We kicked off, we went through um like we demoed it for everyone because we did and this is going to probably surprise y'all, but we did go to the web client to be seen on BC 14, um, which was not a fun thing at first but it was beneficial.

00:14:05.173 --> 00:14:08.346
When we took the next jump, um to get them used to it.

00:14:08.346 --> 00:14:10.474
Uh, so we, we did it six months.

00:14:10.474 --> 00:14:16.910
They kind of like helped us stabilize all the major issues that came out of that um as we were doing testing for that.

00:14:16.910 --> 00:14:21.565
And then when we started doing the rest of the groups, which I think we did what three more groups?

00:14:21.565 --> 00:14:23.167
It was like six at a time.

00:14:23.167 --> 00:14:30.316
After that, those we did in four months at a time each round.

00:14:30.316 --> 00:14:35.072
Yeah, so it was pretty fast-tracked after the first round was kind of complete.

00:14:36.568 --> 00:14:37.220
You have some of the testing.

00:14:37.220 --> 00:14:53.308
So, going from 2013 to BC-14, you chose to upgrade versus re-implement, which means that you brought all of your historical information over and had that as part of the upgrade.

00:14:53.308 --> 00:14:59.530
The other point that you mentioned is you had a lot of modifications within the system and you decided to refactor that.

00:14:59.530 --> 00:15:08.104
Well, you had to refactor the code in essence to accommodate the future development and the way that the extension structure is for coding.

00:15:08.104 --> 00:15:12.293
How did you determine which modifications to keep?

00:15:12.293 --> 00:15:23.029
Did you go through a phase of reviewing the functionality of Business Central versus the modifications you have put in place to see which modifications you bring forward?

00:15:23.029 --> 00:15:32.285
Because I know personally that's always been a challenge with organizations upgrading or even migrating or re-implementing Business Central from an earlier version.

00:15:32.285 --> 00:15:44.067
They have a lot of modifications they made, they spent a lot on those modifications in both time and money, and sometimes, before they even touch it, they want to bring all that stuff forward.

00:15:44.067 --> 00:15:53.285
What process did you go through to evaluate which modifications to bring?

00:15:53.306 --> 00:15:54.509
forward versus the functionalities within Business Central.

00:15:54.509 --> 00:16:15.163
So basically what we did was we have an external Excel actually Google Docs actually where we used to have customization specified for each company separately, like if a company requested it, we used to keep track of which company requested it and how many companies are going to use this.

00:16:15.163 --> 00:16:20.542
So we had something in place to identify how many customizations we have.

00:16:20.542 --> 00:16:24.857
I mean, may not be 100%, it's basically when I started in forum.

00:16:24.857 --> 00:16:26.861
From then we kept track of it.

00:16:26.861 --> 00:16:28.392
It's from 2016.

00:16:28.392 --> 00:16:41.144
So when we started with the first two companies, we would go and see how many customizations are requested by this company, and I know how many are being used by other companies.

00:16:41.144 --> 00:16:49.500
So we would go to the power users and ask them are you really using these customizations anymore?

00:16:49.500 --> 00:16:54.916
They would say yes, no, and that would let us know okay, how much should we keep it?

00:16:55.330 --> 00:16:58.893
And the second step is when we are merging the code with Microsoft.

00:16:58.893 --> 00:17:05.003
Most of the times you know it's similar, you know the field convention or whatever.

00:17:05.003 --> 00:17:09.776
So then when we're merging, actually we had an external company help us.

00:17:09.776 --> 00:17:15.012
So they would let us know okay, we have this code, do you want to still keep it or no?

00:17:15.012 --> 00:17:18.461
You know, of course I had me and my other developer.

00:17:18.461 --> 00:17:20.976
We have to analyze and make sure, okay, we need it or not.

00:17:20.976 --> 00:17:24.901
So it's a little bit of manual work also.

00:17:24.901 --> 00:17:28.517
And then going to the business and we had.

00:17:28.517 --> 00:17:36.021
It's not easy but we had something in place that would help us to identify all these customizations, which ones to keep, which ones to remove.

00:17:37.152 --> 00:17:47.558
You made a great point on what other end users or people that want to decide to move to Business Central to really have in place.

00:17:47.558 --> 00:17:57.539
You had mentioned that you've documented the development or customizations you've had in Nav and then you quickly identified okay, are they being used?

00:17:57.539 --> 00:18:09.023
So you're doing an internal discovery and I appreciate you mentioning that because you know a lot of times some of these you know businesses that's coming from Nav go into Business Central.

00:18:09.023 --> 00:18:10.266
They don't have those documented.

00:18:10.266 --> 00:18:14.076
So you putting some work behind that, some effort.

00:18:14.076 --> 00:18:18.962
It really prepared you to identify okay, do we need to bring this technical debt or not?

00:18:19.604 --> 00:18:19.785
Yep.

00:18:19.924 --> 00:18:20.125
Right.

00:18:20.125 --> 00:18:27.041
So I think that's a fantastic way to get yourself on a good foundation.

00:18:28.523 --> 00:18:28.684
Yep.

00:18:28.684 --> 00:18:34.502
That really helped us to identify what to keep and what to eliminate from the customization.

00:18:34.502 --> 00:18:36.814
And also at the end of the day.

00:18:36.834 --> 00:18:38.519
I mean, it's about standardization as well.

00:18:38.519 --> 00:18:47.265
So you want to standardize across companies and you want to make sure, okay, if there is a customization that could help another company, then they can utilize that, we can keep it.

00:18:47.265 --> 00:18:49.375
So that was another big thing.

00:18:50.638 --> 00:19:01.326
Yeah, and just to add to that too, a part of this round of upgrades that we did to get to BC 14, we used to have like 20 different posted sales invoices.

00:19:01.326 --> 00:19:02.932
Now we have one per country.

00:19:02.932 --> 00:19:12.142
Like, we standardize a lot of those documents so when they ask for updates we don't have to update 20 documents, we can just update the one or things like that.

00:19:12.142 --> 00:19:16.001
So we did a lot of document standardization on top of that.

00:19:16.001 --> 00:19:19.997
But, and reports some of the reports we had like two or three versions of.

00:19:19.997 --> 00:19:21.673
We were able to standardize those as well.

00:19:21.673 --> 00:19:26.192
But I mean data-wise you can't really standardize that once it's in there.

00:19:26.192 --> 00:19:29.421
So a lot of it, some of it like unit of measure, has been a big issue for us.

00:19:29.421 --> 00:19:34.392
In some locations it's EA and others it's each things like that.

00:19:34.392 --> 00:19:38.993
But we did get to standardize what we could while we were doing this.

00:19:40.694 --> 00:19:44.696
No, it's excellent and it is a great exercise, as Chris had pointed.

00:19:44.696 --> 00:19:52.540
You can do an inventory of what you have and what you need and only bring forward what you need as well, which is a big help.

00:19:53.141 --> 00:19:53.540
It's worth.

00:19:54.501 --> 00:20:14.894
In my opinion, it's worth the effort and the time that you may spend, as you're going through an upgrade or a re-implementation, to really take a step back in inventory of what you have, and through this process did you have to do any data you mentioned the unit of measure Are there?

00:20:14.913 --> 00:20:16.739
any other data cleansing or data standardization considerations that you had to make?

00:20:16.739 --> 00:20:17.161
We had to okay.

00:20:17.161 --> 00:20:20.170
So was that on the BC 14 jump we had to remap item categories?

00:20:20.170 --> 00:20:21.875
Is that when it changed to the hierarchy?

00:20:22.417 --> 00:20:22.699
Yes.

00:20:23.431 --> 00:20:27.259
So we had to get that mapping redone and reloaded.

00:20:27.259 --> 00:20:28.122
What else was there?

00:20:28.122 --> 00:20:29.936
Was there another one that I can think of?

00:20:33.993 --> 00:20:36.599
No but what we did was yeah, it was a main one.

00:20:36.780 --> 00:20:42.221
It was a big deal, all the open documents you know, since if you don't go to the next version it'll be there.

00:20:42.221 --> 00:20:51.333
So what we did was we cleaned up a lot of open documents you know, like logs and everything, before upgrading.

00:20:51.333 --> 00:20:57.374
We didn't want to do all the data, so we did quite a few cleanup in every jump we did we could.

00:20:57.374 --> 00:20:58.115
Yeah.

00:20:58.375 --> 00:21:08.886
And we did have some fields that ended up being that we customized, that ended up being standard fields, that we mapped during the upgrade process and got rid of our custom field.

00:21:08.886 --> 00:21:12.337
I can't think of any off the top of my head.

00:21:13.150 --> 00:21:14.935
External document number reference number.

00:21:14.935 --> 00:21:15.979
There you go.

00:21:15.999 --> 00:21:27.030
Thank you, I knew you would remember, paula, this is me.

00:21:27.030 --> 00:21:29.155
We started this project in what 2022, 2022.

00:21:29.155 --> 00:21:34.250
We started this project so, and we got to 2024, wave two uh in march march, was it march, we went live with that.

00:21:34.269 --> 00:21:36.134
Yeah, so we just finished.

00:21:36.193 --> 00:21:38.519
We just got up to date in march and just finished.

00:21:38.599 --> 00:21:40.724
So yeah, well it's it.

00:21:40.724 --> 00:22:13.355
It does take some up to date in March and just finished no-transcript well, we had to jump in between there, didn't we?

00:22:13.355 --> 00:22:15.357
You went to 18 or no.

00:22:15.377 --> 00:22:19.503
We didn't go from 14 to 23 and then to no NAB 2013.

00:22:19.523 --> 00:22:21.317
He's talking about NAB 2013 to BC.

00:22:21.337 --> 00:22:21.538
14.

00:22:21.538 --> 00:22:22.811
Bc.

00:22:22.811 --> 00:22:23.816
14 to 23.

00:22:25.402 --> 00:22:27.496
Bc 23 to BC 25.

00:22:27.496 --> 00:22:29.194
5 to the 8.

00:22:29.214 --> 00:22:33.656
Whatever you pick it, I don't know why he did that.

00:22:34.351 --> 00:22:38.229
Everybody still has the same issue with version numbers right, he's so confusing.

00:22:38.229 --> 00:22:39.954
I have that issue daily.

00:22:41.109 --> 00:22:49.602
You know, it's 25, it's 24, it's 23, it's 2025, wave, one which is 26, which is it's I I don't know they should.

00:22:49.622 --> 00:22:53.452
Yeah, yeah, it's very confusing, but yeah.

00:22:53.452 --> 00:22:54.797
So we we took our time.

00:22:54.797 --> 00:22:58.637
Getting to BC 14, right Rama, we did it ledger per ledger.

00:22:58.637 --> 00:23:01.222
We getting to BC 14, right Rama, we did it ledger per ledger.

00:23:01.222 --> 00:23:07.439
We put them on the web client because we knew we were jumping again pretty fast, so we wanted them to be used to that view rather than that classic view, that Windows view.

00:23:07.439 --> 00:23:11.400
So when we jumped to 23, everybody went at one time.

00:23:11.400 --> 00:23:15.150
We didn't take them per company, so that was a fun job.

00:23:15.530 --> 00:23:19.301
So organizationally, you went from 2013 to BC 14.

00:23:19.301 --> 00:23:21.137
They were functioning on BC-14.

00:23:21.137 --> 00:23:25.219
Then you did another migration to 2024, wave 2.

00:23:25.219 --> 00:23:28.938
Or to 23 Wave.

00:23:29.491 --> 00:23:30.415
No 24, Wave 2.

00:23:31.570 --> 00:23:35.278
We had to jump in between there Between 14 and 24, wave 2.

00:23:35.278 --> 00:23:37.836
We went live last August with it.

00:23:38.730 --> 00:23:39.326
Yeah, that is BC-2023.

00:23:39.326 --> 00:23:39.778
2030, yeah, so you went live last August with it.

00:23:39.778 --> 00:23:40.443
Yeah, that is BC 2023.

00:23:42.054 --> 00:23:44.664
So you went from 23 then to 24.

00:23:44.664 --> 00:23:46.537
You can see why we're confused.

00:23:48.092 --> 00:23:48.855
We don't know where we are.

00:23:51.270 --> 00:23:56.083
Okay, so so, and you did that jump to for one.

00:23:56.083 --> 00:23:59.538
It sounds like for them to be familiar with the application.

00:23:59.538 --> 00:24:01.092
Yeah, was there?

00:24:01.092 --> 00:24:06.490
Another consideration Is that when you converted the extensions from the code from CAL to AL as well?

00:24:06.529 --> 00:24:08.116
Yes, from the BC14.

00:24:08.116 --> 00:24:11.103
Yeah, BC14 to 23 is when we converted the code.

00:24:11.747 --> 00:24:12.369
Okay, yeah.

00:24:12.369 --> 00:24:19.236
So your first step was to review your modifications, determine what you need to bring forward.

00:24:19.236 --> 00:24:22.618
You made and brought those forward to BC 14 and Cal.

00:24:22.618 --> 00:24:27.323
You then went through and did some data sanitization.

00:24:27.323 --> 00:24:29.785
I'll call it to the best you could to clean it up a little bit.

00:24:29.785 --> 00:24:41.692
Then you made at that point you had to now go to 23, which was, with 14 being the last version where you could use cal right.

00:24:41.692 --> 00:24:44.619
23 is now where your full extensions.

00:24:44.619 --> 00:24:47.950
What was the process like for migrating the code to 23?

00:24:50.892 --> 00:25:14.281
um, I mean as to al I should say right yeah, yeah, when, like as I mentioned, you know, even in the NAP 13, when we did the refactoring in the back end, we had the NAP 2018 database where we moved all the code to functions and that helped our external team to move from BC14-Cal to AL.

00:25:14.281 --> 00:25:30.873
So I mean, it was we already gave them outlines, you know, defined everything, so they just had to move the code from cal to al for us converted that's a that's a great strategy because you went to bc14.

00:25:31.314 --> 00:25:38.778
Um, it kept the back end in terms of cal, uh, but you did that so that you have a better user adoption, to get them very comfortable using the web client on bc14.

00:25:38.778 --> 00:25:41.829
So when, when you did that so that you have a better user adoption, to get them very comfortable using the web client on BC 14.

00:25:41.829 --> 00:25:51.505
So, when you did the CAL to AL in 2023, it didn't really affect so much with the users because it's like hey, I'm already in BC 14.

00:25:51.505 --> 00:25:53.777
I'm comfortable with the layout and the look.

00:25:53.777 --> 00:25:58.318
The user adoption 23 is like oh, we're just with no more features.

00:25:58.318 --> 00:26:00.913
Yeah, right, yeah, that's exactly what it was.

00:26:00.993 --> 00:26:04.296
That was the exact plan, yeah exactly, yeah, pc 14 web client.

00:26:04.316 --> 00:26:14.079
Of course, as you know, that was like there's some limitations in it, and they were excited when we kept saying that, okay, all these things will be fixed in 23, next version.

00:26:14.079 --> 00:26:23.678
So and for them they really they didn't have any difference when they upgraded 23, except that they have more features available.

00:26:23.678 --> 00:26:25.082
So that's fine.

00:26:25.082 --> 00:26:28.838
And the backend side?

00:26:28.838 --> 00:26:34.161
They don't need to know what's happening on the backend side and we are already preparing on from 13 itself to 14.

00:26:34.161 --> 00:26:44.159
And then when we had to move to the AL on the 23, so it was not that bad as we thought, like all the code conversion was good.

00:26:44.671 --> 00:26:46.417
Was it fun when they went to BC 14?

00:26:46.417 --> 00:26:49.150
You know, bc 14 web client was, you know, a fun one, right?

00:26:49.150 --> 00:26:51.978
And then so you had to convince them like, hey, it's going to get better guys.

00:26:51.998 --> 00:26:52.800
It's going to get better.

00:26:52.800 --> 00:27:02.558
The main issue with BC 14 is the personalization it sucks Like it's terrible and that was like our biggest complaint.

00:27:02.558 --> 00:27:07.238
They were jumping in and out of role centers trying to change things Like you know it's.

00:27:07.238 --> 00:27:08.121
They couldn't.

00:27:08.121 --> 00:27:14.880
They just couldn't do the things that you can do in nap 13 when you personalize Right, and that's like a big deal to have your own view of how you look at the system.

00:27:14.880 --> 00:27:16.654
So we were like just hang on.

00:27:16.654 --> 00:27:18.080
When we get to 23, it gets better.

00:27:18.080 --> 00:27:19.064
Please hang on.

00:27:19.084 --> 00:27:24.617
But, like every group we rolled out, we would get ticket after ticket after ticket.

00:27:24.617 --> 00:27:26.758
I hate, I can't personalize.

00:27:26.758 --> 00:27:28.036
I hate it, I hate it, I hate it.

00:27:28.036 --> 00:27:30.298
That was our biggest issue, right.

00:27:31.271 --> 00:27:32.375
The biggest one, oh yeah.

00:27:33.337 --> 00:27:36.778
So a couple of our ledgers.

00:27:36.778 --> 00:27:43.561
It depended on the phase right, so we started in 2022 and I think all the way till what August of last year.

00:27:43.561 --> 00:27:49.721
So we had, you know, people were coming in each phase but they had to live in BC 14.

00:27:49.721 --> 00:27:50.603
Yes.

00:27:50.864 --> 00:27:52.375
Yes, not happy with this either.

00:27:52.630 --> 00:27:55.471
And they were like but we kept giving them the hope, we're like, we're almost there.

00:27:55.471 --> 00:27:56.192
We're almost there.

00:27:56.192 --> 00:27:58.973
You know when we went into testing for BC 23,.

00:27:58.973 --> 00:28:00.795
You could see people were happier.

00:28:00.795 --> 00:28:05.718
Just with the personalization, just with bookmarking, they're like oh, I get my bookmarks Just being able to bookmark.

00:28:05.718 --> 00:28:06.818
Yeah, it was funny.

00:28:07.479 --> 00:28:08.559
That made me laugh, brad.

00:28:08.559 --> 00:28:13.583
Remember hope isn't a strategy, but it sounded like this was a strategy and it worked.

00:28:13.623 --> 00:28:15.124
Yeah, it worked, it works.

00:28:15.124 --> 00:28:16.984
I mean yeah, but we had to keep going.

00:28:16.984 --> 00:28:20.748
But if we would have stopped, I think they would have killed us at some point.

00:28:41.750 --> 00:28:43.076
No, it does, because the product matured over the years as well.

00:28:43.076 --> 00:28:43.898
I mean, it was a big jump even back then.

00:28:43.898 --> 00:28:48.641
I'm it so that they could get everybody to it and then start hearing some of the things that they know that they needed to invest, to add it sounds like.

00:28:48.661 --> 00:29:02.503
I don't know if that was the case, but it's almost like like what you're saying just bring everybody there, get everybody to a certain stable point, then now take into consideration what people are missing and what people are asking for and then invest and add to that for them to have it.

00:29:02.503 --> 00:29:08.261
So, and it's an interesting journey that you have.

00:29:08.261 --> 00:29:13.840
So now you went from 14 to 2024.

00:29:13.840 --> 00:29:18.619
Wave two is where you ended up, yes, and now you just finished the switch.

00:29:18.619 --> 00:29:19.633
Has the dust settled yet?

00:29:20.476 --> 00:29:21.351
yeah, actually it has.

00:29:21.351 --> 00:29:25.380
Um pablo actually ran that project so you could probably speak to it.

00:29:25.380 --> 00:29:26.462
The best pablo, I mean.

00:29:27.192 --> 00:29:33.150
You were in the, you're in the thick of it yeah, I mean we had less than 20 issues really reported.

00:29:33.150 --> 00:29:40.763
Most of them were due to some of the release included pages that we had custom.

00:29:40.763 --> 00:29:48.824
So our custom pages were replaced with now the standard Business Central, like Service Archive, for example.

00:29:48.824 --> 00:29:51.479
We had a custom for that, so that had to get replaced.

00:29:51.479 --> 00:29:53.919
So there were some permissions that were also required for that.

00:29:53.919 --> 00:30:06.482
So most of the issues that we had were related to permissions to new objects and let's see, maybe our extensions that's just about it or add-ons, something like that.

00:30:06.482 --> 00:30:07.265
Wow, that's excellent.

00:30:07.930 --> 00:30:19.224
So when you went from 2013 all the way up to BC24, what was the ratio like in terms of changing business processes versus customization?

00:30:19.224 --> 00:30:21.894
Clearly, there's some things that you didn't bring over.

00:30:21.894 --> 00:30:25.323
You know, was there a lot of that business process changes?

00:30:26.631 --> 00:30:28.615
I don't think there was anything like major.

00:30:28.615 --> 00:30:30.378
We did have to leave behind.

00:30:30.378 --> 00:30:41.441
Um, we had our own document attachment process and NAV 13 that did not upgrade, but we moved everybody to just regular attachments and and people seemed to love that more.

00:30:41.441 --> 00:30:47.242
I don't think we had, except it didn't exist on the service side, but we built that for them.

00:30:47.242 --> 00:30:52.142
But I can't think of any other major process change that happened.

00:30:52.570 --> 00:30:54.537
I think the other one was templates.

00:30:54.537 --> 00:30:55.240
Item templates.

00:30:55.871 --> 00:31:00.828
Oh item templates yeah, mm-hmm, yeah, so they have the.

00:31:00.828 --> 00:31:07.720
You know, in NAV 13 and BC 14, they had their item templates that they could use and set up what's mandatory, etc.

00:31:07.720 --> 00:31:11.431
But now you have in BC 25, you have your.

00:31:11.431 --> 00:31:13.875
I'm not even sure what the difference.

00:31:13.875 --> 00:31:18.487
I think it's configuration templates, maybe, and now in BC it's item templates.

00:31:18.487 --> 00:31:30.599
So some of those fields that were included in NAV 13 and BC 14 are no longer available on the standard item templates that they had that they have to use now in BC 25.

00:31:30.599 --> 00:31:31.840
So we're still battling that one.

00:31:33.508 --> 00:31:38.748
Yeah, yes we are still battling that one in the UK.

00:31:38.748 --> 00:31:39.709
Well, that sounds like a good one.

00:31:39.709 --> 00:31:50.240
So, looking back at the implementation and how you went through the planning, so you did the demonstrations to validate the product that you were moving to.

00:31:50.240 --> 00:32:05.119
You viewed your customizations, you did some data sanitization, you did an initial jump to increase user adoption and, I'm going to assume, to also test the functionality as you migrated from Cal, which was the wild wild West, to an organized version of Cal.

00:32:05.119 --> 00:32:11.667
Then you converted your AL code and then you migrated up to the version of business central that you're running now.

00:32:11.667 --> 00:32:13.273
That's a lot.

00:32:13.756 --> 00:32:16.727
It doesn't sound like a lot and people don't realize it's a lot.

00:32:16.727 --> 00:32:17.848
It sounds like it's so easy.

00:32:17.848 --> 00:32:19.212
That's it.

00:32:19.212 --> 00:32:19.834
You summed it up.

00:32:19.834 --> 00:32:25.355
But hey, look that last jump from like 23 to whatever we're calling this version we're on right now 25.

00:32:25.355 --> 00:32:27.630
Yeah, that was like a breeze.

00:32:27.630 --> 00:32:29.613
We just called that a monthly release for us.

00:32:29.794 --> 00:32:31.561
I don't yeah that one was clean.

00:32:31.561 --> 00:32:33.351
That one was clean, that one was super clean.

00:32:33.565 --> 00:32:40.576
So our goal moving forward because we're on prem, so our goal moving forward is to always be, I think what two jumps behind Rama?

00:32:40.576 --> 00:32:46.431
Maybe be I think what two jumps behind rama, maybe one jump.

00:32:46.431 --> 00:32:47.395
If we can, if it looks good, um, that way we can.

00:32:47.395 --> 00:32:50.508
You know, we can work out kinks and stuff like all those kinks get worked out before we make that next jump.

00:32:51.451 --> 00:33:02.766
Um, so, but you, know, the more current you stay, the easier it gets the easier it gets, yeah it was well because just you don't have as radical changes as because they are evolving.

00:33:02.766 --> 00:33:10.599
The application, add in features toin functionality, the changing the data structure, which is, again, it's a normal part of the evolution of software as business needs.

00:33:10.599 --> 00:33:13.795
But if you can stay current with it, that's the advantage of the online version.

00:33:13.795 --> 00:33:14.679
You stay current with it.

00:33:14.700 --> 00:33:18.775
All the time you don't have to go through a three-year implementation for each step.

00:33:18.775 --> 00:33:21.528
Hopefully you can do it a little bit easier.

00:33:21.528 --> 00:33:28.352
So, as far as the movement of the data, how did you move the data as you upgrade it?

00:33:28.352 --> 00:33:30.356
Did you use the standard tools for that?

00:33:30.356 --> 00:33:32.488
Did you have to get?

00:33:32.907 --> 00:33:42.230
Most of them are standard tools, but we have quite a few custom fields, so we had to include our custom fields also.

00:33:42.230 --> 00:33:46.688
Uh yeah, we, we didn't spend a whole lot.

00:33:46.688 --> 00:33:48.873
It's most of them the standard uh tools.

00:33:48.873 --> 00:33:51.137
Only we used standard Microsoft tools.

00:33:51.646 --> 00:33:54.675
I'm very happy to hear that, because I know others.

00:33:54.675 --> 00:34:07.448
I've known others that tried to do other external ways and sometimes they paid for it right because the, the, the way it is of course done in extensions is all the custom fields are in a different table.

00:34:07.971 --> 00:34:13.688
They give us EXT as an appending to the standard tables, which is a good thing.

00:34:13.688 --> 00:34:18.393
So I mean we use the standard Microsoft tools to convert all the data.

00:34:18.664 --> 00:34:19.489
Yeah, that's excellent.

00:34:19.489 --> 00:34:25.213
I'm happy to hear that, and if you have a lot of data to move, it must have taken some time to run?

00:34:25.213 --> 00:34:25.534
How much?

00:34:25.534 --> 00:34:27.139
If you can say, I mean any of this stuff.

00:34:27.139 --> 00:34:28.744
If you cannot say it, I understand as well.

00:34:28.764 --> 00:34:32.536
I think one ledger was what 48 hours or something.

00:34:33.586 --> 00:34:35.492
Overall the whole database is.

00:34:35.492 --> 00:34:37.237
Our database is 900 GB.

00:34:38.985 --> 00:34:40.746
So it's 900 gigabyte Gig, right yeah.

00:34:40.746 --> 00:34:42.907
So it's 900 gigabyte, Right yeah.

00:34:42.907 --> 00:34:45.831
And it took you how long to move it.

00:34:45.831 --> 00:34:49.393
It must have been challenging to do individual companies.

00:34:49.893 --> 00:34:51.436
Right, not to BC14.

00:34:51.436 --> 00:34:52.215
It wasn't, was it?

00:34:52.215 --> 00:34:53.757
That one was not that bad.

00:34:54.018 --> 00:34:55.679
No, no, the latest upgrade.

00:34:55.679 --> 00:34:58.422
We did all these 800, 900.

00:34:58.422 --> 00:34:58.981
Gb.

00:34:58.981 --> 00:35:02.065
It took like 15 hours, wow, that's good.

00:35:02.605 --> 00:35:03.489
That's not that bad at all.

00:35:04.125 --> 00:35:10.333
There's a few things we did after that, which is not related to the upgrade, but we included it because it's the cleanup process and all.

00:35:10.333 --> 00:35:17.237
But in general, the Microsoft upgrade process didn't take like 15, not more than 20 hours definitely.

00:35:18.239 --> 00:35:19.463
There you go yeah.

00:35:19.865 --> 00:35:22.914
We had to do it over the weekend, used the standard tools?

00:35:22.934 --> 00:35:24.161
Yes, for sure do all the weekend Used standard tools.

00:35:24.161 --> 00:35:24.644
Yes, yeah, sure, yeah.

00:35:25.085 --> 00:35:26.130
No, the standard tools were into it.

00:35:26.130 --> 00:35:37.985
So, looking back at this, if you could summarize, you know from each of you what are some things that you thought went really really well and because of what, for whatever reason.

00:35:37.985 --> 00:35:43.150
From preparation or planning, you know what went really well because of that and from preparation or planning, you know what went really well because of that.

00:35:43.150 --> 00:35:52.418
And then maybe, now that the dust is settling as we discussed, what would you have done differently or what have you uncovered as you went through that process?

00:35:52.418 --> 00:36:07.304
So somebody else who may be going through the similar journey, taking pieces every implementation is different but they may have not thought of something that maybe that you realize you should have or may have done differently, not thought of something that maybe that you realize you should have or may have done differently.

00:36:09.905 --> 00:36:14.855
I'll say one of the things that I think we did really well is we have a very strong group of power users in every ledger that we depend on for testing.

00:36:14.855 --> 00:36:22.057
So, like my team will internally test, right but we don't know everyday functionality of what goes on in every one of those ledgers.

00:36:22.057 --> 00:36:24.190
So when we identified them before we kicked in every one of those ledgers.

00:36:24.190 --> 00:36:31.753
So when we we identified them before we kicked off every one of these projects and we asked them to break our system, literally we were like please break it, do what you can to break it.

00:36:31.753 --> 00:36:36.552
We want to know, and I think that was like the biggest thing that we did.

00:36:36.552 --> 00:36:41.675
That was helpful for us during this upgrade, cause we caught a lot of stuff in the first round.

00:36:41.675 --> 00:36:50.365
I think that would have been so major show-stopping if we had four or five going at a time, like four or five ledgers going at one time.

00:36:51.809 --> 00:36:57.380
Just to jump into that, you had SMEs that worked with you on the testing.

00:36:57.380 --> 00:37:04.637
Going through this process, often with the implications of challenges, is how much time do you give someone to do testing?

00:37:04.637 --> 00:37:07.514
How do you manage the testing to make sure that they're actually testing?

00:37:07.514 --> 00:37:10.153
Did you have any tools in place to help with the testing?

00:37:10.153 --> 00:37:13.494
And then what about what some people say the day job?

00:37:13.494 --> 00:37:21.838
Because as you're going through this implementation, you may have these power users and they do more than just test.

00:37:22.085 --> 00:37:26.237
They do just more than I'm assuming know see how things are working.

00:37:26.237 --> 00:37:27.751
They do have a day-to-day work for it.

00:37:28.346 --> 00:37:36.353
But how did you manage that to allow them to have time to test, and how did you track the testing and come up with use case scenarios for them to test?

00:37:36.353 --> 00:37:37.429
What was that process like?

00:37:38.405 --> 00:37:41.798
I'll give that one to Pablo, because he just did the last round of it, so he's probably got it fresh in his mind.

00:37:41.798 --> 00:37:45.186
I'll give that one to Pablo, because he just did the last round of it, so he's probably got it fresh in his mind?

00:37:45.206 --> 00:37:45.648
Yeah, so definitely.

00:37:45.648 --> 00:37:49.132
I mean, we took the release notes and those release notes.

00:37:49.132 --> 00:37:50.773
We divided those up.

00:37:50.773 --> 00:38:08.498
We were seeing what was going to impact us, what wasn't Like some of the AI stuff that's in there, the co-pilot things, I mean we're on-prem, so that's not going to affect us.

00:38:08.498 --> 00:38:16.400
So we kind of took those out of the equation and we just worked on what was going to impact all of our ledgers and then we assigned those to our SMEs on our support team and those SMEs tested internally and then we created the test scripts if needed for our end users to actually test.

00:38:16.400 --> 00:38:22.853
We set a deadline for them to test and then, once they passed it, then we were good to go.

00:38:22.853 --> 00:38:26.262
We were good to to release that with the BC 25.

00:38:27.125 --> 00:38:28.630
Yeah, and that one was for the 25.

00:38:28.630 --> 00:38:39.304
For the rest of them, we actually have super scenarios that we established a long time ago, um, that we make all of our and we use TFS um for testing.

00:38:39.304 --> 00:38:41.552
So we make them go in and sign off on them in there.

00:38:41.552 --> 00:38:51.929
Um, for you know, they're very generic test scripts, basically like the basics to creating a sales order, you know, shipping a sales order, invoicing, whatever.

00:38:51.929 --> 00:38:58.389
Um, if they have any other fields that they require, things like that, we ask them to make sure they test them on their own.

00:38:59.251 --> 00:39:04.199
Um, for all of these updates that we've done, we have sessions.

00:39:04.445 --> 00:39:16.311
We have two-hour sessions with the power users where we make them sign off on the test scripts and do the actual testing, and then we do separate sessions for training for everybody else who wants to join.

00:39:16.311 --> 00:39:19.371
Everything gets recorded so if someone can't join they can watch it later.

00:39:19.371 --> 00:39:38.306
We do have certain power users who do go above and beyond for us and they would take, like, if they're in like sales, they would actually take five or 10 orders they entered in their live environment during the day and they'd spend an hour at the end of the day entering these types of orders in to the test environment just to have real live kind of scenarios.

00:39:38.306 --> 00:39:41.313
So we're kind of lucky with those.

00:39:41.313 --> 00:39:42.356
We't require those.

00:39:42.356 --> 00:39:44.148
We only have to have a sign off on a test script.

00:39:44.148 --> 00:39:47.788
But we do ask for those kinds of things so we do have.

00:39:47.788 --> 00:39:55.324
Like I said when I say our power users are the best, like we have some really good power users out there that want to make sure they function great when we're live.

00:39:55.324 --> 00:39:56.838
So it helps us out.

00:39:56.858 --> 00:40:31.971
That's fantastic to hear like you know you giving that and I know Brad and I had plenty of conversations with others in the community where you have to give an opportunity for them to be able to test, and it sounds like you have that planned out where you're giving them two hours, you know, whatever day that is, and just all they do is like, hey, you're allowed to do this, you're encouraged to test, you're allowed to do this, you're encouraged to test, you're encouraged to break the system and get comfortable with it and not reprimand them for you know, hey, you're not meeting your day-to-day task.

00:40:31.971 --> 00:40:33.371
You know what I mean.

00:40:33.371 --> 00:40:34.532
And then do it at the same time.

00:40:34.532 --> 00:40:35.913
Help us implement this thing.

00:40:35.913 --> 00:40:42.516
So you have one of those like I hate to say, rare, it is, it is.

00:40:42.615 --> 00:40:46.077
It took us a long time to get these power users on board too.

00:40:46.077 --> 00:40:50.519
I think it's gotten better with every jump we've done.

00:40:50.519 --> 00:40:53.382
I think they've learned, but like it took us a while.

00:40:53.382 --> 00:41:01.346
But yeah, we really do have great power users that do that we also.

00:41:01.346 --> 00:41:03.010
I mean that environment was it's it's, it's a testing environment.

00:41:03.010 --> 00:41:03.833
I think it was there for what?

00:41:03.833 --> 00:41:05.739
Two, three months for them to test in during the whole process.

00:41:05.739 --> 00:41:06.059
What cause?

00:41:06.059 --> 00:41:14.690
We were doing sessions and we were like you don't have to wait for us, you can log in right now and start your testing, we're just going to have the session anyways, kind of thing.

00:41:14.690 --> 00:41:26.733
Um, we had early morning 2 AM sessions and then repeated them again at noon, just cause we're, you know, international and the major thing too.

00:41:26.733 --> 00:41:29.016
Sorry, ron, I'm just going to say this.

00:41:29.476 --> 00:41:34.521
The major thing too is we make them test with whatever permissions they have in production today.

00:41:34.521 --> 00:41:43.289
So a lot of people just give up and want to test functionality and set all their users up as supers, and then they go live and then they have no permissions to do anything.

00:41:43.289 --> 00:41:47.431
So we do test permissions along with that whole process as well.

00:41:47.452 --> 00:41:55.500
That is beautiful because I know of so many implementations that the first day they start, everyone gets frustrated because they can't do anything.

00:41:55.500 --> 00:42:04.710
And it's because, as you had mentioned, they didn't want to inhibit testing, because they didn't want users to get frustrated with permissions.

00:42:04.710 --> 00:42:12.195
But then they just sort of pushed that down the road, because now, when they're going live and they're supposed to work, it seems like nothing's working because they can't do anything.

00:42:12.516 --> 00:42:13.847
It's because the permissions.

00:42:13.847 --> 00:42:22.206
So it's great that you tested with that and you flushed that as well too, and now, since you're up into the latest version, you can incorporate the new love of my life page scripting.

00:42:22.206 --> 00:42:24.190
That can maybe help you with some of these testings.

00:42:24.351 --> 00:42:25.094
I hope so.

00:42:25.094 --> 00:42:27.219
Yeah, it's on my list.

00:42:27.219 --> 00:42:34.195
Yeah, so we actually have one location that we acquired Was it last November, I think they're.

00:42:34.195 --> 00:42:40.074
They're a business central online and he uses the page scripting our support guy over there and he loves it.

00:42:40.074 --> 00:42:49.820
We have to be able to record the results somewhere when someone runs the test, because we get audited and we have to show test results.

00:42:49.820 --> 00:42:54.518
Yeah, so that's the only thing we haven't really figured out yet, but it is on our list.

00:42:54.518 --> 00:42:55.382
I know, pablo, haven't?

00:42:55.382 --> 00:42:56.646
You dove into it a little bit.

00:42:56.666 --> 00:42:58.407
Yes, a little bit, a little bit yes.

00:42:58.407 --> 00:43:07.215
As soon as we had that update on there and that release note, I went and tried it out and, yeah, it was great it's wonderful Replay will track the test results for you.

00:43:07.476 --> 00:43:09.376
Oh, that's good yeah.00:43:09.637 --> 00:43:10.657


My guy at Veriperm.00:43:10.657 --> 00:43:21.047


Well, at the other ledger of Veriperm, yeah, he says he just takes screenshots and I'm like I'm not saving screenshots yeah, pablo, take a look at Replay.00:43:21.067 --> 00:43:23.592


You can automate some of those tests and it will track the results for you.00:43:23.853 --> 00:43:24.615


Okay, Thank you.00:43:26.869 --> 00:43:27.833


It will give you a lot with it.00:43:27.833 --> 00:43:34.474


It does give you videos, it gives you the results, it gives you everything, so you'll be able to see, if you'd like to see the actual test, that are going with it too.00:43:34.474 --> 00:43:38.516


So it sounded like the testing was something that you thought you did really well.00:43:38.516 --> 00:43:40.387


What about?00:43:40.387 --> 00:43:40.949


And we?00:43:41.150 --> 00:43:49.853


always say one more thing to you, and every time we upgrade not only creating new orders we make them test the orders existing before upgrade.00:43:49.853 --> 00:43:56.014


You know partial up orders because if something got upgraded we don't know, so if you create a new it might work.00:43:56.014 --> 00:44:05.206


So that's something we make sure they test new orders and old orders, and partial you know invoice or shipments or whatever for the old and new orders.00:44:05.708 --> 00:44:10.965


So yes, that's an invoicing and, honestly, that is a result of our tax engine.00:44:10.965 --> 00:44:19.373


When we did the last update, we had to actually write a script to revalidate all our orders for tax because they weren't validated.00:44:19.373 --> 00:44:20.958


Yeah, we learned that one.00:44:20.958 --> 00:44:22.885


On group one of the BC-14 jump they weren't validated.00:44:22.925 --> 00:44:25.612


Yeah, we learned that one on group one of the BC 14 jump.00:44:25.612 --> 00:44:26.574


No, you need those taxes.00:44:27.557 --> 00:44:28.519


Need taxes yeah.00:44:31.489 --> 00:44:36.659


So so do you have anything that you think went really well from your perspective, other than testing?00:44:39.248 --> 00:44:47.494


I would say yeah, I mean I would say for for, from a permission standpoint, testing with the user's permissions internally.00:44:47.494 --> 00:44:59.391


That's always helpful as well to make sure that you can, you know, get those error message before you hand it over to the user, so you can test with Super just to make sure that everything works, everything functions correctly.00:44:59.391 --> 00:45:06.378


But then also turn around and give your take a user, a power user, copy their permissions, give it to your user.00:45:06.378 --> 00:45:10.786


That way you can test with their permissions and you can catch everything beforehand.00:45:10.786 --> 00:45:12.811


That's also really helpful.00:45:12.811 --> 00:45:22.972


And let's see, I like Jesse said, I mean our power users are great, so that's definitely a plus in our SMEs, on our team.00:45:23.976 --> 00:45:25.018


It's excellent, excellent.00:45:25.018 --> 00:45:29.396


It all comes down to the users to make the implementation easier.00:45:29.396 --> 00:45:38.378


Also, the users sometimes don't realize they're making it easier for themselves, and by getting them in there, it sounds like they were able to have some ownership of it as well.00:45:38.378 --> 00:45:57.233


So I think it's a little bit easier if they feel that they have a good part or part of the implementation process, versus it being forced down their throat, to say it bluntly which is nice, ramas, anything that you look back, that you thought went really well, that you planned for.00:45:57.253 --> 00:45:58.353


I mean, overall, everything's fine.00:45:58.353 --> 00:46:05.481


For me being on the technical team, the way we started doing the code conversion, you know, and then now it's ongoing.00:46:05.481 --> 00:46:12.692


Actually we still find some issues and we'll just make sure that we follow the standards, like basically Microsoft standards, you know.00:46:12.692 --> 00:46:23.610


I know we cannot customize any of the standard objects now, so we just try to keep it as separate as it is, so more easy for the next upgrade.00:46:23.610 --> 00:46:33.952


So the timeline the reason why I'm saying is every time we've been upgrading from 13 to PC, 14 to 23 to 25, the timeline went down every time we're doing it.00:46:35.009 --> 00:46:44.630


So that really made a good thing, we are separating everything from Microsoft Objects, so, which means, when we are upgrading it, we just take it out, upgrade Microsoft and then plug.00:46:44.630 --> 00:46:47.492


It means, when we are upgrading it, we just take it out, upgrade Microsoft and then plug it in and that's it.00:46:47.492 --> 00:46:49.235


So we are doing really great on that.00:46:49.235 --> 00:46:50.635


Excellent, excellent.00:46:50.655 --> 00:46:56.021


I do like your cadence to do one to two versions behind right.00:46:57.244 --> 00:47:08.434


Yeah yeah, because a lot of times where people move to on-prem business center, they kind of just leave it alone as if they'll never upgrade again and it is an internal conversation or internal decision.00:47:08.434 --> 00:47:11.789


Okay, how far back do you want to be behind?00:47:11.789 --> 00:47:29.666


Because then you go back to that same old ways of nav where you stay in nav 2013 right for years to come, versus with business central, with the way you guys have set up, you're setting it up every two versions behind at most and so you're always upgrading.00:47:29.666 --> 00:47:33.514


So that's fantastic it is.00:47:33.735 --> 00:47:35.641


It is you get the latest updates as well.00:47:35.641 --> 00:47:40.896


So if there are things that aren't working properly or need to work slightly different, you get those.00:47:40.936 --> 00:47:46.940


So you can alleviate some frustration and again, as we were talking about it, goes much quicker in retrospect, looking back.00:47:46.940 --> 00:47:50.199


What is something or some things?00:47:50.199 --> 00:48:02.505


If you have that you look back that you wish you had done differently, or you wish you had planned differently, sort of something that you had learned that maybe didn't go the way that you wish you had done differently, or you wish you had planned differently, sort of something that you had learned that maybe didn't go the way that you wanted and you wish you had either known about or planned differently.00:48:03.409 --> 00:48:06.059


Oh, rama, you should tell them about the server patches.00:48:06.059 --> 00:48:12.996


Remember the server patches ran during the upgrade?00:48:12.996 --> 00:48:14.298


Yeah, right, and rolled it back.00:48:14.298 --> 00:48:15.581


Yeah, that's of course an internal schedule.00:48:15.581 --> 00:48:17.925


Now, during the upgrade, yeah, yeah, and rolled it back.00:48:17.965 --> 00:48:19.148


Yeah, yeah, yeah.00:48:19.148 --> 00:48:21.061


That's, of course, an internal schedule now.00:48:21.061 --> 00:48:31.894


I mean, it happened for one first time and then from then onwards we just make sure we keep track of any patching not done during the you know go live, because we lost a day.00:48:31.894 --> 00:48:48.494


Luckily that it was for BC23, I think we gave a buffer, a lot of buffers, so that's why we didn't really, even though we lost a day of work because of the patching for the servers, but still we made it.00:48:48.494 --> 00:48:52.956


But that's something, yeah, we made it in the deadline.00:48:53.471 --> 00:48:55.818


The deadline was made because we planned ahead.00:48:55.838 --> 00:48:56.539


We planned for it.00:48:56.539 --> 00:48:57.753


Yeah, we gave ourselves a day.00:48:57.773 --> 00:48:59.097


We gave ourselves a day, a day extra.00:48:59.097 --> 00:49:13.659


Of course, pablo said when we started this upgrade he went through the Microsoft release notes, but I think we 100% don't want to go with whatever they're saying because they missed some of them.00:49:13.659 --> 00:49:24.081


When we are doing the code conversion, then we have to do QA and see what else is involved in it, because there's some things Microsoft might think it's not a big deal.00:49:24.081 --> 00:49:29.750


I think there's a field which they made it a mandatory during the code but it's not even there in the release notes.00:49:29.750 --> 00:49:37.092


But it is a process for our side it affected, but it didn't make a huge difference.00:49:37.092 --> 00:49:39.456


Process for our site it affected, but it didn't make a huge difference.00:49:39.476 --> 00:49:43.300


We had to work after the release upgrade but we overlooked it because we thought, okay, well, they didn't do anything.00:49:43.300 --> 00:49:48.565


So for the next version not only the release nodes we have decided to go through the.00:49:48.565 --> 00:50:01.239


We'll just do a QA, like Microsoft objects, and see what is that they removed or what is that they added and we can analyze is it going to affect us or not.00:50:01.239 --> 00:50:04.215


So that's one of the things for us.00:50:04.215 --> 00:50:06.619


For the technical side, we have to do it next time.00:50:07.902 --> 00:50:08.423


Yeah, it's good.00:50:08.423 --> 00:50:18.742


I've heard stories like that before, so you're not alone where they had server reboots or other maintenance plans scheduled and it threw things off quite a bit.00:50:18.742 --> 00:50:20.353


So you're not alone in that aspect.00:50:20.353 --> 00:50:29.233


Are there any other things that you can think of that you wish you would have planned differently for or handled differently to?00:50:29.233 --> 00:50:32.822


Anybody that may be, going through the process or was it just perfect?00:50:32.822 --> 00:50:33.764


No other thing?00:50:33.764 --> 00:50:37.938


No, we're not perfect, you know, I will say we had.00:50:38.097 --> 00:50:41.284


we had some add-ons that we kind of struggled with.00:50:41.284 --> 00:50:42.853


I know our tax engine.00:50:42.853 --> 00:50:56.699


For the first jump I think we just assumed everything would update but we had to actually reload a lot of stuff with our tax engine, revalidate, run those scripts to revalidate all the open orders Just stuff we weren't expecting, that we didn't catch during testing.00:50:56.699 --> 00:51:09.181


I remember that for the tax piece I know Pablo for was it the TCM we lost some historical data that you had to go and manually load.00:51:09.570 --> 00:51:12.699


Yes for some posted time cards, things like that yeah.00:51:14.170 --> 00:51:31.170


So I mean all fixable things just weren't caught in the front end because nobody thought let me go look at my historical posted time card lines, you know, or you know everybody just assumed once you plugged in your tax engine all you had to do is click statistics again and it would be fine.00:51:31.170 --> 00:51:32.554


But not everybody does that.00:51:32.554 --> 00:51:37.101


So just little things like that does that.00:51:37.101 --> 00:51:39.905


So just little things like that, other than that, we're perfect.00:51:43.889 --> 00:51:45.514


It sounds like you went well I mean you spent some time to plan it.00:51:45.554 --> 00:51:50.090


You had the users testing and fortunately you have the right individuals on your team to help push it through and guide you through it.00:51:50.090 --> 00:52:04.318


Not all implementations have to be problematic, and nor, in this case, are implement are all implementations problematic, but it just goes to show that a little bit of planning and proper procedure can make it easier and you don't have to rush through it.00:52:04.318 --> 00:52:05.103


I know it's not easy.00:52:05.103 --> 00:52:12.150


Sometimes you can get those users in there, but if it's sometimes just training issues versus having systemic or data issues, it makes a little bit easier.00:52:12.150 --> 00:52:18.007


But I'm happy to hear that you had a pleasant journey with the application, which is great.00:52:18.568 --> 00:52:21.177


Yeah, our project planning timeline is.00:52:21.177 --> 00:52:22.340


I think it's perfect.00:52:22.340 --> 00:52:25.159


You know we all agree with the timeline.00:52:25.159 --> 00:52:28.396


Sometimes they crunch it, but normally yeah.00:52:28.396 --> 00:52:38.925


But you know, in general the planning team, like project manager planning is actually good yeah.00:52:39.951 --> 00:52:42.780


They're heavily involved as well, sorry to interrupt.00:52:42.780 --> 00:52:43.161


Yeah.00:52:44.012 --> 00:52:44.775


No no that's good.00:52:45.431 --> 00:52:48.340


I was about to ask about the managing of the project.00:52:48.340 --> 00:52:59.641


Clearly, you know the three of you are in the trenches and testing and making sure you know users are testing, but at the same time you have somebody has to coordinate all of that, right?00:52:59.641 --> 00:53:08.481


So I'm sure you're working with all the different internal departments, but then you also have, potentially, your partners and your ISVs that you work with.00:53:08.481 --> 00:53:11.579


I mean, those all still have to be coordinated.00:53:11.579 --> 00:53:13.335


So and Jessie, you had mentioned you have four project managers.00:53:13.335 --> 00:53:13.775


Did I hear that right?00:53:13.775 --> 00:53:14.157


We have three.00:53:14.157 --> 00:53:15.442


Well, we have four project managers.00:53:15.442 --> 00:53:16.346


Did I hear that right?00:53:16.887 --> 00:53:17.570


We have three.00:53:17.570 --> 00:53:24.400


Well, we have four, but three were on the project, but one of them is the manager of the project managers.00:53:24.400 --> 00:53:26.614


I don't know how to the project manager manager.00:53:26.614 --> 00:53:27.155


Pmo.00:53:27.175 --> 00:53:27.317


PMO.00:53:29.331 --> 00:53:34.298


And he helps out too as much as he can, but the three were actually the ones planning it together.00:53:34.298 --> 00:53:37.739


We did, I think, not for 14.00:53:37.739 --> 00:53:38.775


Did we bring the two other?00:53:38.795 --> 00:53:38.894


ones.00:53:38.894 --> 00:53:40.916


Remember we had two consultants come in.00:53:41.217 --> 00:53:41.960


That was 23.00:53:42.119 --> 00:53:46.380


Yeah, they came in and helped during the 23 one because it was a bigger jump.00:53:46.380 --> 00:53:49.858


It was like all the ledgers were jumping at one time it was more.00:53:49.858 --> 00:53:59.277


But for the BC 14 jump we had the three and we really laid out the foundation for that and just fast tracked it for the rest of it.00:54:00.311 --> 00:54:02.657


Were there internal PMs or were there.00:54:02.657 --> 00:54:05.503


Okay, so with you, I mean works.00:54:06.349 --> 00:54:12.557


Yeah, three internal PMs for the BC 14 jump and then we had three internal and two external for the 23 jump.00:54:12.557 --> 00:54:17.018


Yeah, just because we were taking more ledgers at once.00:54:17.018 --> 00:54:38.012


The only regret I have with the fast tracking of the timeline when we went to, like, from 14 to 23, like in there or some of the BC 14 updates afterwards, is we tried to merge testing and training into one session and I think it caused a lot more confusion at some areas into one session and I think it caused a lot more confusion at some areas.00:54:38.012 --> 00:54:38.994


I don't think I'll do that again.00:54:38.994 --> 00:54:42.719


I think we'll just keep it separate moving forward.00:54:42.719 --> 00:54:44.079


Do you remember that, pablo?00:54:44.201 --> 00:54:47.485


Yes, definitely yeah, we had to change it up in the middle.00:54:54.251 --> 00:54:57.878


We tried something new and it, you know it, I think everybody was confused on who had to sign off on the test scripts was the main thing.00:54:57.878 --> 00:55:02.518


But yeah, we were like no, just this person, it's fine you know, but yeah it gets a little confusing in there.00:55:03.911 --> 00:55:05.376


Yeah, it definitely is.00:55:05.376 --> 00:55:07.255


I mean, especially what worked before.00:55:07.255 --> 00:55:08.298


Yeah, you tried something new.00:55:08.298 --> 00:55:08.739


It didn't work.00:55:08.739 --> 00:55:11.119


You know you iterate fast.00:55:11.119 --> 00:55:21.501


Now, going back to the ISV comment I made earlier, was there any ISVs or add-ons that you had where it didn't exist in Business Central?00:55:21.501 --> 00:55:27.820


Did you come across any of those and if so, what was your process like in replacing them?00:55:27.820 --> 00:55:30.876


Or did you even replace it and just change the business process?00:55:30.876 --> 00:55:33.297


Was there any of that happening?00:55:35.690 --> 00:55:37.117


No, I think everything updated.00:55:37.117 --> 00:55:40.536


The attachment is the one they didn't upgrade.00:55:40.577 --> 00:56:04.420


We used the standard Microsoft functionality, which process-wise is not different, but it's just different Microsoft we are using, and I think, easy security they didn't upgrade but the standard Microsoft security is good, so we had these two not working in the Business Central, but Microsoft options are already there, so we didn't have to really replace it.00:56:04.460 --> 00:56:06.289


Did the rental fall into that Rental module?00:56:06.289 --> 00:56:06.570


We?00:56:06.590 --> 00:56:09.559


removed the rental module because it wasn't being used.00:56:09.559 --> 00:56:19.197


During the update we stripped that out and one of the shipping add-ons that we had sold those ledgers and they were the only ledgers that used it.00:56:19.197 --> 00:56:22.621


So we stripped the shipping that shipping add-on that we had out as well.00:56:23.496 --> 00:56:23.900


Got it.00:56:23.900 --> 00:56:31.949


So there wasn't major ISVs or add-ons where like hey, they're not going to Business Central, so there was a major change.00:56:31.949 --> 00:56:39.119


I mean you mentioned Easy Security, but then you have a replacement for that you know out-of-the-box functionality.00:56:39.139 --> 00:56:40.592


Yeah, Okay, Everything else.00:56:40.592 --> 00:56:42.512


Updated Everything else.00:56:42.512 --> 00:56:43.898


Yeah, had an extension we could use.00:56:45.411 --> 00:56:47.456


So you had the perfect storm.00:56:47.498 --> 00:56:54.259


I guess they would say, right, like, just everything, just… I mean we still had to customize some of those extensions to make them work for us.00:56:54.259 --> 00:57:00.873


With our processes we have a very, very customized inventory count process.00:57:00.873 --> 00:57:05.923


So that one actually when we jumped to 23, wasn't ready yet.00:57:05.923 --> 00:57:07.293


It took a little bit longer.00:57:07.293 --> 00:57:14.882


Um, so people were having to like, do me, we have, like we have a process in place where we schedule random counts.00:57:14.882 --> 00:57:20.201


So we have like it's a job runs and it just creates a count for us and then they go print it and they do counts.00:57:20.201 --> 00:57:22.076


That wasn't working.00:57:22.076 --> 00:57:26.402


So they were having to manually run their accounts every week to do the randoms, things like that.00:57:26.402 --> 00:57:27.916


Just little things that weren't ready yet.00:57:27.916 --> 00:57:37.983


But, like I said, that inventory account module that we use, we customized it a lot to just work with our policy that we have for accounting inventory.00:57:37.983 --> 00:57:42.260


So, yeah, sure, other than that, I mean everything else I think was pretty straightforward.00:57:42.260 --> 00:57:44.233


Quality took a little bit longer.00:57:44.233 --> 00:57:45.137


Pablo.00:57:45.157 --> 00:57:58.143


Yes, yeah, quality was new because it moved from what it was to separate, so it was kind of a package before quality and time collection, but then they separated that, so that was a new thing.00:57:59.710 --> 00:58:00.175


Got it.00:58:00.175 --> 00:58:04.978


So, with with all of this successes, you have certainly a lot of planning that you've done.00:58:04.978 --> 00:58:07.494


You know everything went up pretty smoothly.00:58:07.494 --> 00:58:09.981


You know, are you?00:58:09.981 --> 00:58:17.815


Are any of you doing any speaking sessions then to talk about how you should do a business, central implementation or upgrade?00:58:18.356 --> 00:58:19.519


No, this is great.00:58:19.519 --> 00:58:20.442


Haven't you met me by now?00:58:20.442 --> 00:58:22.146


You know how much I hate speaking Like oh Lord.00:58:22.166 --> 00:58:22.947


That's a good point.00:58:29.920 --> 00:58:34.929


I did volunteer Pablo to join the New to BC panel for Summit.00:58:34.929 --> 00:58:39.876


So me and Pablo will be on that panel at summit new to bcs with00:58:40.056 --> 00:58:41.380


david volunteer.00:58:41.400 --> 00:58:52.204


Still pablo, that was that was voluntold so I had one of my employees do it with me last year, but she's not going this year.00:58:52.204 --> 00:58:52.731


Um.00:58:52.811 --> 00:59:13.284


So I was like, well, pablo, you can do it, you'll be good I'm looking forward to that, seeing that session you'll probably have a session at the same time, so you know, probably not the new to bc they usually do first right, the first step the first timers meeting is that's me, steve chinsky and kim dollfield and that's on day one.00:59:13.344 --> 00:59:14.791


That one's like a fast chat one.00:59:14.791 --> 00:59:17.657


This one's that panel one, the ask the experts panels.00:59:17.657 --> 00:59:21.266


We do for every track we usually do for every track.00:59:21.266 --> 00:59:25.396


I added ours because I wanted ours in there, because ours was very successful last year.00:59:25.396 --> 00:59:26.619


We had a lot of questions.00:59:26.780 --> 00:59:37.478


A lot of um people who were moving over from gp were in there asking us a bunch of questions I think you'll have a lot of questions this year based on what I see and what I know that there are.00:59:37.478 --> 00:59:39.121


Thankfully the product is sort of exploding.00:59:39.702 --> 00:59:45.041


Yeah, that's why David Laster's in there, because he's very, very knowledgeable on that migration.00:59:47.331 --> 00:59:49.695


That's good to have someone in there.00:59:49.735 --> 00:59:50.938


We'll take this recording.00:59:50.938 --> 00:59:53.351


You set your structure of your agenda.00:59:53.351 --> 01:00:00.456


Then you submit your session to how to implement Business Central in a 55 company.01:00:00.456 --> 01:00:01.539


That's actually impressive.01:00:01.949 --> 01:00:04.396


Brad summed it up earlier, so we have the notes already.01:00:04.396 --> 01:00:05.740


Yeah, there you go.01:00:05.740 --> 01:00:11.835


We'll get to the transcript and you can go through the process and tell your tales and go from there.01:00:12.289 --> 01:00:17.054


Well, jesse Pablo Rama, thank you very much for taking the time to speak with us today and share your story.01:00:17.054 --> 01:00:32.972


It's nice to hear you know a nice implementation story of Business Central and what it takes to go through implementation, and it's nice to hear that they're not all bad and some of them are very easy and a lot of them are very easy as well I regards me here.01:00:32.972 --> 01:00:36.882


So we look forward to seeing you in Orlando in October.01:00:36.882 --> 01:00:44.097


Hopefully I can go to your new to BC session as well, and we look forward to talking with you soon, thank you.01:00:44.137 --> 01:00:46.041


Thank you, thank you, perfect Thanks for having us.01:00:46.663 --> 01:00:47.143


Thank you, bye.01:00:49.751 --> 01:00:56.777


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


Thank you, brad, guests, for participating.01:00:58.965 --> 01:01:03.831


Thank you, brad, for your time.01:01:03.831 --> 01:01:04.914


It is a wonderful episode of Dynamics Corner Chair.01:01:04.914 --> 01:01:06.197


I would also like to thank our guests for joining us.01:01:06.197 --> 01:01:08.663


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


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:01:23.182 --> 01:01:36.561


You can also find me at Mattalinoio, m-a-t-a-l-i-n-o dot I-O, and my Twitter handle is Mattalino16.01:01:36.561 --> 01:01:40.257


And you can see those links down below in the show notes.01:01:40.257 --> 01:01:41.601


Again, thank you everyone.01:01:41.601 --> 01:01:43.175


Thank you and take care.