Forum Discussion
Circular Query
I get the below message when looking at the data model on power bi service. It doesn't show up on desktop version. is there an way to identifiy exactly what it's refering to so I could fix?
Circular query chain present. Member name= Parameter4. Index = 383
Thanks,
I encountered the same error and resolved it by adjusting my parameters. Initially, my parameter was designed to either pull in the top 10,000 rows or display the table name. I did this to reduce the table sizes. I corrected this by changing the parameter to point directly to the source instead of the table name. After republishing and refreshing, the error disappeared. I hope this helps someone.
My pleasure.
In fact, I wasn't sure why you didn't do it .. matter of checking my willingness to search or forum policy or ..
Anyway: this is the part of his primer dealing with 'control structure' in power query
https://bengribaudo.com/blog/2020/01/06/4844/power-query-m-primer-part14-control-structure
Cheers,
C.
16 Replies
That's a new one.
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .Thanks i have raised a ticket so will see what they say
Hey were you able to solve it?
not yet still have a ticket open with support
I encountered the same error and resolved it by adjusting my parameters. Initially, my parameter was designed to either pull in the top 10,000 rows or display the table name. I did this to reduce the table sizes. I corrected this by changing the parameter to point directly to the source instead of the table name. After republishing and refreshing, the error disappeared. I hope this helps someone.
Thanks I did managed to resolve in the end. It was the parameters that were auto generated from connecting to an excel online in the past. I removed all the sample files/paratmeter bits and reconnected the affected tables which fixed.
For me I have the same problem, but I can't get it solved.
In my case the query / function is indeed recursive on purpose. A single DB API call is limited in number of records to lets say 1000. So when I call the function, it always asks for max 1000 to the DB API, and then the rest is called from a recursive call with record 1000/2000/3000.... as starting point.
This works perfectly in Desktop.
But now when published to the service I get this error message.
Any idea?
what error message?
