Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
The only way you can achieve this is by creating several Compound Views (one for each view) and use the compound views instead of the original views in the Dashboard. (if this makes sense)
-
Hi, Where are you trying to change the loglevel? It may be worth checking the value defined in EM, there is a note in oracle support which is about 11g but I believe it still applies to 12c How to set Trace 32 Log levels for BI Publisher 11g (Doc ID 1459264.1)
-
Can you force the Column format in the column properties?
-
My assumption is that the two issues I am troubleshooting would still be evident in he 12c version. Do you have a 12c environment where to test? Otherwise you can't work with just that assumption in your mind
-
Can you then try deactivate cache polling or understand why the statement is failing? This gives you info about removing cache with polling table
-
Happy to help! If this thread contains the solution to your problem please mark it as solved to help others with the same problem! Francesco
-
Did you check if there are multiple files named UserScript.js? maybe the changes are applied to the wrong one
-
Hi, I found that the issue is due to caching. Please try: a) restart the analytics deployment in the console b) delete the history in your browser c) close and open your browser
-
Unfortunately the maps generated by external code like the one you're using in your custom HTML are not supported by Oracle... You really need to recheck all the code since tags and HTML pieces can change between versions.
-
The GoURL parameters can be found here https://gerardnico.com/wiki/dat/obiee/obips/go_url No specific accessibility option, but you may try with &Action=Extract
-
If you can't see the default functions I believe this means that the UserScript.js file is somehow corrupted. My suggestion is to restore the original UserScripts.js and retry. In case you are working from a Win platform into a Linux server, verify that you're not introducing special characters in the file that may corrupt…
-
Hi, I've seen sometimes multiple UserScript.js files in the $FMW_HOME, can you try locating and changing all the files? In addiction sometimes browser cache deletion helps. Thanks Francesco
-
Have you checked everything is properly shutdown before starting it? is there a process running that may have a port conflict? did you change anything lately that could have an impact?
-
Glad it solved! You should now mark the thread as answered since as of now still appears as Not Answered.
-
The max you can do is attach a dashboard page as an agent payload. Check that option it may give you something similar (but not divided in multiple files) to what you're looking for.
-
UNION and aggregate calculations are always a problem because you can't really setup a proper aggregation formula... Is the column NULL in the first part of the UNION and filled with the formula in the second? Have you tried switching the two request (putting the second as first)? Are you forced to use the UNION is there…
-
What date did you choose? If you choose 13-07-2017 it should show dates between 06-07-2017 and 12-07-2017 with the filter "Times"."DATEMAKE" >=TIMESTAMPADD(SQL_TSI_WEEK,-1,cast('@{pv}{17/07/2017' as date)) and "Times"."DATEMAKE" <cast('@{pv}{17/07/2017' as date) BTW marking the replies as helpful or correct will help…
-
The problem is that you are missing part of the filter "Times"."DATEMAKE" >=TIMESTAMPADD(SQL_TSI_WEEK,-1,cast('@{pv}{17/07/2017' as date)) will filter from 7 days before the selected date you need to also add another where condition like "Times"."DATEMAKE" <cast('@{pv}{17/07/2017' as date)
-
If I understand you correctly you want to show the data of the week before the selected date? what about? "Times"."DATEMAKE" >=TIMESTAMPADD(SQL_TSI_WEEK,-1,cast('@{pv}{17/07/2017' as date))
-
The same Doc you mention has a step under "Steps to perfom on the 'target' environment you are cloning to:" which says "Move / rename the instances directory to old_instance. The prior scrips created the instance directory, but it is nothing other than a placeholder / shell. If you do not rename it, then next script will…