This content has been marked as final. Show 7 replies
Yes, we found a solution. In the SQL for the initialization block, set up the code to look like this:
select cast(year as number (4,0)) from blah....
The ,0 in the number specifier truncates any decimal data, and OBIEE then sees it as an integer type instead of decimal. Sorry, I posted this answer in another thread, but there seem to be quite a few threads about this issue.
Hope it helps!
Thanks for the reply!
I am using select max(case when param_nm = 'Var_All_Curr_Fiscal_Year' then cast(param_val_num as number (4,0)) end)
But still defaulting to 2013.0d. Am I missing something?
Have you gone through my suggestions at the below links?
The .0d date issue
Re: OBIEE 126.96.36.199.2 BP1 Repository Variable data type
You have to do it where ever you are using that rep. variable not in the init block.
Yes, I have been using select valueof(year) from abc in front end in dashboard prompt. But instead I am looking for a patch update or permanent fix in rpd itself. Is it resolved in the latest release of OBI. I am currently using 188.8.131.52.6
Insted of doing work around... My Suggestion would be to Try in new version OBIEE 184.108.40.206.8 . I don't see this issue in OBIEE 220.127.116.11.8
But But.. We are having few more new bugs in OBIEE 18.104.22.168.8
Edited by: Venkat Krishna on Mar 6, 2013 7:53 AM
Yes even I have heard about bugs in 22.214.171.124.8. How about 126.96.36.199.7? Is it resolved there?
Again!!!!! Check last msg at Re: OBIEE 188.8.131.52.2 BP1 Repository Variable data type
This issue is fixed in the version 184.108.40.206.7 BP.
Hope this helps to close this
Edited by: Srini VEERAVALLI on Mar 6, 2013 10:02 AM