Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 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.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Cannot publish extension in VS Code on BC13's Migrated Database from NAV 2017
raymond_pugnetto
Member Posts: 3
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
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
0
Best Answer
-
Options
EquinoxDK
Member Posts: 6
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#AddExtensions5
Answers
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
I'm asking this because we are trying different ways but we are encountering different troubles on each way.
Thank you
https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data#AddExtensions
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!!!!