Forum Discussion

ConnieMaldonado's avatar
ConnieMaldonado
Responsive Resident
4 years ago
Solved

Data Modeling Best Practice: One column in a table?

Hello - I'm designing a data model for a field service project.  Although I use Power BI extensively and have been exposed to databases and models, it's my first go at designing one.  What can I say ...
Need Help
  • Weav8060's avatar
    Weav8060
    4 years ago

    absolutely ok to set up such a "dimension" table.  Additional columns may suggest themselves in due time for aspects associated with reasons.  They may be grouped for instance using the ad hoc grouping feature, or ordered using an Order ID column.  You may want to report quantities on all reasons, and so you need your master list of reasons.  Also if you have another employee table that makes sense not to consolidate with the main, you'll have a one-to-many relationship to both tables and key your filters to na_reasons

Weav8060's avatar
Weav8060
Frequent Visitor
4 years ago

absolutely ok to set up such a "dimension" table.  Additional columns may suggest themselves in due time for aspects associated with reasons.  They may be grouped for instance using the ad hoc grouping feature, or ordered using an Order ID column.  You may want to report quantities on all reasons, and so you need your master list of reasons.  Also if you have another employee table that makes sense not to consolidate with the main, you'll have a one-to-many relationship to both tables and key your filters to na_reasons