When Dynamics 365 Finance & Operations (F&O) data entities are exposed as Dataverse virtual tables, the unbound OData actions published by F&O are visible and selectable in the Microsoft Dataverse connector in Power Automate (e.g., “Perform an unbound action”).

However, when the flow runs, the action fails with a runtime error similar to:

Error 0x80060888 / 404 – Resource not found for the segment ‘mserp_’

This creates a confusing and inconsistent experience:

The action appears valid (because it shows up in the action list / metadata)

But the platform cannot execute it via the Dataverse connector path, causing runtime failures and forcing customers to use other integration approaches.

Dataverse actions are generally categorized as bound vs unbound, where unbound actions are invoked at the environment level. 

Expose an F&O data entity as a Dataverse virtual table, then invoke its unbound OData actions from Power Automate using the Dataverse connector.

Business Impact

This impacts real implementations of Power Automate flows:

Customers can’t implement flows end‑to‑end using the Dataverse connector if unbound actions are required.

They must switch to the F&O connector or custom HTTP calls, which increases complexity and operational maintenance.

Multi‑entity / multi‑environment rollout scenarios become harder to maintain (flows must be adapted per environment, and connector limitations add overhead.