Dynamics Community Forum Thread Details

Power Automate Flow with Power Query Dataflows connector BapListServicePlansFailed

Environment: Power Platform / Dynamics 365 / Managed Solution

Issue:
We have two Cloud Flows in a managed solution (JFNA Core Calculations) that use the Power Query Dataflows connector with the trigger "When a dataflow refresh completes."

Both flows have SVC PowerPlatform Automation as the primary owner. This account is not provisioned as a user in the Dataverse environment. When we attempt to Turn On or Turn Off these flows, we get:

BapListServicePlansFailed → MissingUserDetails — "The user details for tenant id 'xxx' and principal id 'xxx' doesn't exist."

Key Observation:
All other flows in the same environment in same solution with the same owner (SVC PowerPlatform Automation) turn ON and OFF without any issue. Only these two flows using the Power Query Dataflows connector throw this error.

What we confirmed:

SVC PowerPlatform Automation is NOT in the Dataverse users list

SVC PowerPlatform App User IS in the Dataverse users list

Changing primary owner to SVC PowerPlatform App User resolves the issue — flow turns ON and runs successfully

Questions:

Why does the Power Query Dataflows connector specifically require the flow owner to be provisioned in Dataverse, while other connectors (Dataverse, SharePoint) do not?

Why did these flows work initially when the owner was never provisioned in the environment?

Is BapListServicePlansFailed specifically a premium connector license validation against the Dataverse user record?

What is the recommended approach for flow ownership in managed solution deployments across multiple environments — should it always be an Application User? Any solution please help me out.