Post

Use Dynamic Inputs for Structured Queries in Copilot Studio

Diesen Beitrag auf Deutsch lesen

Configure a Copilot Studio connector tool with dynamic OData filters to query SharePoint lists and other structured data from natural-language requests.

TL;DR

In Copilot Studio, configure SharePoint Get Items with fixed site, list, view and $top inputs, then make $filter dynamic. A detailed input description lets the orchestrator turn natural-language requests into OData filters, retrieve narrower results, and generate conversational answers without Power Automate flows or custom code.

Original by Karima Kanji-Tajdin, on The Custom Engine. Read the original

This is our own summary, not a republication or full translation.

Governance takeaway

  • Makers: Describe column names, data types, valid values and example OData queries in the dynamic input so the orchestrator can generate better filters.
  • Admins/CoE: Keep $top sensible and require clarification for vague requests, because broad result sets can be truncated, glossed over or hallucinated.
  • Security/Compliance: Review whether connector tools, Knowledge and Work IQ match the required retrieval control, because configured tools provide more control over columns and returned rows.
  • Leadership/Business: Match the architecture to complexity, from static schemas to dynamic schema files or a dedicated custom prompt as lists evolve.

Frequently asked questions

How can Copilot Studio generate OData filters for a SharePoint list?

Make the SharePoint Get Items $filter parameter a dynamic input and describe columns, data types, valid values and example queries.

Which SharePoint Get Items settings should remain fixed in Copilot Studio?

Keep the site address, list name, view and $top fixed so the tool targets the intended list and limits returned items.

When should a Copilot Studio agent use a dynamic schema or custom NL2Query prompt?

Use a dynamic schema when columns change or expand, and a custom prompt when schema explanations and business rules overwhelm orchestration instructions.

This post is licensed under CC BY 4.0 by the author.