Hello,
Microsoft Dynamics GP doesn't associate the USERID to an Active Directory user when it comes to workflow in general. It uses the following logic to determine which user launched the application and uses that Active Directory account to determine who should receive the email, aka who the submitted/originator was.
If you are launching GP on your Desktop locally, Workflow considers you logged in as the Windows User that you are logged into on your desktop (not the GP user that you sign in with on your local install).
If you are logging into GP via a remote session, Workflow considers you logged in as the Windows User that you logged into that remote session as.
If you are logging into the Web Client Version of GP, Workflow considers you logged in as the Windows User that you logged into the Web Client as in your Internet Browser.
Workflows are submitted and assigned in accordance with your Windows User’s as defined above, not your GP (SQL) user id.
If my windows user at my workstation or session is DOMAIN\BILL and I log into GP as SALLY, my workflow will ‘Originate’ or be submitted by BILL when I submit a transaction because BILL is my Windows User.
The only exception that I can think of to this would be for self service Payroll Timecards or PTE Timesheet when using the workflow assignment of Employee to Direct Manager. It wouldn't change who the originator was but would route the workflow based on the GP user in this specific scenario. See Blog below.
https://community.dynamics.com/gp/b/dynamicsgp/archive/2015/10/26/employee-to-direct-manager-workflow-process-how-it-works.
I hope this helps! If not, please let me know your exact situation and how it is reacting compared to how you are expecting it to react.
Thanks,
Isaac Olson
Microsoft Support
Share
Report
75
All responses (
Answers (
