If you have a view in IBM Planning Analytics that only shows the correct data after a manual refresh, it can be frustrating for users and difficult to trust.
This is something we often see in models that were originally built in legacy TM1, where older functions are still being used in view definitions.
The good news is that it is usually straightforward to fix.
What causes the issue? #
In many cases, the view is using a dynamic subset created with:
TM1SubsetToSet
While this works, it does not always evaluate dynamically when the view is opened. This can result in:
- Views showing outdated data
- Users needing to manually refresh to see correct results
How to fix the issue #
The solution is to replace the subset reference with the underlying MDX expression, so the view evaluates correctly every time it is opened.
Step 1: Identify the subset used in the view #
Open the view that is not returning the correct data and check which subset is being used.
For example, in the health check, the view “BS Input” uses the subset:
“Current Year Periods Onwards”
Step 2: Open the subset editor #
Next, open the subset that is being referenced.
In the opened view, open edit MDX page.
This shows the logic behind how the subset is dynamically generated.
Step 3: Copy the MDX definition #
Copy the full MDX expression from the subset.
This is the key step, as we will use this directly in the view instead of referencing the subset.
Step 4: Paste the MDX into the view #
Go back to the view and open the MDX editor.
Paste the copied MDX expression into the view definition and apply it.
Once applied, the view will now evaluate the logic directly, rather than relying on the subset.
Step 5: Apply this across all relevant dimensions #
If the view uses multiple dynamic subsets, repeat this process for each dimension.
In our example, this approach was applied across the full view to ensure consistent results
What this fixes #
After applying the MDX directly:
- The view evaluates correctly when opened
- No manual refresh is required
- Users can trust the data they are seeing
Final thought #
If users are regularly refreshing views to “fix” the numbers, it is often a sign that the view logic needs updating.
Replacing subset references with MDX is a simple change, but it can make a big difference to both accuracy and user confidence.
For help reviewing your Planning Analytics setup, contact us, we’re always happy to help.
