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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Simultaneous operation...
Microsoft Dynamics AX (Archived)
Answered

Simultaneous operations impossible in AX?

(0) ShareShare
ReportReport
Posted on by Alexey Lekanov 522

Hello, guys. Is it possible to define following structure of operations in AX 2009: Nr. 10 (named A) - next 20; 20 (B), - next 50; 20 (C) - next 30; 30 (D) - next 50? The problem is that oper. B takes more time than C and D together, and C must be run after D, but B and C can run in parallel. Obviously, this should be set up as described, but AX does not allow 2 operations with same number and priority, hence C must be secondary, and AX then disregards its run time values, it uses the primary operation's run time for both (i.e. run time of B, which is long). In addition, 30 cannot be defined as "next" for C since C is secondary (again "interesting" AX rule). Ergo: The route presented above is impossible to define. Is it MS or me who does not see obvious things? I hope its me and some of you has a piece of advice. Thanks in advance!

*This post is locked for comments

I have the same question (0)
  • axpediter Profile Picture
    axpediter on at

    I do not understand the naming and numbering. Why is operation 20 named (B) first, than same operation is named (C)?

    From what I understand:

    10

    v

    20

    v    v

    v   30

    v    v

    50

    is this a correct representation of what you are trying to accomplish?

  • Alexey Lekanov Profile Picture
    Alexey Lekanov 522 on at

    Thanks for looking into this, AXpeDiter.

    Operations number is simply its number in the process flow, meaning that e.g. 20 comes after 10. Operations name is unique here. With your notation I am trying to achieve this:

    (A has 20 in its "Next" field meaning that operations B and C cannot start before A is ended.)

    Nr.      Name

    10      A

              v      v

    20      B      C

              v       v

    30      v       D

              v       v

    50      E

    (Operations B and D lead directly to E, i.e. they have 50 in the "Next" field.)

     

    Sorry that my description had some "bugs" like missing nr. 40 (still this is no problem for AX) and not specifying the last operation's name - E. These are nearly irrelevant, but a still bit confusing details. Hope it is more clear now.

  • Verified answer
    Alexey Lekanov Profile Picture
    Alexey Lekanov 522 on at

    So I guess it is time to draw a conclusion here: MS did not make support for proper simultaneous operations in AX, which should be pretty basic functionality, at least in my eyes.

    Any objections/tips are still welcome.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Sagar Suman Profile Picture

Sagar Suman 2 Super User 2026 Season 1

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans