Monday, July 27, 2020
Extending an Extension in AL for Microsoft Dynamics 365 Business Central
Monday, July 20, 2020
Creating a new report and modifying an existing report in Microsoft Dynamics 365 Business Central
Reports, one of the most important aspects of an ERP and of course are widely used through the application. The layout of reports works the same in Business Central as that of NAV. You can use RDLC or Work Layout, the difference is, of course, the AL file like any other object. Apart from this, a major change or drawback is that reports cannot be extended. Yes, you heard it right! Microsoft hasn’t come with report extensions yet but we surely have some workarounds that will help us overcome this drawback.
In this blog, we’ll look
into the following:
1. Create a new report
2. Modifying this custom report
3. Modifying layout of an existing report
wherein modification is required only in the layout.
4. Modifying an existing report wherein modification is required in AL like adding a new field to its dataset (Workaround since reports are not extendable)
Sunday, July 12, 2020
Microsoft Dynamics 365 Business Central release wave 2 Plan June 2020
Microsoft is full fledged working on updating Business Central and yet again we have another release plan updated as per 26th June 2020. Few features are available for preview since May 2020, others are for August & September 2020 whereas few ones do not have a day yet. General availability is in October 2020 as per the plan. Similar to every release, this also has Administration, Applications, Power Platform, etc features. Although, I am still locking forward to report Extensions, to be honest. Regardless, the features mentioned are big enhancements, I must say.
Monday, July 6, 2020
[Resolution] Unable to Download Symbols in Visual Studio Code for AL Extension
While getting started with AL and creating your first
Workspace you might have come across with this error at least once, as you can
see in the image below.
There are 3 points mentioned which can help you resolve this
error:
1. The correct server name and instance are specified in the launch.json file.