Curious if anyone has developed for their organization a best practices document they would be willing to share for data modules?
Running into things like multiple subject areas that share tables, in a framework manager package we would create one project and have all the subjects together, then publish separate packages for the subject area. Then we don't have maintain the tables in multiple projects. How do you handle this with data modules?
If you put a navigation path into a common table then you have to recreate it when you link common table to another data module because according Cognos moving the navigation path forward isn't done by design.
------------------------------
Jo Marie Sellner
------------------------------
#CognosAnalyticswithWatson