Deprecated function: implode(): Passing glue string after array is deprecated. Swap the parameters in drupal_get_feeds() (line 394 of D:\home\site\wwwroot\webapp\includes\common.inc).
By lane | Monday, December 01, 2014 ( 7 years 10 months )
By lane | Sunday, November 30, 2014 ( 7 years 10 months )
If you’re familiar with AX AOS topology, and you’re a global organization, you already know the pain point that is Time zone in AX 2012. The system is designed to host multi-company, multi-currency, and multi-time zone, however not all functionality in the system is time zone aware. One of those major sets of functionality is the SysOperation framework.
By lane | Tuesday, October 28, 2014 ( 7 years 11 months )
Today I will dive in to Visual Studio integration with AX 2012. We will see how to integrate with Azure Service Bus natively, and marshal Brokered Message objects over to X++ Objects, all without breaking a sweat!
By lane | Thursday, October 16, 2014 ( 7 years 11 months )
As Dynamics AX becomes more prominent in your overall IT landscape, integration scenarios will become more challenging. We all know the joys of scheduled maintenance in terms of AX, as it is best practice to take your production system offline and deploy updates in the form of modelstores.
While a good reboot is often a healthy thing, we like to prevent the “We’re down for maintenance, come back soon!” messages on any of our customer-facing software like a website, mobile, and supply chain applications to name a few.
By lane | Sunday, October 12, 2014 ( 7 years 11 months )
This is the last installment in our AX Build Automation series. In part 1, we discussed how to install a continuous deployment software suite, in part 2 we discussed the classes we had to modify to harness the Startup Commands to prepare a modelstore, and finally today we will demonstrate how to automate it all together.
By lane | Monday, September 08, 2014 ( 8 years 3 weeks )
Continuous Deployment with AX is a two part gig. First you need a building software like Microsoft's Release Management or JetBrain's Team City ( covered in part 1 ). Second, you need to be able to call all of the building activities within AX itself such as synchronizing with Version Control, x++ compile, CIL compile, and so on. This is what we will cover today, and will follow up with how to automate the entire process ( part 3 ).
By lane | Tuesday, September 02, 2014 ( 8 years 1 month )
Whether you work in a shop where you are the “AX guru” or if you are a part of a team of rockstars, consultants, or VARs combined: the rate at which you can test and deploy customizations heavily impacts your promised Turn-Around-Time to the business. The more developers you have contributing work, the more complex it can become. Having an organized and automated building process for AX is essential to any dev shop.
By lane | Thursday, August 14, 2014 ( 8 years 1 month )
Hey everyone, it's been a few since my last update so I wanted to make it count We just recently launched our global upgrade of AX 2012 RTM to R3, and it went off without a hitch thanks to a rockstar crew, management and process owners who took charge and made huge commitments to testing, and an organized overall approach. The first two elements come from working at a great company, and the last comes from careful thought and planning. It's our approach that I'd like to review with you today.
By lane | Thursday, July 24, 2014 ( 8 years 2 months )
During our AX 2012 upgrade from RTM to R3, we found that we could no longer have reports run in Batch that print via email with an attachment. This worked perfect in RTM, but R3 seems to have introduced some new .NET based classes that behave differently. I'll show you a work around we have found, while we await a response from Microsoft.
By lane | Tuesday, July 15, 2014 ( 8 years 2 months )
The SysOperation framework has four basic modes, what Microsoft calls Execution Modes. Their desirability depends on the situation, of which I'll try to explain briefly.
Synchronous - This is similar to running a long process on the client. It will lock the client session if the processing takes longer than a few seconds, and the user won't be able to do anything until it is completed.
Asynchronous - To run a service asynchronously, the service class must have a Service node in the AOT, be a part of the AxClient service group, and the service group must be re-deployed thereafter for the change to take affect. If this isn't done, the service will default to Synchronous which will lock the client session.
ReliableAsynchronous - The default mode if none is selected. When the processing begins, it creates two asynchronous threads - the first on the batch server and another on the client to poll the batch server to get the infolog when it is completed. When the batch job is completed, it is removed but leaves traceability in Batch Job History.
ScheduledBatch - This is akin to checking the batch tab, but the user does not get a choice. Even if they did not select to run it on batch, it will. And, it will leave the job in the Batch table in an 'Ended' state when it is complete.
In our in-place upgrade to AX 2012 R3, we found some issues with Enterprise Portal in our validation phase of the project. Namely, the EP Role Center was not available within the client, despite all of the parameters and web site settings being correctly entered. If we were to visit the EP site via a browser, it loads and we can successfully request new vendors, requisitions, expense reimbursements.