Let's work. Programming is only a matter of code. It is the art of translate what users want into a language that will become a system, a functionality. This blog has the goal to provide some tips and tricks about how programming better in X++, for all audiences -- since AX functional consultants that want to understand how the engine on the background makes the "magic" up to senior architects that had forgotten some small code.
Programming in X++, the language for AX is not easy. Sometimes the code is well-written, compiles fine, but the system does not work as the expect. Many daily problems can be solved changing some system/modules parameters. So, every time, before start a new customization, ask your user, functional consultant or manager if the system does not have a second path to solve the business inquiry. Check if the solution was not given at Microsoft Sure Step or Lifecycle Services (let's talk about them on the future).
If the only way is a change, let's do it. Once. Let's avoid "go-horse process" or "jeitinho brasileiro" (Brazilian readers will know well what I'm talking about).
Programming in X++, the language for AX is not easy. Sometimes the code is well-written, compiles fine, but the system does not work as the expect. Many daily problems can be solved changing some system/modules parameters. So, every time, before start a new customization, ask your user, functional consultant or manager if the system does not have a second path to solve the business inquiry. Check if the solution was not given at Microsoft Sure Step or Lifecycle Services (let's talk about them on the future).
If the only way is a change, let's do it. Once. Let's avoid "go-horse process" or "jeitinho brasileiro" (Brazilian readers will know well what I'm talking about).
