Decision Grain: la bussola nel caos dei dati
Decision Grain is the key!
Start here and you’ll avoid getting lost in complexity and complicated intersections.
When you integrate multiple sources the hardest part isn’t the API calls or the dashboards. It’s choosing the right grain.
The request: pulls data from ticketing platforms, project management systems, and HR tools and develop a “Simple Matrix” (Spoiler: date ranges and daily reports don’t speak the same language) in #PowerBI to visualize how people are allocated.
Yes but.. each source has a different level of detail!
- Project Management system: hours per project and day
- Ticketing platform: daily reports
- HR Tool: absences as date ranges (e.g., Aug 1–5)
Seriously, a date range? What did I ever do to deserve this in my life?
Btw the initial decision grain was Person x Day and that was my guiding spirit.
Expand each range into working-day rows and spread the minutes evenly (only as fallback) across those days, then join everything on a stable person key.
List.Dates([from],[to]-[from]+1,#duration(1,0,0,0))
The mess can be managed if you have a clear question to answer.
Curious about the full story? Link on the first comment
#PowerBI #PowerQuery #DataModeling #ResourcePlanning #PMO
