Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Workflow 2.0 Issue - I...
Microsoft Dynamics GP (Archived)

Workflow 2.0 Issue - Incorrect AD Account Used for Manager

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

I have come across a strange issue in the new GP2013 R2 Workflow 2.0 system.

I have created a simple requisition workflow that asks for approval from the originators manager.

The domain details I'm using are as follows

Domain name

dev-07.local, Pre windows 2000 name DEV-070

Users

employee@dev-07.local, DEV-070\EMPLOYEE

manager@dev-07.local, DEV-070\MANAGER

As you can see from the screen shot below when the requisition is submitted the engine tries to assign the task to the user DEV-07\MANAGER. This user does not exists and there fore is not able to process the workflow. If I log on as the user DEV-070\MANAGER there are no tasks for me to complete.

I believe the engine is taking the host part of the domain name (dev-07) to build the loin name, where it should be using the prefix of DEV-070

Any help greatly appreciated. By the way there are lots of other systems running on this domain so renaming it is not an option.

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Workflow 2.0 Issue - Incorrect AD Account Used for Manager

    Problem is also in GP 2015. 

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Workflow 2.0 Issue - Incorrect AD Account Used for Manager

    Can I ask the direct question of why does Workflow 2.0 uses the Pre-Windows 2000 Domain name or WindowsDNSDomain name and not the Windows Domain name as expected.  It seems very backwards and as a result Workflow Name assignment does not work properly.  If it is working by design as specified in the other forum post then why does it not appear correctly with the assigned user.  So for example we see Assigned User: " " and its only when we update the WFI10004 table where we see the corrected Assigned user appear.

    This has to be changed for GP 2013 R2 and GP 2015 as although it may be working as designed it is not working correctly as a customer product for the customers it effects and should remain in the lab.  Very frustrating.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Workflow 2.0 Issue - Incorrect AD Account Used for Manager

    Would be interesting to see if the same thing happens in GP 2015

  • Jonathan Fear Profile Picture
    Jonathan Fear on at
    RE: Workflow 2.0 Issue - Incorrect AD Account Used for Manager

    Just to confirm we do have a bug wrote up on this and it is by design. Development did not they would look into this for a future release maybe.

  • Jonathan Fear Profile Picture
    Jonathan Fear on at
    RE: Workflow 2.0 Issue - Incorrect AD Account Used for Manager

    Well that makes much more sense Chris! You aren't going to be able to have the users names be different like that. I ran into a similar thing with Web Client a couple of months ago. I would have to test this out but I believe if you use a account that matches it will work correctly.

  • Midmichael Profile Picture
    Midmichael 59 on at
    RE: Workflow 2.0 Issue - Incorrect AD Account Used for Manager

    Hi Anthony,

    We are seeing the same issue in a test environment in which we were trying to setup the new Workflow in GP 2013 R2.

    We have users setup as follows

    User1@OurDomain.local,  Domain\User1

    After submitting a PO for approval, I have looked in the WFI tables, and the PO is assigned to:  OurDomain\User1.

    If I change the assigned user id in the table to the correct windows login, the PO Workflow options light-up.

    Have you figured anything out with this issue?

  • Jonathan Fear Profile Picture
    Jonathan Fear on at
    RE: Workflow 2.0 Issue - Incorrect AD Account Used for Manager

    Sounds like a possible bug to me. I just looked and I don't see this as an open bug. If you believe this is a bug I would recommend opening a support case to have it tested and documented.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans