From the Microsoft Dynamics AX Blogs: Batch Job; D365Ops source code; Capacity planning; AIF issues

From this week's Microsoft Dynamics AX blogs:

• Modify a Batch Job's Created by User after It Is Saved
• D365Ops Tip#2: Where Is Source Code located in Dynamics 365 for Operations?
• Capacity Planning for Dynamics AX
• Microsoft Dynamics AX: Simple AIF Issues with SoapUI

Modify a Batch Job's Created by User after It Is Saved

On Brian Norman's Microsoft Dynamics Tech Tip blog, Norman stated that when a Dynamics AX batch job runs, the account of the user who created the batch job gets stamped on all the data it updates. The user account is also used for permissions.

Many times, though, jobs are created with a user's logon when the logon should have been a system account that will exist for the life of the system, he stated.

Norman wrote that in his company these jobs are often created by IT staff members. The problem is that for auditing purposes it doesn't look right when the user accounts of the IT staff members are stamped all over the data the jobs modify, he wrote.

In place of removing these jobs and setting them up under the proper account it is very simple to modify the user account behind the scenes provided you have access to SQL.

You can find out how to do it here.

D365Ops Tip#2: Where is Source Code located in Dynamics 365 for Operations?

On his Dynamics AX: Learn in Doing blog, Ajit Kumar wrote that one of the major changes ...