İsmail Ozcan

By Jakob Steen Hansen, Development Manager, Dynamics AX Developer Tools and Business Intelligence. One thing that can only be underestimated is the value of having a heartbeat for your product. The heartbeat provides a regular rhythm to your engineering process, ensuring that the state of the product is well-known on an ongoing basis. A heartbeat consists of many different parts, the build process being one of the most prominent ones. When working with AX, how are you going to get this heartbeat? It all depends on how advanced your engineering practices are. In this blog post and some to follow, I’ll talk about the purpose of a heartbeat and show how to establishing various levels of automation, including a nightly build and tools/techniques we can use to optimize the engineering system when we have a nightly build. My examples are going to be focused on AX 2012, but many of them apply to AX 2009 with little or no change. Let’s look into the specifics for the two extremes of engin...

static void Job3 ( Args _args ) { LogInProperty Lp = new LogInProperty ( ) ; OdbcConnection myConnection; Statement myStatement; ResultSet myResult; str sqlQuery; ; sqlQuery = 'SELECT TOP 10 * FROM CustTable ORDER BY NewID()' ; LP. setServer ( "Server" ) ; LP. setDatabase ( "db" ) ; Lp. setUsername ( "user" ) ; Lp. setPassword ( "password" ) ; try { myConnection = new OdbcConnection ( LP ) ; } catch { info ( "Check username/password." ) ; return ; } myStatement = myConnection. createStatement ( ) ; myResult = myStatement. executeQuery ( sqlQuery ) ; while ( myResult. next ( ) ) { box :: info ( myResult. getString ( 1 ) ) ; } }