Power BI reports that use queries with variable data sources, to be refreshable in Power BI Service

[ChrisD_UK]

Provide the ability to generate the physical name of a data source from another query ('late bound' in programming-speak), and still be able to refresh the report in Power BI Service.  Currently, this falls foul of the 'hand-authored queries' restriction.  Once published in Power BI Service, the 'refresh' detail has a exclamation mark next to it.  Presumably this relates directly to the above message shown in Power BI Desktop's 'Data Sources' dialogue prior to publishing.

This request particularly relates to 'Web' data sources, in the context of a web-scraping exercise where URLs from an initially-queried page need to feed the data sources of other queries.  This is the Use Case where it feels to be most difficult / impossible to work around the issue.  If this goes beyond the extent to which Power BI should incorporate web-scaping functionality, would it be possible to integrate with a specialist product to achieve the same result?

My specific Use Case:

At a stage in my transformation in Power Query, I have a list of web pages that can't be determined before the refresh, i.e. the list is created from previous query steps.  I have developed a query and a function to walk through the URL list and grab data the relevant HTML tags and elements on each page.  This works fine in Desktop but when I publish to Power BI Service, the report won't refresh.  This will be because the query I've developed is identified as a hand-authored query.  Here's a link to a simplified example that illustrates the problem.

https://www.dropbox.com/scl/fi/wlqge60vz17cfrlsr8qdi/Listed-Web-Page-Data.pbix?rlkey=fsideafc4g00vgu...

Raised as recommended by @tayloramy and @v-menakakota 

[Khashayar]

This is an excellent and well-articulated request. It highlights one of the key limitations when dealing with dynamic or late-bound data sources in Power BI, especially in web-scraping or API-chaining scenarios. The current restriction on “hand-authored queries” does make it difficult to build flexible, data-driven connection logic that works seamlessly both in Desktop and the Power BI Service. It would be extremely valuable if Microsoft could enable a controlled way to parameterize or dynamically generate data source references while still maintaining the security and governance standards of the Power BI Service. Even partial support—such as allowing “certified dynamic sources” or integration with trusted external data transformation tools—would greatly enhance advanced use cases like yours. Thank you for sharing your example; it perfectly illustrates a real-world need many advanced users encounter. Hopefully, this request gains more attention and leads to a practical enhancement in Power BI’s data connectivity model.