Forum Discussion
Unexpected Multiple Requests from Power BI Connector
Hey v-kpoloju-msft,
priorities shift at work this week, so I didn't have time yet to look into your suggestions. Hope I will find some time next week to look into Diagnostics.Cache.
Api.Folder doesn't look poosible at this point, but maybe later.
Disabling the preview didn't change anything for me regarding the number of requests. But since I already reduced requests at that point (and I don't have controll over everyone who uses the connector to turn that option off) I don't think that's helping.
Sorry again for the delay and thanks again for all the help and input!
Regards,
Scheißy
Hi everyone,
sorry for not getting back to you sooner, but a lack of time and results have prevented me from returning to this post until now.
Unfortunately, I have to say that I haven't found a solution that really works. For a single table, I consistently get two requests per file, but as soon as I select a second file (or table), Power BI seems to get confused and, depending on its mood, requires between one and four requests. Very frustrating.
Here is a brief overview (to name a few buzz words) of everything I've tried:
- Better error handling to avoid cascading retries
- List.Buffer
- Buffer results to prevent re-execution
- Buffering the nav table
- Strict sequential processing with List.Accumulate()
- Minimize variable management
- Shift from lazy loading to eager loading with caching
- Manual status handling
- Control retry behavior
- Removed resource parameter
- Removed manual caching wrappers
- Removed debugging
Long story short: looks like we will try to cache the result on the API side. This does not reduce the number of requests, but at least reduces their impact.
Thanks again to everyone who contributed their two cents!