Skip to main content

Summary of Developer Preview - February 2019 for MSDYN365BC.

Hi Readers,

Microsoft has released updates for Developer Preview for February 2019. Below is the summary of changes in AL / VSCode.

Why Should We Worry about these updates?
With all these updates, we will understand what all is allowed as Event or is allowed in AL when you upgrade/develop in AL. All these changes are introduced in Product based on Microsoft strategy for the product and also based on customer/partners suggestions about enhancements in the product.

10 Changes Released with Developer Preview February 2019 in #MSDYN365BC.

  • The biggest announcement this month is that Microsoft is publishing a preview of the base application fully on AL language. There is a new Docker image, which contains this version here: bcinsider.azurecr.io/bcsandbox-master:14.0.28630.0-al
  • Rapid Application Development (RAD) - RAD is a C/SIDE term used for changing an application object, compiling it, and seeing the results instantaneously in the client. Microsoft have tried to replicate a similar experience for extension development in AL Language in VS Code. More specifically it is about publishing only the objects that changed since the last full publish took place. This is especially useful when working on large projects with several thousands of objects.
    • Ctrl+Alt+F5 for incremental publish
    • Alt+F5 for incremental publish and invoking debugging
  • New schema update mode - ForceSync - Recreate and Synchronize were options avilable till now as Schema Update Mode.
  • Debug without publishing - A new command has been added - Ctrl+Shift+F5 - which will start the debugger attached to the Visual Studio Code launched client session. Please be aware that if you start debugging without publishing you will be debugging the last published code of your app.  
  • New Browser Support for Debugging - Firefox has also been added to the list of supported browsers that will open a client for a VsCode debugging session.
  • Debugger info for http, json etc - Variable value inspection has been added for:
    • HttpClient, HttpRequestMessage, HttpResponseMessage, HttpHeaders
    • JsonValue, JsonToken, JsonObject, JsonArray
    • XmlElement, XmlDocument, XmlNode, XmlText, XmlComment, XmlCData, XmlAttribute
  • Code actions - Code Actions is a VS Code feature providing the user with possible corrective actions right next to an error or warning. If actions are available, a light bulb appears next to the error or warning. 
  • TableRelation extensibility - The TableRelation property on table fields can now be modifed in a table extension. 
  • Views - Views offer a way to improve user productivity when working with list pages by proposing an alternative view of the page.
    • Defining views in AL 
    • Filtering and sorting
    • Ordering
    • Modifying the page layout
    • Modifying views from extensions/customizations
    • Visualizing Views in the Web client 
  • AllObj and AllObjWithCaption no longer contains obsolete Tables - The 'AllObj' and 'AllObjWithCaption' virtual tables no longer contains obsolete tables.

For Detailed Updates Refer to the Microsoft Article.

Hope you find the information useful. This information is useful when you code in the future.

Regards,

Saurav Dhyani
www.sauravdhyani.com

Comments

  1. Hi, I like Your "Summary of Developer Preview - February 2019 for MSDYN365BC." This is informative and helpful article. Keep Blogging...Microsoft Office Product Key

    ReplyDelete

Post a Comment

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 - 

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    ---------------------------

Future - What Next After NAV 2016. Code Name - Madeira...

Hi All, While Browsing web I came across some article which says about next release of Microsoft Dynamics NAV. Let's see the History of Code Names Given to Previous Version  - NAV 2013 - Code Name 'Sicily' NAV 2015 - Code Name 'CRETE' NAV 2016 - Code Name 'CORFU' And as we all know that all these are the Islands.