The current functionality does more harm than good. No one would publish a report unless the data is up to date (unless they forgot to refresh the data). To start another refresh, after publishing, puts an unnecessary load on the the source system(s) and the Power BI service. Especially with source systems where the connector does not perform well i.e. SAP BW
I know there is a work around i.e. turn off the scheduled refresh, then publish. However that is an unnecessary step and many organisations centralize/govern the task of enabling auto refresh. For those clients the work around is not really an option.
Also, this functionality was introduced in the last x-years (go back circa 3 years and datasets did not automatically refresh after it was published). So I assume it is not an architectural requirement but rather an enhancement that was implemented - thought to be a good idea.
on:
Feature Request: Python notebooks should support c...
on:
Replace All that are Not a Value
on:
Introducing Staging in Power Query: Smarter Valida...
SMATIN
on:
Support non-deterministic functions in scalar UDFs...