If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

"Live" Look up via Parameter Map in FM

Started by deadsea, 04 Jul 2014 09:44:10 AM

Previous topic - Next topic

deadsea

Hello All:

I am in a planning stage of a project and still waiting on my FM install to come along, so pardon the question which I am hoping is a quickie for most.

My question is if it is possible to utilize a slowly changing parameter map (loaded via ETL generated txt source file) without re-publishing the FM package periodically? I have utilized a static parameter maps many times, but not sure if non-static ones will require republishing the package after each change.

If it needs to be published, I will use sdk to publish the package, but really hoping that I can do this without re- publishing package.

Thank!

cognostechie

You are correct. Paramater Maps which are based on a table in the DB do not need re-publishing the package. You said that
you are using an ETL generated Text file, not sure about that but you could always write the data to a table in the DB using
the same ETL process with a little bit of tweak.

deadsea

Hi CognosTechie:

Thanks for your response.

I was actually referring the "import" option of parameter maps, where you would import the csv/txt file to load up the maps. If this is done once and the ETL process continues to update the csv/txt file I will use of parameter maps (say daily - delta updates), will the import of these map values need to take place each time we update the source csv/txt file?

In the long run we will create a table and this is just temporary stage (while clients DB folks catch up).

cognostechie

Hi -

Yes, I believe Parameter Maps work the same way for static values and values imported from a text file. Those values get stored inside the model.xml file so the package will need to be published again when the values change. It doesn't need to be published when the values are used from a query subject which references a DB table.

deadsea

Thanks. Thats sorta what I figured. Guess would make for an ok/good enhancement!