Personalized Community is here!
Quickly customize your community to find the content you seek.
Building a more successful workforce with Dynamics 365 Human Resources Microsoft delivers solutions that enable businesses to build winning teams and create a workplace where people can succeed. To help ensure we are providing the very best solutions to empower employees, and as we look at LinkedIn’s unique strengths in the talent acquisition market, we plan to refocus our HR technology roadmap and partnership investments for Dynamics 365 | Read More about successful workforce.
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I have an Annual Leave workflow configured where a leave request first goes to the worker's direct line manager, (hierarchy level 1) and then onto the Human Resource Manager security Role. All works correctly. However, if the line manager selects Deny rather than approve, although the status of the request correctly updates to Denied, in the workflow history, it errors with the following fault:
"Stopped (error): Invalid operation - the state transition from Denied state to InReview state is invalid."
Although the outcome is as the client requires, the fault in the workflow history is bothering them. I haven't been able to prevent this error, which I am guessing is because the workflow is trying to move onto the final stage but can't because of the deny action.
Has anyone come across this before and is there a way to prevent the fault in the workflow history?
I would suggest to create a ticket for Microsoft Support as it sounds like a bug to me.
I have looked at your question and believe that adding a conditional statement prior to the Human Resource Manager approval might solve the issue. It could look like that.
However, it is hard to advice you as I have not seen the set up of your workflow. If my suggestion has not helped, please submit a support request and add the extract of the workflow (Personnel management | Links | Human resource workflows | select the WF | Versions | Export). This would help us to troubleshoot specifically for your scenario.
Many thanks for the response, Agne.
I had the same idea and did try including a condition but couldn't manage to capture the status before the error.
Thanks for the response, Andre. After trying a lot of different solutions, I think raising a ticket is the best option.
Business Applications communities