Forum Discussion
Helper IMany-to-many dimension - blank row behavior
A good rule of thumb is to avoid many to many relationships and BOTH cross filter direction.
Can you share some details on your your dimensions and fact table and se if we can model it differently?
Helper IThe topic of the fact table are picking tasks in a warehouse, and the dimension tables holds so-called service codes. These are codes that specify what additional VAS (value added services - things like labeling, repacking, ..) need to be applied. Most warehouse tasks have no services, some have one service and some have multiple services. Conceptually, I feel the modelling question is similar to applying tags to eg emails, where you can have emails that have no tag, one tag or multiple tags (eg categories in Outlook), resulting in a many-to-many relation from the table with the tags to the table with the emails.