Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 317 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Upgrade from Nav 2018 to BC: How to handle customer data?
StLi
Member Posts: 83
Hello there,
A simple question with a not so simple answer: How do you upgrade Customerdata into BC or consequently into Extensions?
I'm looking for anyone who already did it. MS' Guides seam quite useless in that regard as they only care about their standard fields and data. Which does not have to get exported into Extensions.
I Work for an ISV. We are currently developing extensions to replace the C/Side modifications we used to do for our customers. As you can imagine, there are also some Fields involved and we'd really like to allow our customers to switch to BC as fast as possible without losing their data. We're still in development, but We are already wondering how this process will be done best in the future.
Can we just build an Upgradecodeunit in extension form with buffertables and everything? I can see some trouble coming towards us if i try to publish/install an extension while in the middle of the upgrade process. Has anyone a good example? (can be in form of a blogpost)
Thanks for your input
A simple question with a not so simple answer: How do you upgrade Customerdata into BC or consequently into Extensions?
I'm looking for anyone who already did it. MS' Guides seam quite useless in that regard as they only care about their standard fields and data. Which does not have to get exported into Extensions.
I Work for an ISV. We are currently developing extensions to replace the C/Side modifications we used to do for our customers. As you can imagine, there are also some Fields involved and we'd really like to allow our customers to switch to BC as fast as possible without losing their data. We're still in development, but We are already wondering how this process will be done best in the future.
Can we just build an Upgradecodeunit in extension form with buffertables and everything? I can see some trouble coming towards us if i try to publish/install an extension while in the middle of the upgrade process. Has anyone a good example? (can be in form of a blogpost)
Thanks for your input
0
Best Answer
-
SanderDk
Member Posts: 502
We have done upgrade a customer from NAV 2009 to Extension only.
We create the fields we need in extension, and a tool to rename every custom field with a subfix i C/Side. (We cannot have 2 fieds in the same table with the same name).
After that we created a transfer tool to transfer data to extension fields (RecordRef ;-))
After that we can delete the 5xxxx fields in C/side (In C/Side)
i sound so easy but it took a lot of time to figure out how to.For help, do not use PM, use forum instead, perhaps other people have the same question, or better answers.5
Answers
We create the fields we need in extension, and a tool to rename every custom field with a subfix i C/Side. (We cannot have 2 fieds in the same table with the same name).
After that we created a transfer tool to transfer data to extension fields (RecordRef ;-))
After that we can delete the 5xxxx fields in C/side (In C/Side)
i sound so easy but it took a lot of time to figure out how to.