We just migrated to BO 4.1 sp3 and we are encountering an issue where when we try to link from one web intelligence report to another one with a specific date, it gets converted to a different timezone which fails the query behind… for example when we are passing down 11/15/2015… it get converted to 11/15/2015 6:00:00 PM …
any idea how to fix this or is that any settings needs to be configured?
Webi hold the actual value, which can different from the formated value you see in the report. While you may see your datetime formated as a date, webi will see the real datetime value. You should try to explicitly convert your datetime field to date.
FormatDate(datetimefield; "dd/MM/yyyy" )
But the best would be to do it in the universe, since there’s no point to add the time when you only want the date. Some DBA will create every date as datetime, which will put “12:00:000 AM” by default to all dates. Then you need to cast it as date.
For any(well, probably any) database, 11/15/2015 12:00:00 AM is the same thing as 11/15/2015
We were only facing this issue after upgrading to 4.1 sp3 … I think what you mentioned does make sense however it would be quite impossible for us to go back to all universe and change the field type from datetime to date…
so my question is, when I have &lsSTransactionDate=11/15/2015 in the URL. why would BO think it is 11/15/2015 6:00:00 PM when it hits the destination report?
is that a timezone issue or someplace I should have configured ?
This seems like an issue that could be because of the timezone difference between BusObj Server, Client and the database. Its either that or related to an issue observed in some patches documented here :
I had learned much ago that the safest way to deal with date/datetime fields is to compare truncated values for Dates in parameters - unless a timestamp is absolutely needed for the where clause.
(BOB member since 2011-05-16)