Power BI Environment Comparison
Budget: £20 – £80 GBP
I need an interactive Power BI report that compares our Development and Testing environments for every solution we run. The only KPI that really matters right now is the version number, so the visuals have to make any mismatch immediately obvious.
Data will come from our configuration tables in SQL Server, with a small Excel lookup for friendly solution names. A lean star schema—one fact table with environment-solution-version records plus simple dimension tables—should keep refresh times tight. Feel free to use Power Query, DAX, and any native visuals; a matrix with conditional formatting or a custom KPI visual works as long as discrepancies jump out at first glance.
Key requirements
• Slicers for environment (Development, Testing) and solution name.
• Side-by-side view showing the version running in each environment.
• Colour-coded or icon-based alert when versions differ.
• Drill-through or tooltips displaying deployment date and owner pulled from the same source.
Deliverables
• .pbix file with all queries, parameters, and DAX comments.
• Short README explaining where to update connection strings.
• Screenshot demonstrating the alert changing when sample data is edited.
Acceptance criteria
1. Switching the connection string refreshes the report without errors.
2. Matching versions show green; mismatched versions show red.
3. Performance Analyzer reports under two seconds per visual on a 10k-row test set.
That’s the full scope—once the report meets the above points, the task is complete.
Data will come from our configuration tables in SQL Server, with a small Excel lookup for friendly solution names. A lean star schema—one fact table with environment-solution-version records plus simple dimension tables—should keep refresh times tight. Feel free to use Power Query, DAX, and any native visuals; a matrix with conditional formatting or a custom KPI visual works as long as discrepancies jump out at first glance.
Key requirements
• Slicers for environment (Development, Testing) and solution name.
• Side-by-side view showing the version running in each environment.
• Colour-coded or icon-based alert when versions differ.
• Drill-through or tooltips displaying deployment date and owner pulled from the same source.
Deliverables
• .pbix file with all queries, parameters, and DAX comments.
• Short README explaining where to update connection strings.
• Screenshot demonstrating the alert changing when sample data is edited.
Acceptance criteria
1. Switching the connection string refreshes the report without errors.
2. Matching versions show green; mismatched versions show red.
3. Performance Analyzer reports under two seconds per visual on a 10k-row test set.
That’s the full scope—once the report meets the above points, the task is complete.