Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 209 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Oracle Analytics Classic Analysis Session Variables can they be dynamic

We use intensively session variables in our analysis queries (which are used in DV datasets) and in particular we have a session variable called report_name which allows through the RPD to make the query retrieve data for this report. Currently our session variable statement would be e.g. set variable am_report_name = 'PER01-PBRER-PRODUCT1';
Question : is there a way to make the session variable dynamic using logic : e.g. am_report_name = derive value from parsing the actual analysis file name. Can session variable use logical sql and is there a way to retrieve the analysis file name in logical sql?
This would bring a huge benefit to us as then the analysis file name e.g. PER01-PBRER-PRODUCT1-case listing would drive the session variable name and we would have no need to update it as it would become dynamic.
Answers
-
hi @Philippe ROGIERS-Oracle , is your question to have a session variable hold the datasource file name that the RPD should dynamically point to (this can be done reasonably easy), or is it different than this ?
0 -
This is right : if we could have a session variable which would hold the datasource file name, the RPD would dynamically point to this and we would reduce a lot our current manual work of setting the session variable manually when we duplicate our reports e.g. for different products or time periods. We are looking for any information which would tell the RPD to dynamically introduce into the RPD query where clause the selection of the appropriate product or time period. We code our datasets, workbooks, all queries with a report code e.g. PER011-PRODUCTB-PBRER (PER011 is the key) and since the RPD has a table with all report codes (e.g. PER011, PER012, PER013,..) and associated inclusion criteria with regards to products and time periods, as soon as the code PER011 is dynamically shared with the RPD everything becomes dynamic versus manual before when duplicating datasets, workbooks, queries and changing the appropriate code e.g. PER011 becomes PER012, PER013 etc..
0