Skip to main content
heather_hansen
VIP ⭐️⭐️⭐️⭐️⭐️
July 28, 2026
New Idea

Copilot: Should only consider active dropdown values and not all values

Related products:CS AI CopilotCS MCP
  • July 28, 2026
  • 2 replies
  • 66 views

I’ve been trying out creating activities in Copilot and the Slack app before I release it to my team, and in doing so, I've discovered that both return ALL dropdown values versus just ACTIVE values. 

When I asked Copilot about this, it told me this “I can’t verify from the available tool output which Blocker Type values are currently active vs. merely configured. 

  • The tool shows the configured allowed values for Blocker Type, but it does not indicate which of those are currently active/user-selectable.”

So, then, when I select one that’s not active, I get a message that it’s unable to create the activity because that one doesn’t exist.  Our users are definitely not going to know what those ALL of those values are, and it’s not a great experience to tell them to pick one from a list, and then, tell them not that one.  

Can this please be addressed ASAP?

 

2 replies

heather_hansen
VIP ⭐️⭐️⭐️⭐️⭐️
July 29, 2026

FWIW, I was able to keep prompting it until it finally gave me the list of only active options, and then, create a Key Definition to force it to do this when someone asked, but I shouldn’t have to go that far.

This is what it told me about why it gave 2 different lists.
Short version:

  • Activity type config = broader configured values for creation flow
  • Object metadata = current field-level selectable values
  • I should have used the field metadata standard from the start.
angela_domenichelli
Contributor ⭐️⭐️⭐️⭐️⭐️
July 29, 2026

Piggy-backing here that field dependencies are also not considered by copilot OOB and need specialized Key Definitions (which don’t seem to work in all instances of testing)

Angela Domenichelli (She/Her/Hers)