Holistics doesn’t currently have the capability to deal with fanouts on measures when used with 1-N model relationships. However, at least if we define metrics with type count distinct, max, min etc the fanout problem is ignored and the query returns OK.
Sometimes, these measures are then used in other measures (e.g. [count distinct x] / [count distinct y]). However the results are not returned, due to a fanout warning, when actually there is no risk of fanout.
It would be helpful to return the value rather than an error.