Forum Discussion
Circular Query
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.
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.
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?
Actual error message in Service:
getTEobjects is one of those function query's using this recursive mechanism
If this behaves differently on the desktop and the service you can raise it as a bug. Do not be surprised when they tell you that it should never have worked on the desktop either.
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 .
