Skip to content

Commit 6e48349

Browse files
authored
cleaning
1 parent b144326 commit 6e48349

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

Workloads-Specific/PowerBi/BestPractices.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -136,32 +136,31 @@ From [Understand star schema and the importance for Power BI](https://learn.micr
136136

137137
> Enhance report responsiveness and reduce resource load by optimizing visuals and query performance.
138138
139-
| **Best Practice** | **Description** | **Example** |
140-
|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
139+
| **Best Practice** | **Description** | **Example** |
140+
|---------------------------------------|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
141141
| **Optimize Visuals and Interactions** | Limit the number of visuals per report page and simplify complex interactions to improve performance. | Use [Optimize ribbon in Power BI Desktop](https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-optimize-ribbon) to pause visuals and control query execution during design. |
142142
| **DirectQuery Optimization** | Use features from the Optimize ribbon to streamline DirectQuery interactions and reduce redundant queries. | Follow methods in [DirectQuery optimization scenarios with the Optimize ribbon in Power BI Desktop](https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-optimize-ribbon-scenarios) to adjust visual refresh behavior. |
143143

144144
## Documentation and Maintenance
145145

146146
> Keep your reports self-explanatory and maintain a centralized repository for ongoing support and future enhancements.
147147
148-
| **Best Practice** | **Description** | **Example** |
149-
|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
148+
| **Best Practice** | **Description** | **Example**|
149+
|---------------------------------------|-----------------------------------------------------------|--------------------|
150150
| **In-Report Annotations** | Use text boxes, tooltips, and in-report comments to document data sources, transformations, and calculation logic. | Include explanatory notes within report pages as encouraged in the [Power BI guidance documentation](https://learn.microsoft.com/en-us/power-bi/guidance/). |
151151
| **Scheduled Reviews and Updates** | Periodically review report performance, refresh schedules, and security settings to keep the solution optimized and current. | Adopt a routine review cycle based on feedback and usage metrics provided by Power BI service administration tools. |
152-
| **Centralized Repository** | Store and version-control all project artifacts (PBIX files, change logs, documentation) in a secure repository. | Use Azure DevOps or another Git-based repository, following the practices laid out in the source control sections above.
152+
| **Centralized Repository** | Store and version-control all project artifacts (PBIX files, change logs, documentation) in a secure repository. | Use Azure DevOps or another Git-based repository, following the practices laid out in the source control sections above. |
153153

154154
## Deploying Reports with DevOps Best Practices
155155

156156
> Automate and streamline deployment processes using CI/CD pipelines integrated within your Power BI environment.
157157
158-
| **Best Practice** | **Description** | **Example** |
159-
|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
158+
| **Best Practice** | **Description** | **Example**|
159+
|---------------------------------------|------------------------------------------------------------|---------------------------------|
160160
| **Automated Build Pipelines** | Integrate Git repositories with Azure DevOps to automatically validate and deploy Power BI content. | Refer to [Azure DevOps build pipeline integration with Power BI Desktop projects](https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-build-pipelines) for guidance. |
161161
| **Deployment Pipelines via APIs** | Use the Power BI deployment pipelines APIs to automate report deployment steps and ensure quality across environments. | Implement automated deployments as described in [Automate deployment pipelines with APIs for Power BI items](https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/pipeline-automation). |
162162
| **Continuous Integration** | Incorporate quality gates and automated testing within your CI/CD process to catch issues early in the development cycle. | Utilize Git-based integration and automated tests as shown in [Power BI Desktop projects Azure DevOps integration](https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-azdo) for best practices. |
163163

164-
165164
<div align="center">
166165
<h3 style="color: #4CAF50;">Total Visitors</h3>
167166
<img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>

0 commit comments

Comments
 (0)