cardinality for non aggregatable facts

[dssd]

i have a scenario where i have two queries in my report. the two queries seem to have a relationship of 1..n  but, the n side doesn't have any aggregatable fact...Does it make sense to have it as a n then. I ask this because the par ton the n is identified as a fact by the engine. Would the engine get confused

[bdbits]

So you have a factless fact table? Not as uncommon as you might think. You still want to identify it as 1..n so that other aggregations like count work properly. It is also very common to add an item with a value of 1 to the fact table, as it makes certain report calculations easier.