Hi listers,
Anyone seen that message, specifically after an upgrade of 4.15 to 5.01? most of the rest of what we have tested came across ok, but reports against that report won’t run…
Any ideas? I am thinking of starting by re-exporting the universe, but I am open to any suggestions…
Thanks,
Brent
Listserv Archives (BOB member since 2002-06-25)
Answering my own post now…
I found an answer in the BO knowledgebase, that the contexts weren’t properly set - now just need to find out if they were correct before the upgrade, or if this is a symptom of a bad migration…
Brent
Listserv Archives (BOB member since 2002-06-25)
Yes,
looking at aggregate navigation may be your answer. It’s possible to set up aggregate aware objects that don’t drill down to a bottom level.
Aggregate table 1(A1) -> Base table (B1)
Aggregate table 1 is incompatable with Object X
If you Create Object Y that is say Sum(A1.amount) without specifying a drilldown
then ask for Object X, Object Y in a report, you will get this message !
(fix is create Object Y as @Aggregate _Aware(Sum(A1.amount),Sum(B1.amount))
Simon
Listserv Archives (BOB member since 2002-06-25)