1

I have a Process that triggers a Flow. The flow takes a user from a lookup field on Account and adds them to the Account Team - work fine

My issue now is that I want to delete the user from the Account Team if the value on the lookup field is deleted.

I'll also want to delete the user if the value in the lookup field changes but will worry about that later

I've made a Flow to delete the User - which is fine - the problem seems to be my Process - I keep getting the error "The flow failed to access the value for [example] because it hasn't been set or assigned."

To trigger the Flow from the Process I've set the condition to be ISBLANK(User_Lookup) && ISCHANGED(User_Lookup) from which is pass the variables to my Flow AccountID PRIORVALUE(User_lookup.id)

I've tried a few variations of this - using ISNULl, using the Conditions are met way but always get the same error

Any ideas? How can i trigger this flow from a ISBLANK ?

Note: In the Process, the first condition is NOT(ISBLANK(User_Lookup)) && ISCHANGED(User_Lookup) - this triggers the adding of the user to the Account Teams - its working fine

1

Got it working (with some help from David above) - because i was going crazy i added a wf to capture the previous user id - i might look to get rid of this

Firstly I was kinda being stupid in the PB - my initial criteria check on the PB was looking at the RelatedUser.id field - so it was a cross object relationship. specifically NOT(ISBLANK(RelatedUser.id))

This was fine as long as you where adding a user to the team, once you went to delete one though it threw up the error "The flow failed to access the value for [example] because it hasn't been set or assigned."

I was wondering why I could not just see the field standalone like you normally do (see below)

enter image description here

Anyway turns out the field was renamed ages ago - just had to search a bit harder to find and PB does not make that easy

Finally my delete Flow was a bit wrong - you first have to lookup the Account Team Table to get the ID (its no good using the UserID) - then just delete the relevant Account Team Member Record - no need to delete the share also

0

One of the biggest issues with Process Builder is the crappy error support it has. Almost impossible to really debug without wasting a whole day.

Your logic looks great. It seems that you're PB isn't referencing the PRIORVALUE... and I'm not really sure how to recommend fixing something that seems like you've setup fine. I would suggest workaround where you 'on create or change' populate a text field with the UserId of the new person. That way, you can always query the old ID, and then remove the existing User, and then clear it out in your Flow with the new value or a blank value. Obviously not ideal, but you seem like you know what you're doing... and 'failed to access the value' is a common issue I find with PB, so I just always find myself attempting to use as little of a PB as possible - until they improve it.

  • 1
    Thanks David - that helped a bit. PB's error messages are so crap – Podger Jan 21 '16 at 16:03

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.