Bug: Startup Parameter not detected on Interface scenario generation

Question

Hi,
I'd like to report a bug in ODI when generating a scenario from an Interface.
When a variable is used in the Diagram tab there is no problem, so this can be the work around.
However when one uses a variable on the flow tab in one of the KM options, you'll find that variable is not detected when generating a scenario from this interface.
The KM I'm using is: IKM SQL to Hyperion Essbase (DATA)
Here the RULE_FILE option is set to: #vDataLoadRule -- (Also tried '#{project_name}.vDataLoadRule' )
Hope this can be solved in new release, so one is not forced to make non sense where clauses in the interface.
How to use the work around?
If you do not yet have a filter on your source, then:
Create a Filter on your source data store, by dragging and dropping a field.
in the filter set something like this:
{DataStore}.{DataField} = {DataStore}.{DataField}
and #{myVariable} = #{myVariable}
Otherwise, just add the following to an existing source filter:
and #{myVariable} = #{myVariable}
This will create an where clause on your source, which is always true.
Hope this helps!
Rudy

Answer 1

Hi John, thanks for your quick reply.
Doing it dynamicaly is my way to build stuff.
So I've the situation where need to load data to several cubes (more are coming).
I want my life to be easy (as there is more to life...) and so I've created a package that does the following:
Get details of the cube that needs to be processed and process it. The benefit is, that I only need to create a new interface (not a whole package) and register it in my essbase metadata table when a new cube is built.
Of course I can drag the Interface into that package, but then that package is only capable of running that interface, since there is no way to set a variable Interface name.
Hence, I need the interface as an scenario, so that I can make it dynamic.
I have a package that initializes the variables e.g. #vDataLoadRule, #vDataLoadName, #vDataLoadVersion, Which I get from my sql table that holds my Essbase Database metadata ( Server, Application, DatabaseName, DataLoadName, DataLoadVersion, DataLoadRule) and then runs the scenario. The DataLoadName and DataLoadVersion are name and version of the Scenario (Interface) that needs to be processed.
So with that as a background, I'd like to have dynamic Interfaces.
The problem is that when you use a variable in the diagram tab of the interface it's perfectly detected when you generate a scenario of the interface, however when you use the variable in the flow tab, it's not detected on scenario generation.
To me that's a bug.
Cheers!