Cannot publish extension in VS Code on BC13's Migrated Database from NAV 2017

raymond_pugnetto

Hi everybody,
I'm Raymond and I've encountered issues after data upgrade from NAV 2017. My migrated DB on Business Central 13 works (I can access NAV Client and Web Client), but I can't publish a new AL extension.
VS Code gives this error: "Could not publish the package to the server. See Visual Studio Code debug console for more details.", and I've noticed that it cannot download symbols. I've tried to restart BC Server Instance, but it does not change.

With a new BC Demo Database, I have no problems on the same Server Instance.

Anyone with a suggestion?
Thank you in advance

EquinoxDK

It might be due to missing symbols in the database. NAV 2017 does not have symbols in the database. See step 17 here (for nav 2018)

https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data#AddExtensions

kriki

[Topic moved from 'NAV Tips & Tricks' forum to 'NAV Three Tier' forum]

raymond_pugnetto

Let's do one step back, is it even possible to accomplish a migration from Nav2017 to BC13, considering we are trying to migrate data and code from C\AL to AL ?
I'm asking this because we are trying different ways but we are encountering different troubles on each way.
Thank you

EquinoxDK

It might be due to missing symbols in the database. NAV 2017 does not have symbols in the database. See step 17 here (for nav 2018)

https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data#AddExtensions

raymond_pugnetto

You are my hero!
The same step is declared in the guide to migrate from NAV 2017 to BC, task 14, but it specifies to do it only in Danish and German localization (I don't know why), so I've skipped them.

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrading-the-data#task-14-publish-and-generate-symbols-for-extensions

Now it works correctly.
Many many thanks EquinoxDK!!!!