Power Platform Community Forum Thread Details

I'm developing a web application in Copilot Studio where users select their expertise level, and I want the responses to be tailored accordingly. I need guidance on the best approach to implement this and clarification on the orchestrator's role, as well as how to use PowerFx and variables effectively.

Implementation Approach for Tailored Responses:
Currently, I'm using a tool to generate responses in a specific format based on the user's expertise level. Is this a recommended pattern? Or should I have the tool return raw data and let the orchestrator handle formatting and tailoring the response to the expertise level?
- What is the intended role of the orchestrator in Copilot Studio? Am I offloading too much responsibility to the tool by having it generate the exact response text based on the expertise level passed to it?
- Is there no definitive "right" approach, and is it context-dependent? In my case, is it acceptable for the tool to produce the final response text by incorporating the expertise level in its prompt?
PowerFx and Variables in Instructions:
I'm also struggling with using PowerFx and variables within Copilot Studio instructions. For example, I expect System.Activity.Value to contain data (e.g., the user's expertiseLevel) at certain points in the process, but I'm encountering unexpected errors.
- When is System.Activity.Value available, and can the orchestrator access variables like expertiseLevel?
- How should PowerFx and variables be properly used in instructions to avoid errors

Any insights or best practices for these topics would be greatly appreciated!
Thanks,
Wesley

Screenshot 2025-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

General topics

Hi,

A good pattern is to keep the tool focused on retrieving or generating the core data and let the orchestrator tailor the final response based on context, such as the user's expertise level. That said, there isn't a single "correct" approach. If your tool consistently produces better results by incorporating the expertise level directly, that's perfectly valid. The key is to avoid duplicating logic across multiple tools when the orchestrator can handle presentation and personalization.
For variables, be careful with System.Activity.Value as it's only available in specific contexts and may not always contain the data you expect. For user preferences like expertiseLevel, it's usually more reliable to store the value in a variable and explicitly pass it to topics, tools, or instructions that need it. If you're seeing inconsistent behavior, try inspecting the runtime values during testing to confirm when the variable is actually populated.
My recommendation would be:

Store the expertise level in a dedicated variable.
Pass it to tools when it materially affects the generated content.
Let the orchestrator handle final formatting and conversational adaptation where possible.
Avoid relying on System.Activity.Value unless you know exactly which activity payload is populating it.