Olap universe date format

[Former Member]

Hello,

BW query connected to universe.

BW query holds the date values in some of the characteristics-attributes which is of type 'date'.

When this imported to BO universe, the date type characteristics are appearing as 'character'.

This is causing problem when sorting the report.... it is sorted in alphabetical order but not in Date order.

When changing in universe as 'object properties' -> type -> Date. It is giving Error when running the webi report 'A database error occured. The database error text is: (CS) "Driver not capable" . (WIS 10901)' (or) when check integrity in universe.

How to make the type as date in universe for Time characteristics.

Thanks

Sreedh.

[Former Member · Accepted solution]

What is the BOBJ version, that you are using.

-AK

[Former Member · Accepted solution]

Hi,

You cannot change the datatype in the universe otherwise you will have the same error you described.

We support date datatype for characteristics:

- universe dimensions (date)

- universe detail (string)

Which BOE version do you have installed?

Didier

[Former Member · Accepted solution]

Following are the version installed.

Universe Designer : 12.1.0.882

Webi Rich Client : 12.2.6.567

As mentioned in earlier notes.... Webi report connected to Universe to BW Query.

BW query has attributes of 0calweek and it has ValidFrom(date type). The ValidFrom is appearing as character format and the requirement is to treat ValidFrom as date format in BO (universe or in webi) so that customer can able to Sort by date. Since ValidFrom in universe changed to character format after the query connected to Universe, so ValidFrom is Sorting as character but not like date. Is there workaround to make ValidFrom as datetype in BO or anyother version support this.

Thanks

Sreedh.

[Former Member · Accepted solution]

Hi,

As I said you cannot turn the datatype from string to date in an OLAP universe.

We are aware about this limitation and we plan to address it in a future release.

The only workaround is to transform the object into date in the Web Intelligence document.

Didier