Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
3 years ago

Clusterd comun chart not showing correct data

Hello community, I am posting an issue I've encountered while showing data coming from a Streaming dataset displayed in my Dashboard. In the screenshot attached you can see how the highlighted date...
Need Help
Anonymous's avatar
Anonymous
Not applicable
3 years ago

Hello lbendlin ,
thanks for your reply.
Yes, in the API definistion of my Streaming Dataset, both "subscribed" and "unsubscribed" fields defined, but only one at the time will be sent.
Example:

[
{
"subscribed": 23,
"experimentName": "uniqueness_9ZVHo",
"time": "2022-09-28T22:00:00.000Z"
 },
 {
"unsubscribed": "2",
"experimentName": "uniqueness_KxgcX",
"time": "2022-09-28T22:00:00.000Z"
 },
...
]


Here a screenshot on how my Streaming Dataset is configured:

lbendlin's avatar
lbendlin
Icon for Super User rankSuper User
3 years ago

Keep in mind that the Power BI service runs on Zulu time (UTC) . Maybe your event got shifted to another day based on your viewer timezone.

  • Anonymous's avatar
    Anonymous
    Not applicable
    3 years ago

    Hello lbendlin,
    I do not think that the timezone can be the cause in the issue I am describing because the difference in time between the data sent and the graph is of days.
    So, I am positive that the data above it's what I am sending to PowerBi but I am not able to see/debug what the Streaming Dataset is reiceving/interpreting. Do you know if there is a way to do that in PowerBi?

    • lbendlin's avatar
      lbendlin
      Icon for Super User rankSuper User
      3 years ago

      You can use PowerShell or Postman to push rows manually and observe if they have been added to the dataset.

       

      I assume you have history enabled?

      • Anonymous's avatar
        Anonymous
        Not applicable
        3 years ago

        Yes, using cUrl requests still produce the same outcome: data sent in are not correctly shown (as per date, not per value).
        History is not enabled, we are pushing historical data up to 6months prior, which is making the history functionality not really needed