Hello,
In my opinion Power BI is a tool to steer and/or analyze you business.
Analysis depends from which perspective(s) the end-user looks at his business.
If you ask the user if he also wants detail transactions, sometimes he says 'Yes'.
OK, but why do you need them? Answers may be different, sometimes for incident management. Which in my eyes you should not use Power BI for (better use some operational tool).
I am always a little bit reluctant in also embedding all the detail transactions in an Import dataset. We have tables with million of records, some with a billion a year. Why am I reluctant?
- Import dataset might become too big?? (We have premium capacity)
- Maybe I need to create a composite model with it's advantages but also disadvantages
- How often do they really use the details?
How are other people doing this? Are you also struggling with this?
Or should you, when the ultimate future goal is self service BI, just dump everything in a shared dataset?
Another question:
Sometimes you see that people build some kind of a search function in a Power BI report. You can type in an account number or so and then you get a list of transactions. Isn't this more functionality for paginated reports?
Regards
Ron
