Forum Discussion
Helper IUsing inactive relationship in visuals
Community ChampionStel In general I agree with Anonymous , that model is uh, uh, ugly. Seems like you have a number of fact tables related to orders. I would assume that there should be some common id between them like order id. So, you might consider having a distinct list of order id's in a separate dimension table that you could use to tie all of them together. You can create this in Power Query or in DAX it is Table = DISTINCT('Table'[Order ID]) for example.
You can use inactive relationships in measure calculations by using the USERELATIONSHIP function in DAX but if you find yourself having to do that, 99 times out of 100 you have a flaw in your data model. Not always, but generally.
Helper IHi,
I did what you suggested. Hope this makes it less ugly 🙂
Maybe to give you more context: the fact_picking table actually holds data about who has picked what article from which location, from which pallet, to which location and to which pallet. You may call it the actual picking trace
The fact_outboundorder table contains who is the customer, what did he order. Like 1 orderline of 10 items can result in 5 fact_picking lines when an employee, picks 5x2 pieces of the product
I get the point that I should use a star diagram and not connect 2 fact tables.
But now I want for my actual pick traces, slicing on customer. Currently I only have a reference of the customer in my fact_outboundorder table.
Greg_Deckler , v-kelly-msft What is the best way to do that?
I've tried with a dim_outboundorder table as suggested to connect the 2 fact_tables but it's not working.
Thanks in advance.