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 and Edit Menu Item in Development Environment.
In this article, we will discuss the Tools Menu Item in the Development Environment.
1. Language
Past - This option was obsolete after NAV 2009. This option used to select Application Languages for the client.
Future -
Users can now select Language in Web Client.
2. Object Designer
Past - With this option, we can see all the objects in the database.
Future -
If you remember we talked about in past articles that there are multiple extensions for visual studio which shows all objects as object designers.
3. Debugger
Past -
There are three subitems in Debugger Menu which are -
Future -
With business central and VS Code, we can do the following actions in a different way -
** In a future article I will publish an extension that we can use for these options.
4. Zoom
Past - This option was used to see the object properties.
Future - We can use Extensions which shows object designers in AL Programming and also show properties of all objects.
5. Translate
Past - import and export multilanguage files that contain translated strings for multiple objects.
Future -
Business central is multilanguage enabled, which means that we can display the user interface in different languages. This is done using XLIFF files which is a standardized format.
Just add a parameter in app.json file of your extension - "features": [ "TranslationFile" ]
Refer Here
6. Language Module
Past - With this option, we can Add/Remove Language from the objects.
Future - As with Business Central, we don't have permission to object from Microsoft or Third Party Addon. So we don't this option going forward.
7. Compile
Past - with this menu item, we can compile objects in the database (Selected or all).
Future - with Base Application and RAD we can quickly compile objects during development.
8. Build Object Search Index
Past - with this option we used to add reports and pages to Tell Me Feature in Web Client.
Future - As everything is AL Programming, developers will be adding those properties in custom objects which will automatically add those objects in Search feature.
9. Error List
Past - This menu was used to show all compile errors and warnings.
Future - With VS Code compile is always running as we are developing an extension. A developer can check all compile errors/warnings during development.
10. Build Server Application Objects.
Past - This menu is used to regenerate the C# and metadata information for the objects. This also updates Records in Object Metadata table for each object.
Future -
This is not required with AL Programming as new objects when getting published Object Metadata table gets updated.
11. Show Field Data Classification
Past - This option shows data from the Field table. The information that we were using this menu is specifically Data Classification for the field.
Future -
With AL Programming we should not change any base object field properties. For New objects created with the extension, we should be adding data classification properties.
12. Sync. Schema For All Tables
Past -
There are three subitems in Sync. Schema For All Tables which are -
Future -
Sync. Schema can be done via Powershell cmdlet. We can use Sync-NavApp cmdlet to sync schema.
Read here.
13. Data Upgrade
Past -
There are four subitems in Data Upgrade which are -
Future -
Data Upgrade can be started, stopped, Resumed and Show progress can be done via Powershell using following PowerShell cmdlet.
14. License Information
Past - License Information was used to show the current license in the database. This option also allows us to upload a license in SQL Server or change license in development instance.
Future - With Business central we should upload license in the database and there are PowerShell cmdlets to check and upload license in the database. Refer Here.
15. Custom Control
Past - Custom Control menu is used to register & unregister .ocx in legacy Navision.
Future - ocx control is obsolete with Business central.
16. Options
Past - The Options window was used to set some developer-related settings like Auto-lock on design and service tier details which were used to open Windows clients when we run objects from Development Environment.
Future - With A/L Programming we don't need to lock any base objects (as we should not modify base objects) and the Service tier to the popup web client is defined in launch.json.
In the next part of this series, we will talk about other Menu Items.
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
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 and Edit Menu Item in Development Environment.
In this article, we will discuss the Tools Menu Item in the Development Environment.
1. Language
Past - This option was obsolete after NAV 2009. This option used to select Application Languages for the client.
Future -
Users can now select Language in Web Client.
2. Object Designer
Past - With this option, we can see all the objects in the database.
Future -
If you remember we talked about in past articles that there are multiple extensions for visual studio which shows all objects as object designers.
3. Debugger
Past -
There are three subitems in Debugger Menu which are -
- Debug Session - with this we as developers, select active sessions to the database.
- Event Subscription - with this we as developers, can check active subscribers for published events.
- Database Locks - with this option, we were able to see locking objects during a process.
Future -
With business central and VS Code, we can do the following actions in a different way -
- Debug Session - This is page 9506 that we can expose it by creating an Extension.
- Event Subscription - This is page 9510 that we can expose it by creating an Extension.
- Database Locks - This is page 9511 that we can expose it by creating an extension.
** In a future article I will publish an extension that we can use for these options.
4. Zoom
Past - This option was used to see the object properties.
Future - We can use Extensions which shows object designers in AL Programming and also show properties of all objects.
5. Translate
Past - import and export multilanguage files that contain translated strings for multiple objects.
Future -
Business central is multilanguage enabled, which means that we can display the user interface in different languages. This is done using XLIFF files which is a standardized format.
Just add a parameter in app.json file of your extension - "features": [ "TranslationFile" ]
Refer Here
6. Language Module
Past - With this option, we can Add/Remove Language from the objects.
Future - As with Business Central, we don't have permission to object from Microsoft or Third Party Addon. So we don't this option going forward.
7. Compile
Past - with this menu item, we can compile objects in the database (Selected or all).
Future - with Base Application and RAD we can quickly compile objects during development.
8. Build Object Search Index
Past - with this option we used to add reports and pages to Tell Me Feature in Web Client.Future - As everything is AL Programming, developers will be adding those properties in custom objects which will automatically add those objects in Search feature.
9. Error List
Past - This menu was used to show all compile errors and warnings.
Future - With VS Code compile is always running as we are developing an extension. A developer can check all compile errors/warnings during development.
10. Build Server Application Objects.
Past - This menu is used to regenerate the C# and metadata information for the objects. This also updates Records in Object Metadata table for each object.
Future -
This is not required with AL Programming as new objects when getting published Object Metadata table gets updated.
11. Show Field Data Classification
Past - This option shows data from the Field table. The information that we were using this menu is specifically Data Classification for the field.
Future -
With AL Programming we should not change any base object field properties. For New objects created with the extension, we should be adding data classification properties.
12. Sync. Schema For All Tables
Past -
There are three subitems in Sync. Schema For All Tables which are -
- Check Only
- With Validation
- Force
Future -
Sync. Schema can be done via Powershell cmdlet. We can use Sync-NavApp cmdlet to sync schema.
Read here.13. Data Upgrade
Past -
There are four subitems in Data Upgrade which are -
- Start.
- Resume.
- Show Progress.
- Stop.
Future -
Data Upgrade can be started, stopped, Resumed and Show progress can be done via Powershell using following PowerShell cmdlet.
14. License Information
Past - License Information was used to show the current license in the database. This option also allows us to upload a license in SQL Server or change license in development instance.
Future - With Business central we should upload license in the database and there are PowerShell cmdlets to check and upload license in the database. Refer Here.
15. Custom Control
Past - Custom Control menu is used to register & unregister .ocx in legacy Navision.
Future - ocx control is obsolete with Business central.
16. Options
Past - The Options window was used to set some developer-related settings like Auto-lock on design and service tier details which were used to open Windows clients when we run objects from Development Environment.
Future - With A/L Programming we don't need to lock any base objects (as we should not modify base objects) and the Service tier to the popup web client is defined in launch.json.
In the next part of this series, we will talk about other Menu Items.
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
You can use the "inspect" to do the Zoom equivalent in the new version. From the web client go to Help and Support and in there you should be able to find the option "Inspect pages and data". You don't need an extension (for now).
ReplyDeleteSo true @Manuel.
DeleteCan you help to have multiple Nav services with different database. As we have only web client interface how to configure different Nav services on different web client access.
ReplyDeleteHi Srini,
DeleteThis question was discussed in last #bcopendiscussion.
Please watch recording here and I hope this solves your problem. If not please let me know error that you have.
https://youtu.be/zmjpgr8D7LE