Extend Copilot in D365 Customer Service

(0) Share

Report

Posted on by Learner_pp

I am extending the Copilot in D365 Customer Service and below is the use case

There is a Standard "Account" table and Virtual table "Order(V)" with 1:N relationship having "Account" as a lookup column in the Order (V) table. When i creating a prompt i dont see the "Account" column in Filter attribute. This lookup column doesn't appear though it is searchable in the column properties.

My questions are

1) Am i missing something while referencing the Virtual table

2) Why does the lookup column doesn't appear in the Filter attribute, It is needed to pass the input as Filter value right?

All responses (1)

Answers (0)

Suggested answer

SaiRT14 1,318 on at

Like (0)

Report

Extend Copilot in D365 Customer Service

Virtual tables have certain limitations compared to standard tables in Dynamics 365, which might affect how they behave in queries or when interacting with Copilot.

Copilot Studio relies on metadata to surface fields in the filter attribute list. If the lookup field (Account) is not marked as filterable or lacks the necessary metadata, it won’t appear.

Go to Advanced Find or use FetchXML Builder to confirm that the Account field appears as a filterable column in the Order(V) table. Use the following FetchXML query to verify

<fetch>
<entity name="ordervirtual">
<attribute name="account" />
<filter>
<condition attribute="account" operator="not-null" />
</filter>
</entity>
</fetch>

Consider opening a support ticket with Microsoft if the issue persists, as it may be a limitation or bug specific to virtual table filtering.