Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
I'm trying to recreate in dataflows some PQ processes I have in Excel and Power BI, and am suprised by the fact using an M function (e.g. a call to a REST API) is bringing up a reference to "computed entities", which are limited to Power BI Premium.
The same function can be called and refreshed on a regular Power BI Pro dataset, why would using M functions in Dataflows be limited to Premium?! I'm not trying to calculate aggregations here, I'm just automating API calls.
Also, even though the function (creating by pasting M code in a blank query) seems to be recognized as such at creation:
It is then automatically turned into a table. Are functions even supported in Dataflows at the moment? I really want to love dataflows but the beta experience has been pretty rough so far.
Here's my function just for reference:
let ReturnDetails = (placeid as text) => Json.Document(Web.Contents("https://maps.googleapis.com/maps/api/place/details/json?placeid=" & placeid & "&fields=website,formatted_phone_number,url,rating&language=en-Au®ion=au&key=xyz")) in ReturnDetails
Solved! Go to Solution.
Hi @otravers
What you need to do, is to disable the loading of your function.
Here is a great blog post explaining how to fix it and why it happens.
https://ssbipolar.com/2018/11/23/power-bi-dataflows-reuse-without-premium/
The actual issue is that PowerBI Data Flow cannot handle variables in the url argument. If you place the variables to another argument of the Web.Contents() function, there are no issues:
let ReturnDetails = (placeid as text) => Json.Document(Web.Contents("https://maps.googleapis.com/maps/api/place/details/",[RelativePath="json?placeid=" & placeid & "&fields=website,formatted_phone_number,url,rating&language=en-Au®ion=au&key=xyz"])) in ReturnDetails