Employees appreciate having current data on the test system, rather than data from over 2 years ago. In addition, the release levels (code) between the…
Employees appreciate having current data on the test system, rather than data from over 2 years ago. In addition, the release levels (code) between the development, test and production systems should ideally never diverge. Since AX 2012 at the latest, you should definitely refrain from transferring program modifications via XPO. Otherwise you run the risk that the objects (tables, fields, labels, classes) have different IDs on the various systems. And at the latest during a data refresh from the production system to development or test, things then come to a head. A manual maintenance window easily requires 2 – 3 hours of presence from a technical employee. For this reason, we have developed intelligent PowerShell scripts for AX 2009 and AX 2012 that support both data refreshes (PROD > TEST or DEVE) and transfers of the entire application from DEVE > TEST > PROD. Maintenance windows can be scheduled in AX and then started automatically or manually. The scripts ensure the correct order of starting/stopping AOS, SSRS, Analysis Services, compilation and CIL generation of the application. During the automatic maintenance, the script regularly sends status updates by email, which significantly reduces the employee's presence. If you are interested, we are happy to demonstrate these scripts. Simply get in touch .