"Opportunity is Updated" "Trigger Attribute" constraint missing | Community
Skip to main content
Devraj_Grewal
Devraj_Grewal
New Participant
February 5, 2016
Solved

"Opportunity is Updated" "Trigger Attribute" constraint missing

  • February 5, 2016
  • 3 replies
  • 2438 views

Hello,

What I found odd is that there is a specific field in the opportunity that I am trying to trigger by. When I select the drop down for "trigger attribute", it is not available. However, when I type the field in directly and save, there is no red error line under the title so I am to believe it is a valid option. Does it mean that although I could not select the field, it is going to trigger off of it now?

Thanks,

Devraj

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Devraj_Grewal

Heard back from Support and they confirmed that if you manually input the correct field, it will still work. The pick list values for the constraint are just a suggestion list of possible values as there is a limitation of how many items it can show. So i just typed in the exact name of the field in the opportunity and the red squiggly error line does not appear.

3 replies

Devraj_Grewal
Devraj_GrewalAuthorAccepted solution
New Participant
February 6, 2016

Heard back from Support and they confirmed that if you manually input the correct field, it will still work. The pick list values for the constraint are just a suggestion list of possible values as there is a limitation of how many items it can show. So i just typed in the exact name of the field in the opportunity and the red squiggly error line does not appear.

    Josh_Hill13
    Josh_Hill13
    New Participant
    February 5, 2016

    Opp filters are a bit weird because everyone has slightly different things going on. I've also had a lot of problems with the drop downs lately not populating quickly or having too many options, then it just doesn't fill in all the way.

    You can just test it by modifying a test Opp. Did it work? Great! If not, then it's not going to be valid.

    A
    Anonymous
    February 5, 2016

    I haven't tested this out, but when I just added a random made up field I did get the red squiggly error line.

    Devraj_Grewal
    Devraj_GrewalAuthor
    New Participant
    February 5, 2016

    Actually, the field is a valid field, I just can't find it under the drop down list. But when I type it in manually, there is no error line under it.

    A
    Anonymous
    February 5, 2016

    Got it. Seems like it should work if there's no error line but perhaps a Marketo product team member could confirm

    Terms & ConditionsAccessibility statement

    Loading footer...