Forum Discussion
Advice on table structure and modelling
Hello -
I wonder if I could run something by the community. I am trying to create a report based on project outcomes across a whole service (11 projects).
The problem I have is the source database captures these outcomes as date columns and all in seperate (project specific) tables. Further, some of the outcomes will be equivalent between two project tables.
I want to simplify this structure to allow me to visualise across the whole service of 11 project and to show / count outcomes that are equivalent the same way.
Find an example below of the table structure including two of these Outcome tables (linked to client).
My idea was that I create one big union table from all these individual outcome tables and map each outcome into the reduced list of total outcomes possible. However, this will be hard to update/maintain so i wondered if there were any other ideas on how to report across the whole structure of different project outcomes?
Any advice would be greatly appreciated!
Thanks
2 Replies
- AnonymousNot applicable
Just adding an additional thought to this. I think we will use categories to break down the list of outcomes. However, I think these are likely to change as as well as new outcomes come in. So i suppose the solution i go for would have to have that flexibility.
Thanks
- AnonymousNot applicable
Hi Anonymous ,
It seems that you want to make some adjustments to your existing data model. Could you please tell us what the final result you want is with more details first? We need to give suggestions or methods suitable for your scenario based on your needs. Here are some good documentations that may help you.
Optimization guide for Power BI (Data reduction techniques for Import modeling)
Optimizing models for reporting
Best Regards
Rena