Forum Discussion
Entities do not appear in Dataflow when creating Linked Entities
jeffshieldsdev That sounds new. DateTime fields were working fine. I am not sure the change to text is going to fix your problem. I have been using a mixture of DateTime and Text.
In the Edit Dataflow web UI, expand the Entities (not to be confused with Editing the Entities) and make sure none of the fields are appearing as "Unclassified". Any that are you will need to fix by editing the entities.
As an aside.
I get a 500 error if I use the Web UI for the sharepoint.files connector. For some reason the UI doesn't include the [ApiVersion = 15] parameter. I have to use the advanced editor and manually add that into the connector. I have asked my internal team to raise that issue with MS also.
Good luck with it all.
I heard that it is already escalated to the Product Group(PG) Team for their assistance and next update would be this weekend.
Please refer the support page for further updates from PG Team.
https://powerbi.microsoft.com/en-us/support/
Data Flow Current Issues:-
Power BI Customers who are using Dataflows may see scheduled refreshes not processed. As a workaround, customers can perform a manual refresh. Engineers are working on a fix and will provide an ETA soon
Customers creating a new Dataflow from the Power BI service will see the default setting "Allow combining data from multiple sources" set to true instead of false. As a workaround, customers can uncheck the setting. Engineers are working on a fix and expect it to be deployed by end-of-day 11/22/2019.
One more Issue
Data Flow Entities are missing while loading it from Power BI Desktop.
If this post helps, then please consider Accept it as the solution to help the other members find it more
If this post was helpful may I ask you to mark it as solution and click on thumb symbol?
- jcullum6 years agoAdvocate II
venal This is not the the same issue based on what you described. That workaround of manually refreshing will not work for issues related to Date columns with being set as a data type of Unclassified.
Please read the full thread, we do not want to be conflating all the separate issues that people are experiencing within the Dataflows component of the service. The Unclassified issue needs to be resolved as a matter of urgency.