1) Download Visual Studio Code and Al Extension in Visual Studio Code.
2) Create a new project. For this
- Ctrl + Shift + P and type >AL: Go and rename the project
3) Press enter now it ask for 2 options Microsoft cloud sandbox and own server. Select OWN Server
4) It Create 2 .json and one .al File , Now Set up the configuration in Launch. Json.
- a) Server: link of local server see from IIS (copy the link): browse it with UserId , Password and copy the URL and paste
- b) Server instance- instance name
c) Port – developer port of service refer below screenshot and Enable the two boxes given below.
- d) Startup Object id – give the object id as the starting point of your customization.
e) Startup object type – give the object type whether it is Page and Table.
To see the option available, click CTRL + Space.
5) Change some setting in Microsoft.dynamics.nav.server.exe file that can be found in the below path:
- C:\Program Files\Microsoft Dynamics 365 Business Central\130\Service
Below changes require to edit this file, you have to give full access to the user. <NetFx40_LegacySecurityPolicy enabled=”False” />
6) Now Download symbols. For this
- CTRL + SHIFT + P Type >AL: Download symbols.
7) Run the project using F5 key or Fn+F5.
Create Extension on Cloud.
- 1) Same as above create project using >AL: Go enter and select Microsoft Cloud Sandbox. Now the other window open asking for id and password for authentication (business central cloud credentials).
2) If any other error comes then login with cloud credentials on Dynamics 365 Business Central Online.
3) Create a sandbox environment on business central online for testing purpose.
4) Clear the cache using Clear credential cache.
5) Run the program.
6) Go to microsoft dynamics 365 business central Online type EXTENSION. Click on MANAGE->UPLOAD EXTENSION.
- 7) Upload the .app file
- 8) Deploy It.
UPGRADE THE DATABASE
- 1) List out all the objects that having customizations.
2) Convert all the objects through tool (txt2al) which convert CAL Code to AL Code.“C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\130\RoleTailored Client\txt2al.exe” –source=”D:\OneDrive\Delta” –target=”D:\OneDrive\target”“C:\Program Files (x86)\Microsoft Dynamics NAV\110\RoleTailored Client\txt2al.exe” –source=”D:\OneDrive\CAL” –target=”D:\OneDrive\AL”Source-> Folder that contain all customization files in CAL code.
Target -> folder that contains after conversion files in AL code.
3) Open visual studio code and create a new project and paste all the customized al files in that folder
4) Reverify the objects with araxis merge.
5) Migrate customization on events.
6) Upload the extension.
Publish the extension in NAVISION 2018
- 1) Open the ISE and write command
Import-Module ‘C:\Program Files\Microsoft Dynamics NAV\110\Service\NavAdminTool.ps1′
Publish-NAVApp -ServerInstance dynamicsnav110 -SkipVerificationPath – where your app files are stored
C:\Users\njain\Documents\AL\DemoCloud\.alpackages -> 2 files are stored that need to be publish before project app file.
And after that give the path of your app file.
3) Open RTC 2018 and find extension management.
4) Install the application
Unpublish the extension in Nav 2018
Unpublish-NAVApp -ServerInstance dynamicsnav110 -Name “Data” -Version 18.104.22.168.
- 1) If any Customized field added in a base table then there will be a new table generate in SQL that having Foreign key relation with base table.
2) There is no byte’s issue while creating a field in extension.
3) When the new table is creating through visual studio then new table generates in SQL also.
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.”