News

Hey y’all. I just wanted to send my Holiday wishes to the community I value so much. It’s been another crazy year in terms of the world being upside down by this freaking virus. However, it has also shown us how strong this amazing community is – finding new ways to connect, share insights, or …

A few months ago, I blogged about a new initiative from Microsoft: Microsoft Dynamics 365 Business Central Publisher program. At Directions EMEA, we got more insights to the program. There is still the same focus and intention – but with a different approach and name. I’d like to go more into details on that, as …

Azure AI in Business Central – The Forecasting Model AI (Artificial Intelligence) can be used with Business Central; there are

Those who have already acquired and started to read might have discovered that there is a GitHub repo accompanying the book. They also might have seen that a number of out-scoped issues have been already listed. Issues I was going to handle after the book would published. So, here I am with my first addendum to the book tackling the incorporation of the new report extension object introduced in 2020 wave 2, aka BC18. When I was working on this part of the book – i.e. Chapter 8, test example 8 – there was a bug in the AL Language extension which made me decide to not yet include the report extension in the book. Instead I out-scoped it and parked it next to a handful of other issues. Now the book is published I will pick them up in the coming weeks and share them with you in a series of addendum posts.

This addendum is about a new scenario that addresses an additional customer wish, or ATDD scenario:

[FEATURE] LookupValue Report
[SCENARIO #0032] Test that lookup value shows on standard Customer – List report
[GIVEN] 2 customers with different lookup value
[WHEN] Run standard report Customer – List
[THEN] Report dataset contains both customers with lookup value

This introduces the following report extension object:

reportextension 50000 "CustomerListExt" extends "Customer - List"
{
    RDLCLayout = './reportlayouts/CustomerListDefault.rdl';

    dataset
    {
        add(Customer)
        {
            column(Customer_Lookup_Value_Code; "Lookup Value Code")
            {
                IncludeCaption = true;
            }
        }
    }
}

And of course the implementation of the test scenario in a new test method. You can find the added code in the GitHub repo.

BcContainerHelper 3.0.0 just released and as something new, you will see this message when importing the module: BcContainerHelper emits usage statistics telemetry to Microsoft What does that m...()

Time to get back to Best Practices for Per Tenant Extensions. This time we are going to discuss something that in my opinion should also be implemented by ISV’s in their AppSource solutions. By default, AL Objects are extensible. This means that everyone can take a dependency on your extension and therefor Microsoft does not

I recently blogged about this new initiative .. the revival of the “NAV Design Patterns Wiki”: ALGuidelines.Dev . Time to talk a bit more on how you can contribute. I’m documenting this while I’m writing my very first pattern 😉 (I admit, I had this blogpost laying around for a while ;-)). Disclaimer We do …

The alternative title for this blog post would have been something like… TempBlob, why did you waste my time! Or waste thousands of hours accross our community. The topics of my blogs tend to be about what happens in the freelance projects I work on, and last week this was two extensions that have a

I’ve been in doubt if I should write this post or not. Read it fast as it may disapear if I regret writing it. Ever since I started working with Navision, almost 25 years ago, I’ve had my own little stuborn ideas. These ideas got me where I am today, but just as often they