ConnectorRequestFailure when trying to work with a Dataverse table

(2) Share

Report

Posted on by SB-16051357-0

Hi,

I am seeing the "Error Message: The connector 'Microsoft Dataverse' returned an HTTP error with code 400. Error Code: ConnectorRequestFailure" when trying to use the list rows in a dataverse table with an action setup in Copilot studio.

If I preview the table in the knowledge source then I can see the information that is in the table. The error seems to happen when I try to access the table via the HTTP request. The table only has one row in it so I feel it is unlikely to get too much data back from the look up.

Is there a way to see more details on the request that was sent and what was recieved apart from that in test results ?

Kind regards,

Steve

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (2)

Answers (0)

Expiscornovus 33,195 Most Valuable Professional on at

Like (0)

Report

Hi @SB-16051357-0,

I see you outputs is missing a variable and is set to the table data type?

Have you tried it with the record data type? And does that make a difference?

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

Was this reply helpful? Yes No
Suggested answer

DAnny3211 134 on at

Like (0)

Report
Hi, The `ConnectorRequestFailure` with HTTP error code `400` from the **Microsoft Dataverse** connector typically indicates a problem with the request payload or configuration, even if the table preview works correctly in the knowledge source. Here are a few things to check: 1. **Table name formatting**: Ensure that the table name (`Test-Inv`) is the **logical name** (also known as the schema name), not the display name. Logical names usually follow a format like `new_testinv` or `crd_testinv`. Using the display name can lead to a 400 error. 2. **Environment reference**: Double-check that the environment name (`PowerPlatformDev`) is correctly referenced and accessible by the agent. If the environment is not properly linked or the user lacks permissions, the connector may fail. 3. **Connection permissions**: Confirm that the connection used by the agent has sufficient privileges to read from the Dataverse table. This includes having the correct security roles assigned in the Power Platform environment. 4. **Inspect request/response details**: While Copilot Studio doesn’t currently expose full HTTP request/response logs directly, you can: - Use **Power Automate run history** to inspect the flow execution and see the exact error details. - Temporarily replicate the same action in a standalone Power Automate flow to capture more detailed diagnostics. 5. **Data volume**: Even though the table has only one row, ensure that no filters or query parameters are misconfigured, which could cause the request to fail. For further reference: - List rows using Dataverse connector - Dataverse table naming conventions Thanks and best regards, Daniele **Note: This response was prepared with support from Copilot to ensure clarity and completeness.**

1 people found this reply helpful.

Was this reply helpful? Yes No