Skip to main content

MSDYN365BC 2019 Wave 2 - Missing Development Environment Task Part 3?

Hi Readers,

In this article, we will discuss things that we used to do in Development Environment till Business Central Spring Release and how we will do them now in Business central 2019 Wave 2 or higher.

This article is based on a question that I received on an email and guess what I never thought about it.

Previous articles we already talked about - Help, Window, View, Edit & Tools Menu Item in Development Environment.

In this article, we will discuss the File Menu Item in the Development Environment.


1. New

Past -  This menu option was used to create new objects with or without wizards in the database.

Future - Using Snippet and other extensions developed by Developers to develop new objects for extension.

2. Design

Past -  This menu option was used to design existing objects in the database.

Future - Using New programming language and code editor we can modify new objects created for the extension.

3. Run

Past -  This menu option was used to Run Objects in the Object Designer.

Future - All objects can be run from AL Object designer using extension build by other developers.

4. Close

Past -  This menu option was used to close the object designer.

Future - As there is no object designer in VS Code we don't need to close objects.

5. Lock

Past -  This menu option was used to Lock selected or all objects from Object Designer.

Future - There are no requirements in AL Programming to Lock Objects.

6. Unlock

Past -  This menu option was used to Unlock selected or all objects from Object Designer.

Future - There are no requirements in AL Programming to Unlock Objects.

7. Force Unlock

Past -  This menu option was used to Force Unlock objects from Object Designer if locked by other developers.

Future - There are no requirements in AL Programming to Force Unlock objects.

8. Import

Past -  This menu option was used to Import selected or all NAV Objects from Object Designer.

Future - There are no base objects that we can import objects in AL Programming or VS Code. Let's put this way before AL Programming Source Control was Object Designer in the database now it GIT. With AL Programming we are truly using Source Control the way it should be used.

9. Export

Past -  This menu option was used to Export selected or all NAV Objects from Object Designer.

Future - There are no base objects that we can export objects in AL Programming or VS Code. Let's put this way before AL Programming Source Control was Object Designer in the database now it GIT. With AL Programming we are truly using Source Control the way it should be used.

10. Database

Past -  This menu is so important for all developers because it provided us the following options -

  • New Database - Create a new database.
  • Open Database - Open an Existing database.
  • Alter Database - We used this option to change the following properties of the database 
    • Change Initial File Size of the database file.
    • Change the File Growth %.
    • Set File Growth Type.
    • Set Max Size of the database file.
    • Change Collation of database.
    • Set Recovery Model.
  • Delete Database - Delete Currently open database.
  • Close Database - Close currently open database.
  • Database Information - You can check the database name and server instance about the database.
Future -
Yes, databases are important and all above-listed objects are very important to us. We cannot do our daily tasks if we don't have alternate to these menu options.

New Database - 
We can create a new database from the Powershell.
Powershell cmdlet New-NAVApplicationDatabase can be used to create a new database for Business Central.

Open Database - Actually to tell you the truth we don't need an option to open a database with AL Programming. The database is mapped to a service that is used in the launch json file for the extension.

Alter Database - 
All actions defined above can be achieved by using the SQL Server Management Studio.

Delete Database - We can delete a database from SQL Server.

Close Database -  As we don't need to open database we also don't need to close the database.

Database Information - We know all information about the database from the Service tier mapped to it.

11. Exit

Past -  This menu option was used to close the Development Environment.

Future - No More Development Environment so this menu option is not required in the future.


Hope you find the information useful.

Let me know your views as a comment on this article.

Stay tuned for more.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

Dynamics 365 Business Central 2021 release wave 2 (BC19) Released.

Hi Readers, As we all were expecting Microsoft have Released Business Central 2021 Release Wave 2 Today a.k.a BC19. In this article we will see what all is announced with the General Availability.  Starting Today Customers & Partners can start using Business Central 19. #msdyn365bc #bc19

Error After Restore SQL Backup of NAV 2013 Database

Hi all, we are facing a conman issue during restoring a SQL Database backup restored for NAV 2013. While Trying to run object from Object Designer we get below listed error (even the service is configured properly) - --------------------------- Microsoft Dynamics NAV Development Environment --------------------------- There are no NAV Server instances available for this database. You must ensure that a NAV Server instance is running and is configured to use the database before you perform this activity. --------------------------- OK    ---------------------------