Forum Discussion
PowerBI changes data table name to RealTimeData and creates errors
Dealing with the real time streaming dashboards, I have faced the same issue several times this past days. Everytime I set the new table name from ASA job, Power BI changes the name to RealTimeData. Finally I gave up and began setting the table names "RealTimeData".
In addition to your issue, when I try to update the dataset schema from the dataset actions menu, I get the same error. A single data type change is enough to break the streaming dataset.
Even when I try to disable and re-enable historic data (mostly to clear the previous data) I get another error and the visualizations are all messed up.
I'm guessing the changes to the model of the dataset refresh all the fields and when trying to keep getting the streaming data, the inputs are unaligned with the previous schema. I can see slight changes in ordering of column keys once in a while.
I've given up trying to find a solution, and frankly in the scope of current streaming visualization options, it's easier to re-create the whole dataset from the beginning. For a more detailed report though, this can get real frustrating real quick.
Did you have any luck in solving this mpeterson?
Hi Greyincarnation,
were you able to get the configured visuals working with the newly created dataset? And what exactly you did in ASA job output? Did you create completely new output with the same dataset name but with "RealTimeData" as table name? Or you did something else?
Best Regards
Edin
Hi emulic,
First I always delete the dataset and related reports, dashboards from the power bi service, then delete the power bi output from ASA job. Next, I add the Power BI output to ASA with a dataset name and RealTimeData as the table name.
ASA replaces the existing dataset if there is already another with the same name so it doesn't matter but I always give the table name RealTimeData.
That solves my troubles until next time I need to update something, and start all over again.
I can repro the issue, but the provided "workaround" seems like awful lot to do for a simple update, any comments Microsoft?
