Hello,
I have found quite interesting workaround for following problem:
If you want to have some variable - i.e. dimension, type date then you should know that list of values for this specific variable will probably have timestamp format. This is not problem in table in report, you can always set specific date format there, but it is problem in prompt or when you want to use UserResponse function for this variable and wanna specific format directly from universe.
The thing is whatever you do in custom SQL in LOV, the format is still the same (this is conditioned by date type variable - at least this is behaviour on XI 3.1 and Teradata Database). Sure you can cast this date variable to char and then there is no problem with specific format, but if the table contains multi-millions of rows it is not exactly the greatest idea because casting eliminates partitioning and most likely statistics on this as well so it will result to unwanted all-scan and performance loss.
When you attempt to try cast only LOV, error about incompatible format appears. And the solution?
Create different variable,just duplicate original date variable and cast it to char. No LOV for this variable needed. In original date variable edit LOV, in selection pane choose new char date variable - that is the trick, because now you will be able to use custom SQL with changing of date type to char and specifying format - no error occurs and it works perfectly well.
If you have any question feel free to post.
AnAlienHolakres3 (BOB member since 2012-04-06)