From the Microsoft Dynamics AX Blogs: Refreshing dev machines; Missing work time; PowerShell data refresh; Create new languages

A selection of the latest insight from the Microsoft Dynamics AX blogs:

• Refreshing an AX7 Development Machine with Changes from Other Developers
• Timesheets & Missing Working Time
• How to Solve AX Data Refresh with PowerShell?
• Create a New language in Microsoft Dynamics 365 for Operations

Refreshing an AX7 Development Machine with Changes from Other Developers

On the K3 Technical Blog, Kalle Sober pointed out that with Dynamics 365 for Operations (AX7), every developer must work on his or her own machine and share the work with others using Visual Studio Team Services (VSTS).

In the post, he explained how one developer can update his or her development machine with the developments made or hotfixes installed by other developers. This approach can also be used for other development-type environments, Sober stated.

Sober noted that although the instructions are probably obvious to someone with VSTS/TFS experience, they still may be useful for AX developers who have used other techniques for previous versions of AX.

You can read Sober's instructions here.

Timesheets & Missing Working Time

On the Dynamics AX Finance & Controlling blog, Ludwig Reinhard stated that before invoicing project customers and/or preparing the month-end close, you typically verify that all employees have recorded their working time. Dynamics AX supports this verification process through the missing timesheet report, he stated.

Another way to generate the missing timesheet report is to use the periodic missing timesheet email notification functionality, Reinhard stated. This periodic process sends automatic email reminders to those employees who haven't recorded their working ...