BindingKeyNotFoundError with Type 'Prompt'

(2) Share

Report

Posted on by FarmingCode

I'm encountering a BindingKeyNotFoundError when developing a topic with a prompt to a Dataverse table. The error message is as follows:

[
  {
    "diagnosticResult": [
      {
        "$kind": "BindingKeyNotFoundError",
        "bindingKey": "IndividualName"
      }
    ],
    "componentDisplayName": "Individual Attributes",
    "componentId": "12345678-1234-1234-1234-123456789012",
    "diagnosticErrorCount": 1
  }
]

The topic and prompt run flawlessly within the studio, but the error appears only during development and publishing. This issue is related to a Run Prompt action, where the difference comes in. I've tried changing the binding key to the logical name, reviewing the environment settings, and watching YouTube videos like "How to Fix Variable Type Error in Copilot Studio" but the issue persists.

Has anyone else faced a similar problem with prompt actions? Any insights or solutions you can give me would be greatly appreciated!

Categories:

General topics

I have the same question (0)

All responses (1)

Answers (1)

Verified answer

FarmingCode 31 on at

Like (1)

Report

We resolved the issue by republishing the prompt from the 'Library' and then recreating the topic.

P.S. If someone encounters this issue in the future, they can also try using 'Generative answers'. However, we found that using the prompt gave us the desired results.

1 people found this reply helpful.

Was this reply helpful? Yes No