Forum Discussion
Changing from a dynamic to a fixed data source
Hi JJS8080 ,
If you're still seeing a dynamic data source even after trying the previous suggestions, that means Power BI is detecting a fully constructed URL somewhere in the query. Power BI will always block scheduled refresh when any Web.Contents call uses a dynamically-built URL string.
Try to rewrite your paging function so that every Web.Contents call uses this structure:Web.Contents(
"https://api.aircall.io",
[
RelativePath = "v1/calls",
Query = [
per_page = "50",
page = PageNumber,
from = FromUnix,
to = ToUnix
],
Headers = [ Authorization = encodedAuth ]
])
No concatenated strings.
No full URLs.
No manually built "https://api.aircall.io/v1/calls?...“.
Once the paging logic is rewritten using RelativePath + Query only, your dataset will become refreshable in the Power BI Service.
Hope this helps.
Thank you.
Hey, tried both methods but didnt get the result I wanted as still ended up being a dynamic data source.
Hi JJS8080 ,
If you're still seeing a dynamic data source even after trying the previous suggestions, that means Power BI is detecting a fully constructed URL somewhere in the query. Power BI will always block scheduled refresh when any Web.Contents call uses a dynamically-built URL string.
Try to rewrite your paging function so that every Web.Contents call uses this structure:
Web.Contents(
"https://api.aircall.io",
[
RelativePath = "v1/calls",
Query = [
per_page = "50",
page = PageNumber,
from = FromUnix,
to = ToUnix
],
Headers = [ Authorization = encodedAuth ]
])
No concatenated strings.
No full URLs.
No manually built "https://api.aircall.io/v1/calls?...“.
Once the paging logic is rewritten using RelativePath + Query only, your dataset will become refreshable in the Power BI Service.
Hope this helps.
Thank you.
Thanks for the help, Issue is now fixed