Ensure Report Functionality for Data Modules with Unloaded Schema Assets

Currently, if a data module includes schema assets that are not loaded into the Cognos environment, all reports based on the data module fail, even if the reports only reference loaded sources. This behavior negatively impacts the usability and reliability of data modules in event-driven environments.

Problem Statement:
The issue arises in scenarios where data modules are generated dynamically using event-driven processes, and certain schema assets are not loaded into Cognos due to missing events or other edge cases. When such unloaded schema assets are included in a data module, all reports referencing the data module fail, even if the reports only utilize query subjects from loaded sources.

This behavior is inconsistent with the expected functionality. Reports that rely solely on loaded schema assets should continue to function, while only those referencing unloaded schema assets should fail.

Proposed Solution:

• Modify the validation logic of data modules to ensure that reports referencing only loaded schema assets can still execute successfully.

• Implement a mechanism to handle unloaded schema assets more gracefully, such as flagging them without invalidating the entire data module.

• Optionally, introduce an automated process to detect and load missing schema assets when a data module is generated.

Business Impact:
This enhancement would significantly improve the stability and usability of data modules in event-driven environments. It would prevent the failure of all reports based on a data module due to unloaded schema assets, ensuring that users can continue working with loaded sources without interruption. This improvement would enhance user experience and reduce the operational impact of edge cases where schema assets are not loaded.

Reference:
This issue has been detailed in the attached support case, where specific scenarios and their impacts have been described. For example, Scenario 1 highlights an unexpected error where reports fail even when they only reference loaded sources, while Scenario 2 demonstrates the expected behavior when schema assets are manually deleted after being loaded.