Weird, I have a JSON export of my dataflow from couple of days back, it has dates in it. When I import it and refresh, it works perfectly fine. It is when I make any change to any table (no date field changes), it starts to collapse on tables with date fields. I hope Microsoft is working on a fix.
Even in Dataflows that have been running without intervention, they prompt for credentials
Dataflow Entities with DATE columns have been somehow changed to UNCLASSIFIED and are likely the cause of the error. Entities that do not include DATE columns work as expected.
When attempting to manually refresh a Dataset that includes Dataflows in question, it fails. In the Power Query editing, the error code is "Key does not match any rows", meaning it can't find the Dataflow
Edit Dataflow entities that have column type UNCLASSIFIED to TEXT. I titled the Custom Step "Text Workaround Step", so I can delete it after MSFT fixes.
I initially started changing from UNCLASSIFIED TO DATETIME (as mentioned above), but there were a few instances where after clicking "Save and Close", it reverted back to UNCLASSIFIED, so I just switched them all to TEXT
Refresh data in Power BI Desktop to update your Dataset
I couldn't agree more the absolute relief I felt stumbling across this thread by chance.. I've almost spent an entire day and night going insane over it deleting & re-creating entities, importing jsons, even creating entirely new workspaces... this is amidst also randomly finding out last week that there was apparently also a bug with the Advanced Compute engine preview that was potentially effecting dataflow refreshes.. (mine started randomly failing (not to mention the endless refresh issues I've had with Dataflows so far already) but I beleive that's now been resolved)... all these sanity-questioning bugs (lol) are frustrating when attempting to implement a new & unfamiliar technology.. and really spoiling my experience with Dataflows so far.. it's not been a good week 😞
Anyhow, thanks to this thread I've successfully had my Entities re-appearing in the Dataflows folders in the Power BI Service by following the workaround suggested earlier, changing the data type to DateTime (or Text also works). I really hope this gets fixed asap (and that others suffering the same pain stumble across this thread quickly too!!)
Thanks to those of you who have pointed out the exact cause of the issue, and for a workaround. I've just had a couple of days pulling my hair out too, and then raised a support ticket with MS about it. They have been very responsive and helpful and after much trace capturing etc they have pointed me to this thread, and also informed me:
It is already escalated to the Product Group Team and they said that they are working on it and shared the ETA for the issue.
"We're aware of the issues and planning a QFE path. Current plan is to have it deployed to ROW by end of week."