When you overlayered an application element (e.g. a method or a form) in Dynamics AX, a copy was saved in a higher layer. You modified the object there, therefore you ended up with two copies of the same element – the original one in a lower layer (such as SYS) and your modified one in …
Continue reading ‘Detection of code upgrade conflicts in F&O’ »
In the previous post, I explained that duplicating application elements is expensive and we should avoid it whenever possible. Let me mention a few techniques that you could use. Obviously, you can create metadata extensions, use Chain of Command for methods, subscribe to events and so on; I’m assuming that you all know that. What …
What I want to talk about today is a special case of code duplication: when we take an F&O application element created by some other company (Microsoft, ISVs or so) and create a copy in our model. Usually, people do it to deal with code that can’t be accessed or extended, e.g. when we want …
Last time, I mentioned using of GitHub Copilot for X++ development, but I didn’t realize that not everyone is aware of the option of using GitHub Copilot in Visual Studio. A lot of examples on Internet shows it in Visual Studio Code and don’t mention Visual Studio at all, which may be confusing. To use …
I’ve finally started looking more closely on GitHub Copilot. What it can do with languages like C# is impressive; I also checked that it can help with things like Powershell scripts or Excel formulas. But because I’m still primarily an X++ guy, I’m keen to explore how it can help there. So far, I tried …
Continue reading ‘X++ documentation comments by GitHub Copilot’ »