Unable to pass Date among DPs. Is this a limitation for BO?

building semantic layer
1

I have two data provider.

I took some date “D1” in DP1.
Now In DP2, m selecting some objects, with a condition on
cydate = Select query results(DP1.D1)

when I run this report it gives me an error saying:-
Exception: DBD, [NCR][ODBC Teradata Driver][Teradata Database] A character string failed conversion to a numeric value. State: 22003

I tried passing numbers and characters, they work fine…however it doesn’t work with dates. Is this a limitation in BO or there is ny other way to do that.
I am using BO6.5

bounty (BOB member since 2007-02-16)

2

I believe most people stay away from using query results in that manner as there did exist an issue at one time. Might be something to look into before you rely on this functionality. Do a search on this, I remember using it and it was causing some issues that I believe related to the queries and the order to which they returned with data and making the report seem like it was corrupted as it would sometimes show junk data in the report.

To your question, have you verified your dataprovider without the use of query results? The error that you listed doesn’t really reference an issue with dates whatsoever. Also, I would check whether all objects involved are of the same datatype.

JTAMBLYN :canada: (BOB member since 2003-05-28)

3

Take a look at these two postings:

JTAMBLYN :canada: (BOB member since 2003-05-28)

4

Hi JTAMBLYN,

Thanks much for the response…My report is exactly similer as referred in the second link provided by you…

@dpvalues(‘Claims.From_Date_of_Service_Dtl’,268435460,19)@dpend

the above condition appears in sql for the query and I am using Tera data

Its specified there that this is a bug with BO and their is a fix to it…hmm…welll I have change the way I am creating report now however
I still want to get the details of that reported bug and the fix “bug # 1089731”. I tried to find on Business Objects website…failed to get it.

Thanks Again.

bounty (BOB member since 2007-02-16)

5

Using Teradata…

This still does not work with dates in XiR2 SP2!

Any suggestions?

anorak :uk: (BOB member since 2002-09-13)

6

Based on the error message, it is about the data type. I use Teradata as well. I wonder if the two dates you use are exactly the same. I mean: cydate and DP1.D1. If one date has timestamp, the other doesn’t, it will give you error message. You can try the same formula in Teradata SQL Assistant to see if you get the message again. I don’t think it is BO.

Lilly J (BOB member since 2002-08-22)

7

Lilly,

I’m using the same Date object in all instances, so this cannot be the cause of the error.

anorak :uk: (BOB member since 2002-09-13)

8

Anorak:

Just copy what you used in the universe to Teradata SQL Assistant to run it to see if there is any error message.

Lilly J (BOB member since 2002-08-22)

9

Business Objects has confirmed that this is a Teradata specific bug that has been corrected in FixPack2.6.

A workaround is to Save and Close your query, and then refresh. For some reason, the error message does not appear when you use this method.

anorak :uk: (BOB member since 2002-09-13)