Navigation Paths for Data Modules

Need to have the option of bring a navigation path create in a data module forward when you link it into another data module

Steps

1. Create 'Data Module A' which contains Navigation Path(s), security, property setting
2. Create 'Data Module B' and save.
3. 'Data Module A' is appended to 'Data Module B'. 'Data Module A' will be added to other Data modules going forward
4.  After the new data is added to 'Data Module B', the navigation paths you have created in Data Module A should show in data module B

This is make maintenance easier and it allows to setup common tables that will be shared for reuse.

Currently, I have a set of about 5 common tables that are used across currently 4 subject area that are secured to user based on the subjects they have access to, if I have add each table, the sorting, navigation and security multiple times and also maintain them multiple times.  By being able to add them to a common data modules and set everything up once development and maintain is easier and faster.

Per Cognos:

Navigation Paths will not be included when adding a data module containing navigation paths to another data module.

The reason for this is the following:

The main issue here is fact that the navigation paths are independent of tables. When bringing Data Module A over to B, You may select which tables from A you want bring into B. The nav paths aren't included as they may no longer be relevant to the tables moving from Data Module A to B.

For example, you may have a nav path in Data Module A spans fields from tables X, Y, and Z. You may then wish to bring in table X only into Data Module B. Bringing over the nav path doesn't make sense since it has table references that doesn't exist in B (i.e. tables Y and Z).