Question regarding semantic model design. Fact table as a dimension?
I work for a staffing company. When a client wants our services, we create one or multiple projects in our system. Each can contain at most one staffer at a time and they pay us on a monthly basis. Is the project table a fact or a dimension why?
I think they are facts, but my issue is that there are other tables related to projects, such as project revenue, project resource lines, and so on. My draft design is this:
This seems to work, but Copolit hates it. It says a fact table should never be used as a dimension and this doesn't resembles a star schema design. I see the argument, but whats the alternative? Copilot suggest separating the project table into 2 with facts and dimmensions. This seems so unnecesary, I don't see how this would even work. Thoughts? If someone has an example from an article/book that addresses this scenario I would love to read it. Thanks!
Posted Mar 6, 2026, 3:49 PM UTC