Answered

Workflow with Connector to Dataverse Error "Change type must be integer" no matter what is selected

(0) Share

Report

Posted on by MC-20031332-0

Copilot Studio > workflow >

Trigger type > Connector > Add > Microsoft Dataverse > when a row is added modified or deleted

Immediately, Copilot Studio displays warning, "2 new issues detected"

Change Type = Added or Modified or Deleted

Immediately, Copilot Studio displays warning "Change type must be an integer"

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Vish WR 3,748 on at

Like
a
(1)

Report
Copy link

Link copied!

@MC-20031332-0

This is a known bug in Copilot Studio. The Change type dropdown shows text options but internally expects an integer and the UI doesn't handle that correctly, so no matter what you pick you'll hit that error.

Two options to work around it:

First, try switching the trigger type to the native Dataverse option instead of Connector if it shows up in your workflow.

Second, build it as a regular Power Automate flow outside Copilot Studio. The same Dataverse trigger works perfectly fine there. You can then call that flow from your agent.

Changing the dropdown selection won't fix it, the issue is in how Copilot Studio wraps the connector itself.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
MC-20031332-0 8 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Vishnu - thank you for clarifying this is a known bug in Copilot Studio.

RE: try switching the trigger type to the native Dataverse option - there is no "native Dataverse option" as the screen shot below shows the only options are: Manual, Recurrence, Connector, or When an HTTP request is received.

RE: build it as a regular Power Automate flow outside Copilot Studio - Yes, I have already tested that a regular Power Automate Flow can reliably be triggered by a Dataverse table add, modify or delete. However, switching to Power Automate kind of defeats the purpose as I was trying to evaluate the new Copilot Studio workflows.

Was this reply helpful? Yes No
Prasad-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi MC-20031332-0 We have highlighted this concern to the Engineering team and have raised a bug for further investigation. Once we receive any updates, we will keep you informed. Thank you!

Was this reply helpful? Yes No