Intelligence Server crashes after removing a report used as a filter from a dashboard

Symptom

MicroStrategy Intelligence Server crashes when removing a report from a dashboard in which that same report is used as a filter for another report.

Steps to Reproduce

1. Create a report named RA.
2. Create a report named RB, and set RA as a filter of RB.
3. Create a dashboard, and add RB first and then RA as separate datasets.
4. In the dashboard editor, edit RA from within the dashboard and choose to update the standalone report RA directly (uncheck “keep Changes Local“ before updating).
5. After saving the changes, remove RA from the dashboard.
6. At this point, Intelligence Server may crash.

Cause

When both reports RA and RB are added to the same dashboard, the dashboard internally maintains separate contexts for each report. Because RA is used as a filter for RB, the definition of RA is referenced in both contexts.

When RA is edited from within the dashboard and the changes are saved back to the standalone report, both internal references end up pointing to the same underlying context. Removing RA from the dashboard then releases that context while it is still referenced by RB. When Intelligence Server later tries to access the released context through RB, it leads to a crash.

Solution

There is currently no simple and safe code change available to address this behavior in the product version listed below. To avoid triggering this issue, use one of the following recommendations:

1. Do not remove a report that is used as a filter in the same dashboard after editing it as a standalone report from within the dashboard.
2. If a report is used as a filter for another report in the dashboard:
1. Avoid adding that report as a separate dataset in the same dashboard; or
2. If it must be included, avoid editing and saving it as a standalone report from within the dashboard and then removing it.
3. If changes to the filter report (RA) are required:
1. Edit RA directly from the Reports or Objects area outside the dashboard.
2. Save RA.
3. Reopen the dashboard so it picks up the updated definition of RA.
   
   

Following these guidelines helps to prevent the Intelligence Server crash until a permanent fix becomes available in a future release.