Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi,
I have a workspace that is configured to use PowerBI's inbuilt storage for dataflow. I created a dataflow that would connect to AdventureWorksDW2017 database on my on-premise server. Created an entity for DimAccount table, saved it and refreshed. It works fine. The refresh log is as below
Run time | Dataflow name | Dataflow refresh status | Entity name | Start time | End time | Entity refresh status | Error |
11/2/2019 13:13 | TestDF | Completed | DimAccount | 11/2/2019 13:13 | 11/2/2019 13:14 | Completed |
I created a new workspace and have configured it to store the dataflow in the linked ADLS2 storage. And then created a dataflow that would connect to the same AdventureWorksDW2017 database on the same on-premise server. Created an entity for DimAccount table, saved it and refreshed. It FAILS to refresh. Please note that the folder structure and the empty files do get created in ADLS2, but it fails to populate those with data. The refresh log is as below
Run time | Dataflow name | Dataflow refresh status | Entity name | Start time | End time | Entity refresh status | Error |
11/2/2019 13:12 | DimAccount | Failed | DimAccount | 11/2/2019 13:12 | 11/2/2019 13:12 | Failed | Error: Internal error Request ID: 04834762-aaa4-70e8-6df8-395d82fb809f Activity ID: af3147ad-4f6a-4e83-acc8-402fb5ba81a4 |
In the same workspace, when I created a new dataflow, to store the data in the ADLS2 storage and this time used Azure SQL Database or D365 CRM online as source, for the entity, the refresh is successful. I do see the files getting created in ADLS2.
Please help me in resolving this refresh issue.
Regards,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.