I need to be able to change case to current case owner's manager using standard manager ID field on User object. As shown in the screenshot below. Process Builder

I am getting following flow error every time flow executes and meet entry criteria.

This error occurred when the flow tried to update records: The flow failed to access the value for myVariable_current.Owner:User.ManagerId because it hasn't been set or assigned.. You can look up ExceptionCode values in the SOAP API Developer Guide.

I made sure that my manager lookup on user record is populated with value.

I have also tried creating formula field on case to get owner manager id and try changing owner with that id but I am getting the same error. Please note that I am system admin and have Manage internal user permission.

Can someone please help me resolving this issue?

  • when is this process builder running (on update or insert)? Is it possible there's no owner assigned which is the issue? You checked the user had a manager, but do you know what the value of the owner is on the case before this point? Oct 9 '19 at 18:48
  • @KrisGoncalves This executes on update. And yes I assigned that case to myself. So I am the owner.
    – Ricky
    Oct 9 '19 at 19:35
  • Well, I was going to suggest trying it using a formula type instead of field reference to see if you get the same error. I'd guess that it must somehow not be the value you're expecting - is there any trigger or WF update on owner that would run before PB? Oct 9 '19 at 20:01
  • Yes I also tried using formula type within PB and same result. There is no workflow or trigger executes on owner field.
    – Ricky
    Oct 9 '19 at 20:08


I've experienced this before where I swear process builder would throw an error on a related objects' field even though the field has a value. I included the post above to show this is not just something I made up.

I think a good test would be to (in a test environment), just create a formula field on case that includes the Manager ID of the owner of the case to confirm that process builder can change owner with a custom field on the same object without error. This way, you can isolate the issue to navigating through the related object.

Whether this is a necessary workaround, I'm not sure. It might be worthwhile to put in a case with Salesforce or test out activating the critical update concerning process builder and relationship fields (this is related to null values, but worth it in a dev box to give it a try to see if it helps).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.