1) Upgrade the database to Microsoft Dynamics Navision 2018 (application and Data).
2) Create the new table for each table that is customized or also for customized field in standard table but while creating table for standard table, add the primary key and customized field with same ID and Name in new table.
For E.g. :
I have created 1 table “Person” and 2 Customized Field (Test, Doc No) in “Sales Header”.
Now create 2 New tables in 2018.
- Upg Sales Header -> 2 base field (PK) and customized field -> Same ID and add primary key. Refer below screenshot.
- Upg Person -> save as new table (person)
3) Tables consisting data (refer screenshot)
4) Create Upgrade code unit i.e. code unit that having subtype as upgrade and it should have following entry to copy that data:
5) Delete the new customized field and customized table with sync schema validation .
6) Now to check , run the upgrade sales header table .it will show you all data.
- Do the same for customized table.
7) Create extension in visual studio for the customized field and customized table with same id of field and name.
- And Create a codeunit with subtype -> install
8) Publish this app in Microsoft Dynamics NAV 2018 using ISe.
- Open ISE :
Import-Module ‘C:\Program Files\Microsoft Dynamics NAV\110\Service\NavAdminTool.ps1’
Publish-NAVApp -ServerInstance Dynamicsnav110 -SkipVerification
Path : C:\Users\njain\Documents\AL\ExtensionV2Project\Default publisher_ExtensionV2Project_184.108.40.206.app.Install from Client.
9) Now check the data.
- UPGCu.al -> upgrade codeunit in AL
- UPGCU.txt -> upgrade codeunit in NAV.
Error while downloading symbols or unable to access customized table in Visual studio code
Get-NAVAppInfo -ServerInstance DynamicsNAV130 -SymbolsOnly
You should be getting an output as this
If you are getting the version for 11.0 or any other versions in than please follow the below steps.
Open Powershell with Admin
- Import-Module ‘C:\Program Files\Microsoft Dynamics 365 Business Central\130\Service\NavAdminTool.ps1’
Later Please place the files System.app and Test.app in a folder of your choice.
The files are located in the dvd in the following folder (Use the version of BC)
X:\DVD\ModernDev\program files\Microsoft Dynamics NAV\130\AL Development Environment
Run the below 2 commands in the same Powershell (Change instance and path accordingly)
- Publish-NAVApp -ServerInstance DynamicsNAV130 -PackageType SymbolsOnly -Path C:\Test\System.app -SkipVerification
Publish-NAVApp -ServerInstance DynamicsNAV130 -PackageType SymbolsOnly -Path C:\Test\Test.app -SkipVerification
The finsql.exe command must be executed client side.
Run a command prompt and change directory to the client folder (typically C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\130\RoleTailored Client).
From the client directory run the following command
finsql.exe Command=generatesymbolreference, Database=”Demo Database NAV (11-0)”, ServerName=localhost\ITMBSNAV
where Database is the database where you wish to generate symbols and ServerName is the SQL Server instance where the Database is attached
NOTE: The command itself might give the idea to be completed in few milliseconds but this is not true since finsql.exe continue to run in background even if the prompt returns to the command console window.
Use Task Manager to inspect the resource consumption by finsql.exe process.
When running finsql.exe with the generate symbol reference parameter key within command prompt, it might seem the process ending too fast or that nothing happened.
Just close the command prompt and run Task Manager (taskmgr.exe) and go to tab Details to inspect finsql.exe background process and its resource consumption.
You might notice memory growing up high of several hundreds of MB and process disappear when finished.
After this please try to download the symbols again.
Disclaimer– “All data and information provided on this blog is for informational purposes only. Dynamics Square / MPG Business Information Systems Pvt. Ltd. makes no representations as to accuracy, completeness, currentness, suitability, or validity of any information on this site and will not be liable for any errors, omissions, or delays in this information or any losses, injuries, or damages arising from its display or use.”