Best Practices Data Modelling- Using the same source data for multiple dimensions

federerman — Wed, 17 Apr 2019 21:48:32 GMT

What are the best practices when creating a model that uses the same source data for multiple dimensions?

In particular, let’s say I have an Issue tracking system. An issue belongs to a particular Project (BI, Data, etc.). An issue is Reported by an employee. The issue is then Assigned to an employee. Hours worked are then tracked to this issue. The traditional data model looks like this:

Note that this model requires employee source data be read twice. Though it is makes charts like this very straightforward:

But, what if I want to create a table that shows number of issues assigned/reported to each employee and the hours spend on assigned and reported issues. Maybe even include some comparison metrics. See example table below:

Given this data model, there is no way to contract this table. I was only able to create this chart using a heavily altered data model that makes other forms of analysis a pain.

Can a model be created where that allows all three charts to be created (A, B, C)?

See attached QVFs:

Re: Best Practices Data Modelling- Using the same source data for multiple dimensions

federerman — Wed, 17 Apr 2019 21:57:50 GMT

Couldn't find a way to edit post. Looks like the screenshots didn't make it in the right order.

For reference, charts A/B/C should be these images:

topic Re: Best Practices Data Modelling- Using the same source data for multiple dimensions in App Development

Best Practices Data Modelling- Using the same source data for multiple dimensions

Re: Best Practices Data Modelling- Using the same source data for multiple dimensions