A reference to Dynamics.Ax.ProcessAutomation is required to compile this module

Hello Everyone,

For our customer, we recently upgraded to version 10.0.40.

Version validation for business scenarios, integrations, and reporting went smoothly in the T-2 and PROD environments.

However, when attempting to upgrade the T-1 Development and Build environments, we encountered the following build error.

Issue :

The deployment of version 10.0.40 was successfully completed through LCS. However, when attempting to build the custom model, an error occurred: "A reference to Dynamics.Ax.ProcessAutomation, version = 0.0.0.0, Culture=neutral, PublicKeyToken=null is required to compile this module."

Resolution :

When I checked our custom model for referenced models, I did not find the ProcessAutomation model.

After including the ProcessAutomation model, the build was successful.

Therefore, if you have not already referenced this model, you may encounter these issues.

Conclusion :

Include a reference to the ProcessAutomation model in your custom model to resolve the roadblock.

Mean while i was trying to explore what is Process Automation Framework and found below interesting information.

The process automation framework is a set of APIs that allows implement process automation processes.

Process automation is based on a system-critical batch job called poller that runs every minute and invokes various subsystems of the process automation framework.

Please read the below interesting blog written by Francisco Zanon on Process Automation.

https://www.linkedin.com/pulse/process-automation-framework-francisco-zanon/

Thanks for reading.

Happy Learning :)

Environment administrator for D365 F&O Production instance

Hello Everyone,

While provisioning D365 finance PROD instance in LCS, service accounts are recommended instead of named user accounts because of the following reasons.

• Environment cannot be able to access if the named user account is used as admin and user is not available.
• Some scenarios where only the Admin user can access an environment are:
  • First log-on after initial deployment to any environment – Only the admin user account can access the environment
  • First log-on to an environment after database movement – Only the admin user account is enabled
  • You will have to add the generic account to the LCS project as user in order to set it as environment admin
  • The Admin user is critical in some situations in the apps, such as when system batch jobs are run. These jobs must run with administrator privileges.

But in some cases, administrators realizes later after provisioning the environment with a named user.

Can change environment admin?

Yes, definitely you can change the environment admin user, but it may require a downtime. 

Impact : Causes downtime to the target finance and operations apps environment.

Prerequisites :

• You must be a project owner in the LCS project.
• The new administrator account must be a member of the same tenant that the environment belongs to.
• Plan for the downtime with appropriate approval in your organization.
• If you are going to change domain for the environment, you need to get new ISV license file(s) that references the new domain.

Update environment administrator :

For updating the environment administrator, please go through the steps explained in below.

1. In LCS, go to your project, and open your environment details page.
2. Select Maintain > Update environment admin.
3. In the dialog box that appears, select another Project Owner or Environment Admin user from your LCS project.
4. Select Save.

Please refer Microsoft docs LINK for more information.

Thank you 😊

Happy Learning.