Extend Copilot in D365 Customer Servcie

(3) Share

Report

Posted on by Learner_pp

We have a use case with Copilot in D365 Customer Service.

Agent asks the copilot: "Fetch me the Orders for account 'Contoso'."

in this case we have two tables involved Accounts(Std table in Dataverse), Orders(Virtual table in dataverse). The orders table is only retrieved with Data from third party when accountid is passed.

note: To fetch orders accountid is must.

I have developed a custom connector with two actions

1) FetchAccountIDByAccountName

2) FetchOrdersByAccountID

There is no response for the copilot and I am not able to realize the issue

When I republish the connector, it seems to be in pending state for long time. Also new connectors wont appear after publish.

I am looking forward to understand if the approach i have used is correct and why the connector doesn't appear after publishing in Copilot Studio.

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Muhammad Shahzad Sh... Most Valuable Professional on at

Like (0)

Report

Extend Copilot in D365 Customer Servcie

A: Refactor the custom connector to expose one action: FetchOrdersByAccountName, which internally handles both steps (resolve AccountID → fetch Orders).
B: Use Power Automate to wrap both steps and call the flow from Copilot.

Was this reply helpful? Yes No