web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Unable to reference In...
Copilot Studio
Suggested Answer

Unable to reference Input Variables in Child Agent

(0) ShareShare
ReportReport
Posted on by 43
I am trying to setup a child agent that will call dataverse to fetch data. I specify my filter in my instructions. It looks like this:
 
Get data with tool /Get_data_from_dataverse where xxx_name eq '{section_name}' and xxx_version eq '{version}'
 
The problem is that the agent is unable to map reliably my input variables. I tried referencing the variables with '/' -> 'variables' but I only see system variables. Is this by design? Is there a way to map it?
 
UPDATE 2026-02-24
I was able to add the variable to the instructions by typing '/Topic.Input.version'. Then the variable started to appear. However, I don't if it's related to my variable name, the agent never maps the value. I tried other ways to specify the value. The agent just put a random value there.
Categories:
I have the same question (0)
  • Suggested answer
    Nivedipa-MSFT Profile Picture
    Microsoft Employee on at
    Hello ,
    Generative agents may produce incorrect parameter values if instructions are unclear.

    Quick Fix:

    1. Be very clear with instructions:
      Make sure to use the EXACT input values.
      xxx_name = {Topic.section_name} (do not modify this)
      xxx_version = {Topic.version} (do not modify this)
    2. Manually pass variables from parent to child – they do not transfer automatically
    3. Set input variables in the child agent’s settings first

    Better Solution:

    Avoid using agent instructions for filtering. Instead, use a Power Fx/Power Automate action:

    Filter(dataverse_table,
      xxx_name = Topic.section_name And
      xxx_version = Topic.version
    )

    This approach is deterministic—no unexpected values, and results will always match exactly.

    Generative agents are not reliable for precise data queries. For Dataverse operations, structured actions are recommended.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 277

#2
11manish Profile Picture

11manish 206

#3
sannavajjala87 Profile Picture

sannavajjala87 156 Super User 2026 Season 1

Last 30 days Overall leaderboard