Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Karl Stadick]

Hi!

We are setting up Workflow in GP 2015 R2. I have tried setting up a Financial GL Batch Workflow and a Vendor Setup Workflow and in both cases, when we click “Submit” and check the Workflow, we receive the error: “The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found.”

I have tried setting up very simple workflows with originator being the approver and with and without additional approvers and keep getting the same error. I have run the exec wfDeployClrAssemblies Stored Procedure on our Dynamics database but it hasn’t helped. All of the Managers and User Names are pulling correctly from Active Directory.

Looking for other items to check.

Thank you!

Karl

——————————
Karl Stadick
Dynamics GP Administrator
Estenson Logistics LLC
Mesa AZ
——————————

[Jo deRuiter]

?Hi

It’s very possibly a permissions issue.  Since GP Workflow is built off of the “AD” (Active Directory) containers in GP.   The user’s AD Accounts will need to be added to SQL Server with permissions in the GP databases.

Contact your sys admin or GP Partner to help you set up the AD securities in SQL.

Let us know if you have any other questions!?

——————————
Kindest Regards,

Jo deRuiter
“That GP Red Head”
Senior Financial Systems Consultant
Advanced Credentialed Professional-Dynamics GP
Chairman, GPUG Partner Advisory Board
Heartland Business Systems, LLC
Milwaukee, WI
770-906-4504 (Cell)
——————————
——————————————-

[Rob Klaproth]

Hi Karl and Jo.  First of all, users do not need to be added to SQL to approve workflow items.  The whole benefit of GP workflow is that you can add active directory users without them being GP or sql users. 

Second, when alternate final approver kicks in something is wrong with your work flow design.  There is either a rule such as not allowing self approval or none of your conditions are being met so it’s triggering the alternate.   You should always define an alternate approver for each workflow just in case this happens.  

Start out by removing all your conditions and just set it to always route to a single person.   Once you’ve tested that the workflow engine is working and routing to that person then start working on your conditions. Remember to be careful when using the and plus or operators together as they can cancel each other out if they are used in the wrong order.   Double check all your conditions too.  The Gl account condition is based off the account index number NOT the GL account so that throws people off a lot. 

Post a screen shot of your conditions if it’s still not working.

——————————
Rob Klaproth
Dynamics Certified Professional
(GP Install & Configure)
Sr. GP Consultant
Armanino, LLP
San Diego, CA
——————————
——————————————-

[Jo deRuiter]

?Here is where I have found my resolutions in the past.

The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found. – Microsoft Dynamics GP Community Forum

Dynamics		remove preview
The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found. – Microsoft Dynamics GP Community Forum I’m getting the same thing. I ran the ‘ wfDeployClrAssemblies’ script and got the following returned. My client did remove the old GP server off the network. Any help would be appreciated. (1 row(s) affected) Configuration option ‘clr enabled’ changed from 1 to 1. Run the RECONFIGURE statement to install. View this on Dynamics >

I would try Rob’s technique, but I’ve had to solve this with data permissions.   I’d be interested to see if Rob’s technique works.

——————————
Kindest Regards,

Jo deRuiter
“That GP Red Head”
Senior Financial Systems Consultant
Advanced Credentialed Professional-Dynamics GP
Chairman, GPUG Partner Advisory Board
Heartland Business Systems, LLC
Milwaukee, WI
770-906-4504 (Cell)
——————————
——————————————-

[Derek Albaugh]

What can also cause this, is if the Windows account/SQL Server account doesn’t have permissions to query the Active Directory to verify the approvers/alternate approvers/workflow managers for this workflow type, it will automatically reject the workflow.

If a workflow doesn’t meet any of the approval conditions, it will only be routed to an alternate approver if you have the option marked to ‘always require at least one approval’, otherwise it’ll just ‘Complete’. Now, this is different in Dynamics GP 2018 where we added an option on each step to tell it what to do if the step doesn’t meet conditions.

If the workflow in GP 2015 R2 doesn’t meet approval conditions, and you do have the option to always require approval marked, it’ll first look for the alternate final approver on that workflow, if it doesn’t find any, it then will actually default to the Workflow Manager of that workflow type. A manager is required on each workflow type before you’ll be able to activate it.

That being said, I’d make sure your Workflow account/SQL service account has permissions to query Active Directory and validate the approver’s accounts. If the approvers are in OU containers in Active Directory, the accounts would need permissions to access/read each of those OU containers. By default, the users would be under Active Directory Users & Computers > Users, but usually customers have the users in levels of OU layers.

Another test would be to disable your current workflow and create/activate a new one, with only one workflow step which always requires approval, thus it will always go to the approver(s) of that step, then see if the workflow still gets rejected or not.

Thanks

——————————
Derek Albaugh
Sr. Support Engineer
Microsoft
Moorhead MN
——————————
——————————————-

[Karl Stadick]

Hi!

First of all, I wanted to thank everyone for their input and willingness to help.

Per Derek’s last response, if I mark “Action is always required for this step”, set the “Use alternate final approver” as me and I am also the only Manager assigned to this workflow, it still errors out.

I had my Network Administrator check our OU containers in Active Directory and we have all of the appropriate permissions.  I have tested 2 different workflows and get the same result.

Is there anything else we should check?

Thank you!

Karl

——————————
Karl Stadick
Dynamics GP Administrator
Estenson Logistics LLC
Mesa AZ
——————————
——————————————-

[Derek Albaugh]

So, the workflow isn’t even being passed to the workflow manager, it is being rejected outright.

In that case, as a test, try the following:

1. Change the service account running SQL Server to be a domain admin.

2. Logon to a machine as a domain admin and login to Dynamics GP to submit another workflow.

Does the workflow get rejected outright again, or does it get send to the designated approver(s)?

I’m also curious if we’re using users from more than one domain? If so, if you login to a machine as a domain user that is on the same domain as Dynamics GP and SQL, then login to Dynamics GP and submit a workflow, does it reject automatically or not?

Again, about the only time we see workflows auto-rejected like this, is because Dynamics GP/Workflow cannot validate the approvers/alternate approvers/workflow manager accounts in Active Directory.

This normally occurs because the SQL service account / users don’t have permissions to query the AD to validate these domain accounts and/or the designated approvers/alternate approvers/workflow managers are on a secondary domain that doesn’t have the trust setup correctly, the way Dynamics GP requires.

Thanks

——————————
Derek Albaugh
Sr. Support Engineer
Microsoft
Moorhead MN
——————————
——————————————-