Adding Key Fields - "Expected Value"

Created by Mike Johnson, Modified on Thu, Jun 5 at 3:35 PM by Mike Johnson

Expected Value" Matching (Existing Functionality)


Overview:
Expected Value field is used to define a single expected value that must match exactly for the key field to be accepted as completed.


How It Works:

  1. Select a Key Field – Users choose any field type (Picklist, Text, Number, Currency, Percent, etc.).
  2. Define an Expected Value – The user enters the specific value that marks this field as complete.
  3. Completion Check:
    • If the Key Field’s value matches the Expected Value exactly, the  key field is accepted by the milestone as Completed (✅).
    • If the value is anything else or null, it remains considered as  Incomplete (❌).
  4. If No Expected Value Is Set:
    • The field is considered Completed as long as it is not blank (any value counts).

Example Scenarios:

Key Field TypeExpected ValueKey Field ValueCompletion Status
Picklist"Qualified""Qualified"✅ (Completed)
Picklist"Qualified""New"❌ (Not Completed)
Text"Approved""Approved"✅ (Completed)
Text"Approved""Pending"❌ (Not Completed)
Number"100""100"✅ (Completed)
Number"100""90"❌ (Not Completed)


Current Limitations:

  • Only supports exact matches. No way to define multiple acceptable values.
  • No support for greater/less than comparisons for numeric fields.



Need to match multiple acceptable values? Here's a workaround:


Workaround for Multiple Acceptable Values


Create a formula checkbox field that returns True when any of your valid values are selected. Then use that formula field as your milestone key field. Questions? Contact support — we’ve got you. In the mean time, here are a few examples of how to implement using "multiple "expected values" on one milestone key field. 


  • Text Field Example
    Returns TRUE if the text field contains one of these colors: Red, White, Blue, Brown, or Gray


CASE(TEXT(Color__c), 

  "Red", TRUE,

  "White", TRUE,

  "Blue", TRUE,

  "Brown", TRUE,

  "Gray", TRUE,

  FALSE

)


  • Number Field Example
    Returns TRUE if the number field value is 7, 8, 9, or 10


OR(

  Number_Field__c = 7,

  Number_Field__c = 8,

  Number_Field__c = 9,

  Number_Field__c = 10

)



  • Percent Field Example
    Returns TRUE if the percentage is greater than 75%


Percent_Field__c > 0.75



Picklist Field Example
Returns TRUE if the picklist value is Oregon, Washington, Idaho, or Montana


CASE(TEXT(State__c), 

  "Oregon", TRUE,

  "Washington", TRUE,

  "Idaho", TRUE,

  "Montana", TRUE,

  FALSE

)


  • Multi-Select Picklist Example
    Returns TRUE if any of these states are selected: Oregon, Washington, Idaho, Montana

OR(

  INCLUDES(Multi_State__c, "Oregon"),

  INCLUDES(Multi_State__c, "Washington"),

  INCLUDES(Multi_State__c, "Idaho"),

  INCLUDES(Multi_State__c, "Montana")

)




Important Reminder


Avoid using the following field types when adding your Key Fields:

  • Text Area

  •  Text Area (Long) 

  • Text Area (Rich) 

  • Text (Encrypted)

  • Address (it's ok to use Street, City, State, Zip, but not the field that bundles all of these together)



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article