Unanswered

DataFlow - "Next" Button disabled

(0) Share

Report

Posted on by james_hathaway

427

I am trying to build (another) dataflow in my Dataverse Environment to get data from an On Premise SQL Server into dataverse.

I am able to define the SQL query without any issues, but I am unable to progress to the "Map Columns" screen - the "Next" button is simply greyed out/disabled.

Anyone have any idea why?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Sort by

AhmedSalih

6,680 Moderator on at

Like (0)

Report

Copy link

Link copied!

Hello, @james_hathaway , Do you have Environment Maker security role in the Environment?

Check this for more info: https://learn.microsoft.com/en-us/power-query/dataflows/security-role-standard-dataflows#roles

Environment Maker : Required to create any dataflow. Standard dataflows require additional roles depending on Dataverse tables permissions

If my reply helped you, please give a 👍 , & if it solved your issue, please 👍 & Accept it as the Solution to help other community members find it more.

I am primarily available on weekdays from 6-10 PM CT and 5-10 PM CT on weekends.

Visit my Blog: www.powerplatformplace.com

Was this reply helpful? Yes No

james_hathaway 427 on at

Like (1)

Report
Copy link

Link copied!

Yes, I have that security Role.

There's a clue in my initial post - I said I was trying to make ANOTHER dataflow in my environment...
... suggesting that I have already created at least 1 dataflow in this environment before.
(I have 15 running regularly)

Was this reply helpful? Yes No
DadaDude 11 on at

Like (5)

Report
Copy link

Link copied!

Encountered a similar problem.
The issue was that the Query Enabled Load checkbox was not ticked.

Was this reply helpful? Yes No
365-Assist 2,327 Moderator on at

Like (5)

Report
Copy link

Link copied!

In case anyone is wondering where the Query Properties Options solution is (as per @DadaDude😞

Was this reply helpful? Yes No
StevenHampson 16 on at

Like (0)

Report
Copy link

Link copied!

Thank you! That was exactly my issue. I was in the middle of some dev work and set my table to do not load so I could at least save it, and when I went back in the next day, disabled. Set to Enable load and that did the trick.

Was this reply helpful? Yes No