Forum Discussion

mpeterson's avatar
mpeterson
New Member
9 years ago

PowerBI changes data table name to RealTimeData and creates errors

I am sending data to PowerBI from Azure storage using a stream analytics job.  I can see my data table in the PowerBI interface (I called it deviceData), but when I create a report from the data stream, PowerBI changes the name of the data table to RealTimeData.  Then when I create any visuals, I get errors saying "we are not able to identify the following fields: RealTimeData. Please update the visual with fields that exist in the dataset".  How do I get PowerBI to not change the name of my data table so it can find the data?  

7 Replies

  • Eric_Zhang's avatar
    Eric_Zhang
    Microsoft Employee

    mpeterson wrote:

    I am sending data to PowerBI from Azure storage using a stream analytics job.  I can see my data table in the PowerBI interface (I called it deviceData), but when I create a report from the data stream, PowerBI changes the name of the data table to RealTimeData.  Then when I create any visuals, I get errors saying "we are not able to identify the following fields: RealTimeData. Please update the visual with fields that exist in the dataset".  How do I get PowerBI to not change the name of my data table so it can find the data?  

     


    mpeterson

    When enable "Historic data analysis" for a streaming dataset, by default, the historic data table is called "RealTimeData". I was trying to reproduce the error in your case, however the visual just show correctly.

     

    Could you be more specific about the problematic visuals and upload a snapshot of the error message?

    • mpeterson's avatar
      mpeterson
      New Member

      I was following the IoT setup tutorial in Azure so I created a stream analytics to get the data to Power BI.  I can see my data table in Power BI but now when I try to change it and turn off the historic data I get an error that "something went wrong".  

       

      Regarding which visualizations are affected, it is all of them as far as I can tell.  I tried line graph, map, and GIS map.  All with the same error.  

       

      Setup in Azure sends data to my "deviceData" dataset.  

       

      Visualizations are all affected by the change to "realTimeData"

       

      I can't change the historical data option to off.  I get this error.  

      • Anonymous's avatar
        Anonymous
        Not applicable

        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?

  • We have the same issue. Table named "Telemetry" in Stream Analytics, but when trying to use the dataset in Power BI online the name is changed to RealTimeData and you get error: "We are not able to identify the following fields: RealTimeData. Please update the visual with fields that exist in the dataset."

     

    If you connect to the dataset from Power BI Desktop the table name is correct and reports can be created successfully, but as soon as you publish the error pop up again.