Upgrade from Nav 2018 to BC: How to handle customer data?

StLiStLi Posts: 81Member
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

Best Answer

Answers

  • BlackTigerBlackTiger Posts: 1,210Member
    "Upgrade" here is more MS marketing term. Actually this is a normal re-implementation.
    "You can’t just ask customers what they want and then try to give that to them.
    By the time you get it built, they’ll want something new.” Steve Jobs
  • TallyHoTallyHo Posts: 156Member
    edited 2018-12-04
    Tables in C/AL in the 5xxxx object range, can they be migrated in one step to AL? Or do we transfer the data to buffertables first and delete the C/Al object?
Sign In or Register to comment.