Symptom
- The getPlanning().setEnabled() API is not working as intended when using bookmarks.
- Planning remains enabled after Table.getPlanning().setEnabled(false) runs in onInitialization.
- Bookmarks stop working as expected after story load and bookmark application.
- Warning message: "Pausing data refresh didn't work because planning is enabled."
Environment
- SAP Analytics Cloud
Reproducing the Issue
- Open a story that contains a table where a script calls Table.getPlanning().setEnabled(false) in the onInitialization event.
- After the story fully loads, apply a bookmark.
- Observe that a warning indicates refresh pause cannot be applied because planning is enabled, and planning remains enabled instead of being disabled.
Cause
When opening a bookmark, the planning state was restored incorrectly, creating a conflicting state where refresh pause was on while planning was enabled; as a result, setEnabled and setRefreshPaused returned early and did not change the state.
Resolution
- Update SAP Analytics Cloud to the release containing the fix for the bookmark planning state inconsistency (QRC3, client version 2026.15.2 or later).
- After the update, validate the behavior: open the story, apply the bookmark, and confirm that planning is disabled as expected and no warning appears.
- If the issue persists after updating, review the story’s scripting and bookmark configuration with the help guide.
See Also
Keywords
SAP Analytics Cloud, story, table, bookmark, planning, setEnabled, getPlanning, scripting, onInitialization, setRefreshPaused, refresh pause, warning message, optimized story, table API, bookmark restore , KBA , LOD-ANA-PL-DE , Data Entry and Mass Data Entry , Problem
Product
SAP Analytics Cloud all versions
SAP Knowledge Base Article - Public