Skip to main content

Notifications

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 506

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

  • Verified answer
    Alexey Lekanov Profile Picture
    Alexey Lekanov 506 on at
    RE: Simultaneous operations impossible in AX?

    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.

  • Alexey Lekanov Profile Picture
    Alexey Lekanov 506 on at
    RE: Simultaneous operations

    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.

  • axpediter Profile Picture
    axpediter on at
    RE: Simultaneous operations

    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?

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,865 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,723 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans