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.