Here at MADIC dynamics we will be presenting a Knowledge Hub Webinar at 1400 UK time on Tuesday.
Explore the capabilities of standard workflows in Business Central and how Power Automate can be used to extend those capabilities.
The webinar is open to everyone who wants to sign up and join:
|
No aug-2024 events found. |
This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2024 Wave 2.
The 4th of the new functionality in the Development section is use the ‘this’ keyword for codeunit self reference.
A new ‘this’ keyword is introduced as known from other languages. The keyword supports passing the current object as arguments to methods, which until now has only been possible with less optimal workarounds. In addition, the use of the this keyword improves readability for bigger methods where it can be difficult to see if a variable is global or local scope..
Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Oct 2024
General Availability: Oct 2024
Microsoft have added support for the this keyword for self-reference on all objects, as known from other programming languages.
The main benefits of using the this keyword are that it
A new CodeCop rule AA0248 is added and enabled by default with severity ‘hidden’. ‘Hidden’ means that it shows up as three dots in the editor, but not as a diagnostics in the Problem view in Visual Studio Code, or in pipelines. There’s also a workspace-wide CodeFixer to update existing code to use the this keyword.
The System Application is converted to use this for referencing methods and globals in the same object.
This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2024 Wave 2.
The 3rd of the new functionality in the Development section is pull extension source from GitHub when opening Visual Studio Code from the web client.
A year ago, you got the power to open a Visual Studio Code project from within the web client. This removed all the hassle of creating projects so you could launch configurations and download symbols yourself. This is a great tool for exploring functionality and troubleshooting, whether it’s in sandboxes or production, and it empowers support, consultants, and developers. However, what if access to extension code is blocked by IP resource exposure protection, but the source is in your GitHub repo? Or maybe you want to proceed with authoring your own code, such as hotfixing one of your apps or pulling the latest source version for changes or development? In 2024 release wave 2, this feature will make that possible.
Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Oct 2024
General Availability: Oct 2024
In this release, Microsoft are building on the recent “Explore in Visual Studio Code” feature by using the source and build metadata in the manifest of an extension to offer pulling source from the related GitHub repository and from a specific build. This allows navigating code for the extensions that you have source access to and allows you to hotfix a given build or sync to get the latest changes for investigation or development.
From the Extension Management list page, you now have a new Open Source in VS Code option in the context menu for an extension.
If you invoke that, Visual Studio Code will open and ask you whether to clone or open the GitHub repo for the extension. It will use the repo metadata that was included in the extension when it was built.
You can read more about the source and build metadata in the app.json file here:
.