Question

Can't set Rule to assign CTA to Opportunity Owner

  • 12 August 2016
  • 5 replies
  • 50 views

Userlevel 7
Badge +7
  • Gainsight Employee: ACE
  • 550 replies
For our smaller customers, the CSM responsibilities are owned by a team of folks, until it comes time for the renewal, at which point an individual CSM is assigned the renewal Opportunity. We set them as the Opportunity Owner, and I would like to assign the "Renewal" CTA to them.



I have a rule that pulls in Opportunity Owner ID: https://cl.ly/3t1w3Y3t162p

However, the Owner ID is not available as an option when trying to assign the CTA: https://cl.ly/2v1j3h2t452g

5 replies

Badge +4
I like this use case!  Not sure why Opp Owner isn't showing up (I will look into it) but in any case that is the Default Owner field.  Wouldn't you want to select the Opportunity Owner ID in the Owner field? In fact, as a default the Account Owner might be good in case there is a problem at the Opp level.
Userlevel 7
Badge +7
Thanks for reaching out, Karl!  I actually did click into the "Owner Field", not the "Default Owner", when taking that screenshot. But I can appreciate that it's confusing from the screenshot, since the "Owner Field" drop-down then falls over the "Default Owner" field, as shown here: https://cl.ly/3x26122m3Q3B
Badge +4
Yes, of course.  I was being silly.  The Owner field is where you search for a field to map 🙂.  I am able to find Opp ID when I make a rule like this so I am not sure what is going on.  Maybe a permission issue?  I am asking Manu for help 🙂
Badge +4
OK. With Manu's help we have a theory.  The problem is on the UI layer.  Try doing a hard refresh on the action screen and see if the right options now appear.  I think that you are seeing the options from a previous rule that you were editing and for some reason it is being cached.  Assuming this fixes the issue please file a ticket as this is obviously not correct behavior. 
Userlevel 7
Badge +7
Thanks for brining in the big guns, Karl! Your hard refresh does seem to have fixed the issue. I've filed support ticket #13601

Reply