cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

#DATATYPE ERROR

Former Member
0 Likes
964

Hi Guru's,

Iu2019ve got an issue here on some of my reports on QA, the very same reports are running fine on Dev environment but the problem is in QA some columns are showing #DATATYPE on the reports when run on InfoView in QA, what is strange is the fact that the same report if I run it from BO rich client it runs fine and it shows the figures without any problems.

Iu2019ve checked these measures at Universe level and everything looks ok, like the function is set as sum.

Any advise from you side please?

Accepted Solutions (0)

Answers (3)

Answers (3)

ashish_gupta3
Product and Topic Expert
Product and Topic Expert
0 Likes

If it's working on Rich Client but fails in Infoview - you are probably having different middleware connectivity setting on your client machine than on the BOBJ Server.

e.g. If you are using Oracle, make sure you have the same tnsnames.ora file on your desktop as on the BOBJ Server or you are pointing to the same Oracle Name server at both the places. If it's a different setting, check the appropriate database configuration.

0 Likes

WHat kind of data source do you use? Are those converted DeskI reports?

Regards,

Stratos

Former Member
0 Likes

Hi Stratos,

I'm using BW InfoCube => multiprovider => BEX Query => Universe => Webi. So the key figure used in Webi is created from the InfoCube.

0 Likes

Are you on BO XI 3.,1 SP2 and FP 2.4?

Regards,

Stratos

former_member793810
Active Contributor
0 Likes

This means it is throwing wrong data. Suppose your data is numerical but it is throwing char or something else then this error comes.

What happens, The value_if_true and value_if_false parameters can mix string and number or string and date/time data types. If these data types are mixed, the function returns a string.

Date/time and number data types cannot be mixed; this results in a #DATATYPE error.

Can you check your variable again please?

Or you can refresh the report again to see if this error is gone.

Regards,

Bashir Awan