Power BI real-time dashboard tiles - Historic Data

[vhello]

I've been trying out the new Real Time dashboard tiles with Streaming Dataset

In my personal space I can see that 1 mb is used in each of my streaming dataset.

However I'm noticing my new telemetry is not being saved in the Historic Data.

From my Streaming Dataset, I selected "Create Report" action.

This will take me to the report page with the data. However by looking at the data I've been missing weeks of testing data.

I've pushed some data today and I can see the visuals update on in the dashboard.

But my report data from historic data is still not up to date. It's showing data up to 8/23.

Any ideas?

Thanks

-Helen

[sirui_sun]

Hello - 

Happy to help. First, let me make sure I understand the problem. Can you confirm that the following is true:

• A while back, you created a streaming dataset via API option, and enabled historic analysis
• You've been sending data to this streaming dataset over the past few weeks
• Today, when you push data, the visuals on your dashboard do update
• However, when you go to build a report, you don't see any data since 8/23

[vhello]

- A while back, you created a streaming dataset via API option, and enabled historic analysis

  Yes
- You've been sending data to this streaming dataset over the past few weeks

  I've been sending data on and off but not continuously
- Today, when you push data, the visuals on your dashboard do update

  Yes
- However, when you go to build a report, you don't see any data since 8/23

  Yes

[vhello · Accepted solution]

After support I've found the issue:

Looks like I pushed extra column data that is not specified in the Power BI Streaming Data.

eg.,

[{"device_type":"thermoMeter","DataTimestamp":"9/12/2016 5:14:42 PM","mac_address":"Thermal_Simulator","Temperature":200,"Humidity":446}]

"device_type" isn't on my Streaming Data table since I didn't need it in the Power BI side.

This will give an error when Power BI inserts the row.

Either add the column to the table or remove device_type value to fix this.

Thanks for great support 🙂

-Helen