50 lines
3.3 KiB
Markdown
50 lines
3.3 KiB
Markdown
|
# 20250122-01 - Power BI Main Guest KPIs Bug
|
|||
|
|
|
|||
|
|
This page is to report a bug noted on the Main Guest KPIs report in Power BI noted on the 2025-01-21, 16:00 ES Time. The bug was then fixed on 2025-01-23
|
|||
|
|
|
|||
|
|
## Summary
|
|||
|
|
|
|||
|
|
- Due to some formulas used on Power BI during the creation of the report, which were working correctly at the time of release, stopped working properly. Although we are not sure exactly when this happened it couldn’t have been many days earlier since Joaquin had checked on the report the week before and we know that Joan usually checks that report regularly.
|
|||
|
|
- This problem with the formulas only happens when the report is on the server, when working locally on the report all was working perfectly fine as it was previously.
|
|||
|
|
- Once I (Joaquin) noted which were the formulas that were generating problems I found a workaround to replace those visualizations that had the formula problem.
|
|||
|
|
|
|||
|
|
## Impact
|
|||
|
|
|
|||
|
|
Uri reported this issue after a meeting with Kayla where he was showing an example of our Main KPIs reports so we could extend this to the Accounting Managing team.
|
|||
|
|
|
|||
|
|
Fortunately the impact wasn’t in the entire report but only some particular visuals focused on the CSAT Score which we have in a separate report as well if any user had any urgent need of it.
|
|||
|
|
|
|||
|
|
## Timeline
|
|||
|
|
|
|||
|
|
| Time | Event |
|
|||
|
|
| --- | --- |
|
|||
|
|
| 2025-01-22 16:00 | Uri reported this bug after a meeting with Kayla displaying the report. |
|
|||
|
|
| 2025-01-22 16:30 | Uri notified me (Joaquin) about the bug so he could that a look at what could the problem be. |
|
|||
|
|
| 2025-01-22 09:00 | Together with Uri we tried to understand the problem once we noted that locally the report was working perfectly fine and tried to do some troubleshooting on the PBI server to find the root problem. Unfortunately the details PBI gives on any issues are not very clear so this effort wasn’t really fructuous. |
|
|||
|
|
| 2025-01-22 11:00 | After multiple failed attempts of trying to fix the bug reuploading the report, I started going into detail to find the problem. I realized that there was a formula that was causing the problem (WEEKNUM gives the number of the week on the year). |
|
|||
|
|
| 2025-01-23 09:00 | I changed the measure using WEEKNUM and reuploaded the report now working correctly. |
|
|||
|
|
|
|||
|
|
## Root Cause(s)
|
|||
|
|
|
|||
|
|
We don’t know for sure since there weren’t any changes from our side that could have affected the report. We believe it was mainly a problem from the server in PBI or a bugged update from them that generated this issue.
|
|||
|
|
|
|||
|
|
## Resolution and recovery
|
|||
|
|
|
|||
|
|
- We noted the problem before any user so we had enough time to fix it before anybody was affected by it.
|
|||
|
|
- The good thing is it was only a small part of the report that wasn’t working and that data is available in another report in case of emergency.
|
|||
|
|
- We managed to fix the problem relatively quickly once we found where the problem was with a workaround so now the report is working perfectly.
|
|||
|
|
|
|||
|
|
## **Lessons Learned**
|
|||
|
|
|
|||
|
|
- What went well
|
|||
|
|
- Good communication within the team to pick up the problem
|
|||
|
|
- What went badly
|
|||
|
|
- Trying to really understand what the root problem was, the troubleshooting with PBI is not user friendly
|
|||
|
|
|
|||
|
|
General lesson:
|
|||
|
|
|
|||
|
|
Whenever possible try to do all calculations within DWH models so there are no created measures or the least possible amount in the PBI report. This will help mitigate problems like this.
|
|||
|
|
|
|||
|
|
## Action Items
|
|||
|
|
|
|||
|
|
## Appendix
|