We are using a 'corporate' version of the data warehouse but need to add additional 'local' tables and columns to the database structure. This will then necessitate applying additions/modifications to the issued catalog. [We are using specific prefixes to ensure there is no clash of names]
I have now been warned by the central development team that I will encounter problems in the future, i.e. when they issue an upgrade to their system and I add back in the modifications I have made locally.
I am told this is because Cognos issues internal ids for the items defined within the catalog and these are used in Impromptu, etc. to identify the specific data items referenced within the report(s).
When changes are applied to the catalog, there is a risk that particular internal ids will now point to a different item in the database.
Can anyone clarify if I really do have a (potential) problem. If so, what are the recommendations of how to minimise the affect of this difficulty.
I have now been warned by the central development team that I will encounter problems in the future, i.e. when they issue an upgrade to their system and I add back in the modifications I have made locally.
I am told this is because Cognos issues internal ids for the items defined within the catalog and these are used in Impromptu, etc. to identify the specific data items referenced within the report(s).
When changes are applied to the catalog, there is a risk that particular internal ids will now point to a different item in the database.
Can anyone clarify if I really do have a (potential) problem. If so, what are the recommendations of how to minimise the affect of this difficulty.