Forum Discussion
Dates dataflow suddenly reverting to earlier version, dropping fields
Thanks for the reply, edhans . I guess that's possible. Here's the confounding part: The report in question didn't fail in the couple days after I'd last done development on the Dates dataflow, which I'd expect to have happened if I somehow managed to revert to a cached version of my dataflow. I guess this is a good reminder to save the code for these tables somewhere outside the service. Mea culpa.
I've never seen a dataflow revert, but what could have happened is if you opened a dataflow and got a message similar to "this dataflow wasn't closed properly would you like to recover from the cache" and you do, or don't, it can change what is there. Unfortunately, it will not tell you what pressing Yes or No will actually do to the code, so it is a shot in the dark. Unless I had a browser crash, I almost always hit no. That browser tab instance could have a cache from a few days ago.
Thanks for the reply, edhans . I guess that's possible. Here's the confounding part: The report in question didn't fail in the couple days after I'd last done development on the Dates dataflow, which I'd expect to have happened if I somehow managed to revert to a cached version of my dataflow. I guess this is a good reminder to save the code for these tables somewhere outside the service. Mea culpa.
You can export the JSON and restore the dataflow, but it will assign the dataflow a new ID, which means you'll need to tweak that code in your dataset. Kind of a pain... but all M code for the entire dataflow will be in one file.
Thanks for this replay, edhans . I've not done this...looks like I'd export it via PowerShell? Will the JSON contain all the historical changes in the dataflow? I.e., will it contain the code that's now missing in the dataflow's current incarnation?
No, it in the menu for dataflows.
It is the current version. I am not aware of any versioning for dataflows.