I am using BOXI R2. I have created webi report with prompts for date.
Now whenever I refresh the report it prompt me for date and It shows me the calender. I select the date but after selecting the date it shows the time stamp with date.
I need to show only date without timestamp everytime i refresh the report.
As well as in database we have date with timestamp.
I found oe more thing, this is happen only in view mode i.e. when I open the report in view mode and refresh it then select the date then it comes with time stamp but when i modify it and refresh the report and put the date then it shows only date without timestamp.
I had the same issue, but not in WebI, so I’m not sure if this is what you need. I resolved on the universe side. Here is a link I found that helped fix my problem…
As soon as you start applying functions at the client level (ie truncate, instring etc. etc.) you will find unless your DBA has built some function based indexes (unlikely), the indexes won’t get hit and performance will be compromised.
Which leads me onto my second point, a good data warehouse should have dates truncated when stored as a date. If storing date and time as an element is important, this should be in a seperate column on the table (ie Date = trunc(Date), DateTime = Date).
If this is done, you should be able to either:
a) manually enter in the date without a time element.
b) select from the calendar object. This will return a time element, but if the column you are hitting alredy has dates truncated, the issue should become one of cosmetics only.
I am facing the same problem. And I get this problem when I open the report in view mode or save the report and reopen it. Please let me know if you find a way to eliminate the time (even though it is default) from the date field. Also Trunc(Table.datecolumn) did not work for me at universe level.
BO treats date as string when we passed as prompt, so it displays timestamp. we can remove this by appyling to_char() function in universe.
Create a new object in universe of type char.
then apply function
to_char(calendar_date,‘mm/dd/yyyy’), not exact the same, something like that.
But we can’t sort the variable, if we apply sort then it ll sort as
01/01/2005
01/01/2006
…
This works if you are selecting from the LOV, it doesn’t work with calendar. I don’t believe there are any changes you can make at a universe level where you can stop this behaviour with the calendar.
You are better off using Truncate if you are using Oracle or a DB function that will convert your character to a date once you have set the desired “format”…