User Objects - Entering a Constant

[Snakeboy]

Hello, I hope someone can help...

I have created a User Object (in BO V4 - yes yes, I know!) as all I wanted to do was to enter a constant value of 3.72 (Ie the cost of another column's data). For this I simply entered the formulae as 'Absolute ( 3.72 )'.

I wanted to create it as a user object as then hopefully I would be able to SUM it for each broken group without much hassle. This appeared to work OK, however, for some random rows it appears to have doubled or tripled the value, for no apparent reason.

Also, when looking in the 'Filter' screen it doesnt seem to recognise the doubled/tripled values ie it only shows the value of 3.72.

Does anyone know why this occurs? - and how i can rectify it????

Confused?!!!!

Thanks in advance,

Steve

 

[blom0344]

The filter option is on the information in the datacube, NOT on the values displayed in a report. Furthermore a table displays unique combinations as a default and automatically aggregates measures when it uses 3 records from the datacube to display one row in a table.
What happens when you activate 'avoid duplicate rows aggregation' with the 'format table' option. Can you set it as a constant in the universe and set its aggregation behaviour to 'none'? T. Blom
Information analyst
tbl@shimano-eu.com

 

[Snakeboy]

Seems to have worked, thanks. Still a bit unsure as to why though.... can you explain this in baby lang for me? - not very bright see!!!! (-:

Thanks,

Steve

 

[blom0344]

Hello Steve,

Imagine 3 records in the dataset:

object1 object2
X 3.72
X 3.72
X 3.72

object1 is a dimension,
object2 is a measure.

If you build a table with this data and the aggregating behavior of object2 is set to sum, then:


X 11.06

BO automatically aggregates over object1 and shows one record.

Setting aggregating behavior to 'none' in the universe should get you:

X 3.72

And you probably end up with the following table-contents if you set the table property "avoid duplicate rows aggregation" on:

X 3.72
X 3.72
X 3.72


All these types of behavior are needed in order to work with automatic aggregating and drilling at reportlevel.

T. Blom
Information analyst
tbl@shimano-eu.com

 

[Snakeboy]

Ahhhh! Thanks.

Steve