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.
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 .OK, thanks.
"never intended": I can indeed imagine and even undestand such answer to a degree. Since power m is not a sequential interpreted language, I can only guess the complexity behind the scenes to optimise the queries like power bi does.
In any case, looks like waiting for a solution for that recursive seems a long term thing at the best.
So I'm going to look to rewrite the code with some form of iterator. I used the recursive call because this was advised in some other forum topic. But a search reveils there is also a "for list" iterator. So I'll dig into and analyse that alternative for a recursive call.
thx for your clear answers
Read Ben Gribaudo's Primer. He specifically mentions the complexities and design limitations. In the vast majority of cases an iterator is preferable to a recursion, especially when large amounts of data are involved.