BO4 - universe object datatype change affecting pre-existing reports with filters on this object

[former_member272336]

Hi,

version using BO4.2 SP05

We have noticed web intelligence wasn't allowing merging of dimensions of different datatype so we changed one of the datatypes in the universe (.unv) from character to number to allow this. - data is all numeric.

However, pre-existing reports which used filtered data displayed based on this object stopped displaying data and had to reapply the filter to get it to work correctly.

It looks like you have to reapply report-level filters any time you change datatype of universe object. Wouldn't have expected this as means would have to freeze datatype of object in such cases.

Have checked sap knowlege base and searched this forum but can't find anything similar.

Anybody seen similar and know if this is a known issue?

In the meantime, we have had to change the datatype of this object back to character so as not to affect pre-exisiting reports.universe-object-datatype.png

Thanks

[amitrathi239]

Instead of changing the datatype of the object,create new object with datatype Number so that there will be no impact on existing reports.

[former_member272336]

Thanks for suggestion.

We can link on another column instead which are both numeric - wouldn't want to have 2 objects with nearly same name in universe as would create more confusion.

It looks like best policy may be if have pre-existing reports to avoid changing datatype due to this behaviour.

Would have been better if product could automatically detect no real difference between e.g. 777777 and '777777'

[amitrathi239]

What is the datatype in database for this object?

[former_member272336]

Number datatype

[denis_konovalov]

Why would you expect change at universe level not to affect existing reports ?
This is not a simple change - 777777 and '777777' are 2 completely different things.

Looks like the product works as it supposed to.

[former_member272336]

Query running against an Oracle Database which automatically converts a value from one datatype to another when such a conversion makes sense - in this case if run query ..col = '777777' or col=777777 returns data.

col defined as number on database

Had thought business objects may also have done similar - looks like we will need to bear this in mind and avoid any changes to any universe column datatype.