Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

Microsoft Account Login Prompt in Workflow

Posted on by 50

Dynamics GP Build Version: 18.4.1436

When a user edits or presses submit for a Purchase Order Workflow the user is intermittently prompted for a Microsoft account loginExchangeLogin.png. The user clicks on the name and the prompt disappears. The email notifications for that submission will not be received but a new one will work after that. This can go for an hour without issue and then pop up during a submission or a save to changes in the workflow.

The customer also sends EFT remittances and an Application ID is setup in Company Email Settings. EFT remittance works without issue. If the application ID is removed Workflow works without issue but obviously the EFT remittance stops working.

Email testing in Workflow setup works fine. Looking for possible reasons that the email connection is broken.

Have been through the email troubleshooting guide

Thanks

Categories:
  • Suggested answer
    RE: Microsoft Account Login Prompt in Workflow

    The emails to the submitter, such as letting them know a workflow was submitted, approved, rejected, completed, final approved, etc., I do know we had issues with those in 18.4 that were resolved in 18.5.

    I'm not really following the rest though and may need a support case to look at your environment directly........

    You mention that "Emails make it to the sent folder after clicking on the Exchange login for the next workflow", which, is how it should work. If the submitter or approver haven't already entered their Exchange credentials for Modern Authentication prior, when they submit or approve a workflow, it'll prompt them for their Exchange credentials, before sending the email out and completing the process.

    They should only be prompted for their Exchange credentials one time for as long as they're logged into Dynamics GP, they shouldn't have to enter their credentials each and every time they attempt to submit or approve a workflow. If you're seeing this, then there's definitely not something setup correctly with Modern Auth.

    I'm not sure what this means exactly either:

    "If the user clicks on their login they are not prompted for a password. Any new workflow or change after that will work for a while and then it will pop up again sometime later with a new workflow or change."

    When prompted for credentials via the 'sign in to your account' windows, if they've signed in before on that machine, it's possible that their account and even password is saved, they just have to click OK, the exception here would be if they have multi-factor authentication enabled, then they'd have to enter that code or challenge.

    Again, this should only be the first time they attempt to email in Dynamics GP and they shouldn't need to keep being prompted for those credentials each and every time.

    There was another bug we had in an earlier version of 18.x where the token that Modern Auth was using, would expire every hour or so, but it appears you're past that version/build.

    Thanks,

  • renzweiler Profile Picture
    renzweiler 50 on at
    RE: Microsoft Account Login Prompt in Workflow

    - What email is not being received?  The email that lets the submitter know the workflow has been submitted. Any email to the approver following the submission.

    Emails make it to the sent folder after clicking on the Exchange login for the next workflow.

    I have run the EXEC wfDeployClrAssemblies a number of times.

    If the user clicks on their login they are not prompted for a password. Any new workflow or change after that will work for a while and then it will pop up again sometime later with a new workflow or change.

    Going from GP2018, 18.3, 18.4 now 18.5.  I know how that will be received by the customer.

    Thanks for the reply

  • Suggested answer
    RE: Microsoft Account Login Prompt in Workflow

    If you currently have Modern Authentication enabled in your GP 18.4 environment (which if you're using Exchange email, you most likely do) it's normal that when a user logs into Dynamics GP and then submits or attempts to approve/reject a workflow pending their approval, they'll be prompted for their Exchange credentials via the 'Sign in to your account' windows you mention, as that is what Workflow will send the emails through.

    The SMTP account/server is only used, when Modern Auth is enabled, to send out test emails, otherwise it isn't used at all. The exception would be when approving workflows through the email notification links, which is using Web Services functionality. Since Web Services doesn't use Modern Auth at this point, it defaults to emailing through the SMTP server/account specified in the Workflow Setup window.

    This process of asking for the Exchange credentials is also true when emailing something non-workflow related or accessing a email window.

    It should ask for the user's Exchange credentials and use those to email through, for as long as the user is logged into Dynamics GP.

    It seems the issue you're seeing is "email notifications for that submission will not be received but a new one will work after that. This can go for an hour without issue and then pop up during a submission or a save to changes in the workflow"....

    What email is not being received? Is it the email to the approver(s) letting them know a workflow is assigned to them and pending their approval, or is it the emails sent to the originator/submitter letting them know when a workflow is submitted, approved, final approved, etc., if applicable based on your setup?

    I ask because with 18.4, on different builds we had different issues with the workflow emails, more so the emails to the originator/submitter than the approvers, and these issues were pretty much resolved in the latest 18.5 releases.

    Also, if emails are working and then not working, I'd be curious if you see the emails making it into the SENT folder of the Exchange account of the submitter or approver, depending on which account the email is coming from, to see if it's being generated by Dynamics GP but not sent to the recipient, or not being generated.

    It also doesn't hurt to run this script against the GP system database:

          EXEC wfDeployClrAssemblies

    Thanks,

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,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans