Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
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 |
8/2/2019 11:48 | TestDF | Completed | DimAccount | 8/2/2019 11:48 | 8/2/2019 11:48 | 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 |
8/2/2019 11:53 | DimAccount | Failed | DimAccount | 8/2/2019 11:53 | 8/2/2019 11:53 | Failed | Error: Internal error Request ID: 6fd36043-14b6-1d26-3060-c801ad3f686f Activity ID: d45206eb-13e8-415a-a571-f5a9fce18fc5
|
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
hi, @Anonymous
I would suggest you create a support ticket here.
Best Regards,
Lin
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.