Football Project: Publish & Refresh

Key insights

• Power BI Service: Publish your updated report to the service and enable a scheduled refresh so the dataset updates automatically on a regular cadence.
  Set the refresh frequency and time window in the dataset settings to match your reporting needs.
• API calls: Change your queries so the web API endpoints and authentication methods support background refresh in Power BI (avoid ephemeral tokens in URLs).
  Bring API headers and auth into Power Query or use service-supported authentication flows so refreshes run without manual steps.
• Parameters: Build parameters for season and competition values inside Power BI so you can switch contexts quickly without editing queries.
  Expose those parameters in the service (dataset parameters) to change seasons or competitions without republishing the PBIX.
• Dataset credentials and On-premises data gateway: Configure dataset credentials in the Power BI service and install or map an on-premises gateway if your API or data source sits behind a firewall.
  Ensure the gateway and credentials are valid so scheduled refreshes succeed.
• PBIX files: Use the provided PBIX examples to follow the same steps locally: update parameters, test refresh, then republish to the service.
  This helps reproduce the setup and speeds troubleshooting.
• Best practices & troubleshooting: Run a manual refresh to confirm success, check refresh history for errors, and monitor API rate limits and error messages.
  Use incremental refresh for large tables and add logging or retry logic in queries to handle intermittent API failures.

Video overview and context

Curbal published a practical walkthrough titled "FOOTBALL PROJECT #11: Publish and schedule refresh" that focuses on getting a Power BI report from desktop into the Power BI service and keeping it up to date. The video frames a small football dataset and explains how to adjust API calls so that the dataset refreshes reliably in the cloud. Additionally, the author highlights the use of parameters to switch seasons and competitions quickly without rebuilding the report each time. As a result, viewers gain a hands-on tutorial rather than a purely conceptual talk.

The creator also points viewers to downloadable report files and supporting material, which helps replicate the steps shown. Meanwhile, the video emphasizes practical configuration rather than only theory, so users can follow along and test changes. Consequently, the guide serves both learners and working analysts who need a repeatable publish-and-refresh workflow. Overall, the episode fits within a larger series that explores Power BI for sports analytics.

Publish and scheduled refresh explained

In the video, Curbal demonstrates how to publish a .pbix file to the service and configure a scheduled refresh so that data stays current. She walks through dataset settings, authentication choices, and the timing of refreshes, explaining why each step matters for maintainability. Furthermore, the walkthrough clarifies how the service interacts with external APIs and when a gateway is required. Therefore, viewers can see the full path from a local report to an automated cloud refresh.

The author also outlines how refresh failures often point to credential, privacy or API limits rather than the report logic itself. For that reason, she recommends testing the API calls in isolation before relying on the scheduled job. However, she notes that the Power BI service will respect API rate limits and that you may need to throttle refreshes or move to incremental strategies. Thus, the publish flow includes both technical steps and operational checks to reduce surprises.

Using parameters to switch seasons and competitions

A key point in the video is the use of parameters to let users change the season or competition without editing the dataset each time. By wiring these parameters into the API query stage, the report can fetch different slices of data on demand and during scheduled refreshes. This approach speeds up testing and supports multiple views of the same model, which is particularly useful for recurring sports analyses. As a result, parameters make the solution more flexible and reusable.

At the same time, the author warns about tradeoffs: adding parameters can complicate caching and may affect refresh performance if each parameter change triggers large API calls. Additionally, parameter values that require user input create governance questions, since they may demand secure storage or careful handling of credentials. Therefore, while parameters offer convenience, teams must balance flexibility with predictable performance and administrative control.

Technical tradeoffs and performance considerations

The video compares different refresh strategies and discusses the typical tradeoffs between using Import mode, DirectQuery, and incremental refresh. Import mode often gives faster reports but requires more frequent dataset refreshes, while DirectQuery reduces data movement yet can lead to slower visuals and depends on live API responsiveness. Meanwhile, incremental refresh can reduce load by updating only recent data, but it demands appropriately designed time attributes and careful API support. Hence, each method brings pros and cons depending on dataset size and refresh windows.

Moreover, Curbal touches on service limits and the benefits of capacity tiers: higher capacities reduce the risk of throttling and allow more frequent refresh schedules. Nevertheless, moving to a paid capacity has cost implications and governance requirements that teams must weigh. Consequently, organizations should evaluate their data volume, expected refresh cadence, and budget to choose the right mix of modes and scaling options.

Implementation challenges and best practices

The video does not shy away from common pitfalls such as broken credentials, inconsistent API responses, and complex query folding that prevents efficient refreshes. To address these issues, the presenter recommends validating API responses, testing parameterized calls, and monitoring refresh logs after publishing. Additionally, she suggests setting sensible refresh windows and alerting so stakeholders know when automated processes fail. This combination of checks minimizes downtime and helps teams act quickly when problems arise.

Finally, Curbal emphasizes documentation and repeatability: keep a clear changelog for API changes, document parameter meanings, and store secrets securely. In large projects, these practices reduce handover friction and improve long-term maintainability. Overall, the video offers a balanced view that combines hands-on steps with operational advice, allowing analysts to build a reliable publish-and-refresh pipeline while understanding the tradeoffs involved.

• Topics covered in the video include DAX techniques, beginner dashboards, tips and tricks for Power BI, and connecting Power BI to analytics sources.

Keywords

football project publish and schedule refresh, publish and schedule refresh tutorial, Power BI football project publish, Power BI scheduled refresh guide, schedule dataset refresh Power BI, publish dashboard tutorial football analytics, automate data refresh Power BI, football analytics dashboard publish