Query Dependencies View

[thakks]

query dependency skewed for query iterating tokenized or static page. Separate node for each iteration! Is this expected behaviour 

[Anonymous]

HI @thakks,

I test on my side and it works, which version of power bi you used? It will be help if you share the detail contents.

Regarcs,

XIaoxin Sheng

[thakks]

Hi @Anonymous

Say for example you scrapping the details form the web page and iterating through all the static or dynamic page to extract the details. To do this we will end up using List.Generate to traverse through the web page output in multiple pages. What Power BI is doing is that it shows all the iteration as a separate node in the query dependency. So if you iterating around 10 pages, it will show 10 seperate node on the query dependency and visually its wont be user friendly.

In the diagram below, it is showing https://graph.facebook.com from where i am extracting all the posts. The diagram is only for post published since 15 July and it has only one node for that query. 

Now the same query dependency will have node for a each page iterated by the query to extract the Facebook Posts. To me that doesn't really make the query plan user friendly, instead it should have , something like 1..10 to show 10 call made to that node to extract all the posts. So if i extract post that needs iterating two pages the query dependecies will have two node as shown below

 Now if i have a separate query to extract facebook metrics for each post, i will have a separate node on the query dependecies for each call made to facebook API. So for 1000 posts i will have 1000 node on the query plan, which wont make any sense.

[Anonymous]

HI @thakks,

>> Now if i have a separate query to extract facebook metrics for each post, i will have a separate node on the query dependecies for each call made to facebook API. So for 1000 posts i will have 1000 node on the query plan, which wont make any sense.

So you want to merge these similar node to a list to make view more humanize, right ?

If this is a case, current it not support this feature, I think you can submit an ideas about this requirement.

Regards,
Xiaoxin Sheng

[thakks]

Thanks @Anonymous . I have now raised the idea here