Model versioning issues that might cause errors during report runs
Under some circumstances, model versioning in a package might not work as intended, or the model itself might contain unexpected changes. Both types of problems can cause issues when reports are run.
The following list provides examples of issues, some of them based on client scenarios:
- A package contains a model (named “model”), which references a TM1 data source. The package also
contains other models (with names that are timestamps), which reference TMR (IBM Cognos Planning)
data sources. This combination of model objects in a package indicates that model versioning is
combined with no model versioning.
In newer versions of Cognos® Analytics, TM1 data sources are not supported so the reports cannot run. Opening and saving the reports in Reporting resolves the problem because the report specifications are updated to point to the latest model version, which is TMR-based and supported in Cognos Analytics.
- An older model version no longer exists so the report service (RSVP) runs a report with the
latest model version. The report cannot run because the model was changed.
In this case, editing the report moves it to the latest model version. Then, the author must make all required changes to deal with the model changes.