web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Configure Workflow Batch Jobs in Dynamics 365

(0) ShareShare
ReportReport
Posted on by 40

I am currently working on an upgrade from 2012 R2 to Dynamics 365. When we spun up a DEV environment a few weeks ago, I was able to configure workflow and the associated batch jobs easily. I navigated to System admin > Workflow > Workflow infrastructure configuration to setup the workflow process. When I did this, all fields were editable (see below). I updated all fields, clicked OK and the batch jobs for workflow were created automatically. I also set the workflow batch group to use the correct server and workflow was working fine.

wf1.jpg

We are currently iterating through the data upgrade and this weekend we spun up a new DEV environment to use for upgrading a more recent copy of our 2012 R2 PROD database. However, when I tried to repeat the process of configuring the workflow batch jobs (workflow infrastructure configuration), the fields used for selecting the batch groups were greyed out and could not be edited. The default batch groups were correct on this form but when I finished this setup, the batch jobs were not created. 

 2055.wf2.jpg

Does anyone have an idea why I was able to access these batch group fields in our first environment but not our second?

Any thoughts on how else I can get these batch jobs setup so that we can test workflow?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Sohaib Cheema Profile Picture
    49,438 User Group Leader on at

    Thank you for reaching Dynamics AX community.

    Grayed out (Non-editable) fields on workflow configuration wizard represent that batch jobs are already in place. you may adopt any of following two approaches

    1) delete existing batch jobs, related to workflow and re-run wizard. this time it will let you modify information, as you will go after deletion of existing batch jobs.

    OR

    2) update existing batch jobs in terms of anything (reoccurrence schedule, etc.)

    Good luck!

    PS: I am old school person who likes to call it Dynamics AX or AXPATA, though official name is different and hard to say it as its very log. apologies for any inconvenience.

  • Matt Alford Profile Picture
    40 on at

    Thank you Sohaib. That fixed my issue!

    I found the old batch jobs that were copied from the 2012 environment and deleted the, I was then able to reconfigure the wizard which created the new jobs.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans