Streaming job analytics input and output not show in PowerBI

Hi Team

Can any mate help with the following sql query for consuming an output to my power bi desktop. I am unable to get an input and output both on my azure portal and power bi desktop dataset. What am missing? Kindly please assist as i sat with the problem close to a day now, i saw this example with fraudelence for using stream analytics job to connect to power bi dataset.

--Our criteria for fraud:
--Calls made from the same caller to two phone switches in different locations (for example, Australia and Europe) within five seconds
SELECT System.Timestamp AS WindowEnd, COUNT(*) AS eNtsaACT083(MyStream-Analytics-Job)
INTO "PBIOuput"(Output-Job-Stream).
FROM "PBIEventHub"(Input-Job-Stream) CS1 TIMESTAMP BY CallRecTime
JOIN "PBIEventHub" CS2 TIMESTAMP BY CallRecTime
--Where the caller is the same, as indicated by IMSI (International Mobile Subscriber Identity)
ON CS1.CallingIMSI = CS2.CallingIMSI
-- ...and date between CS1 and CS2 is between one and five seconds
AND DATEDIFF(ss, CS1, CS2) BETWEEN 1 AND 5
-- Where the switch location is different
WHERE CS1.SwitchNum != CS2.SwitchNum
GROUP BY TumblingWindow(Duration(second, 1))

What am i missing had follow this link to that; Please help me team

https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/stream-analytics/stream-analytics-power-bi-dashboard.md

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Guest User7y ago
Hi Team

Just for the feedback, the issue was not on azure sql database script, rather on the naming conversion its when calling a streaming analytic job. It should be exactly the same name when specify your deviceID. I think its a rule when dealing with authentication type. i was using self assigned not asymetric key. Lesson learnt, thanks team anyway i learnt something along the way.
Guest User7y ago
This is what i meant from above and my dataset on power bi desktop is not shown; what could be the reason? please assist me team, i am stuck to this issue close to a day now.