Usage property behaviour

[khabaleshri]

If usage property set as attribute to Fact query item in FM then what will happen in Report studio? And if you don't have access on Framework manager then how will you tackle such behaviour in Report studio?

[MFGF]

If usage property set as attribute to Fact query item in FM then what will happen in Report studio? And if you don't have access on Framework manager then how will you tackle such behaviour in Report studio?

Setting an item to have a usage of Fact means that the item will be automatically aggregated when you use it in a report. If you have an item with a usage of Attribute, the query will attempt to deliver distinct values. You really need to fix things in your model to get anywhere easily in reports...

MF.

[khabaleshri]

Thanks for your quick reply but if I don't have access on Framework manager to change usage property as Fact then can I use cast function or other techniques to avoid distinct values in Report studio?

[MFGF]

Thanks for your quick reply but if I don't have access on Framework manager to change usage property as Fact then can I use cast function or other techniques to avoid distinct values in Report studio?

You could try setting the Detail Aggregate and Summary Aggregate properties to allow the value to aggregate in your report, but I suspect this sort of hack might lead you into trouble further down the line. The safe solution is to get the model changed.

Cheers!

MF.

[khabaleshri]

Thanks MF. Actually this was interview question. I know best practice is to change in FM model but interviewer need any possible solution in RS.