All Around Microsoft Dynamics Business Central
When working with AL (Dynamics 365 Business Central), we often need to dynamically construct complex filter strings. A common example is filtering users based on their User Security ID. For this purpose, AL provides the TextBuilder, a wrapper around the .NET StringBuilder, optimized for efficient string manipulation.
While investigating the Business Central 26 CallStack performance improvements, I stumbled upon an interesting question: Does the TryFunction attribute add significant overhead when there are simpler alternatives?
Back in 2016, I wrote a blog post about how to check if your code was being called from a specific function using a try function and an empty error to access the callstack via GETLASTERRORCALLSTACK. For example, checking if you were inside a SaveReportAsPDF function.
In many Business Central implementations, there’s a recurring need: extract a distinct set of document identifiers from a filtered set of detail records. Whether you’re working with sales lines, purchase lines, ledger entries, or custom transactional data — the goal is the same: identify which documents are involved based on line-level criteria.
Business Central 140 has two ways to work with symbols.
I created a simple Dockerfile and a Powershell script to create an custom docker image based on an offical Microsoft image.
If you use a BC Container to develop a WebService connetction, it is hard to analyse the traffic with only the Debugger.