Symptom
- After converting classic analytic applications to the optimized story experience, certain scripted functionalities no longer work.
- Search action does not apply the account filter after entering a member and clicking the search button.
- After removing the member and clicking search again, the table returns with the hierarchy collapsed instead of the initial state.
Environment
SAP Analytics Cloud 1.0
Reproducing the Issue
- Open an optimized story converted from a classic analytic application that uses custom scripting.
- Use the search input to enter a member and click the search button.
- Observe that the member filter is not applied; removing the filter and clicking search collapses the hierarchy instead of restoring the initial state.
Cause
- Using PlanningModel.getMembers() can return member ids that do not match the ids expected by setDimensionFilter in the optimized story; this leads to filters not being applied.
- This happened to work with Analytics Designer and it was a bug.
- This bug has been fixed by Optimized Story so it stops working with Optimized Story.
Resolution
Replace uses of PlanningModel.getMembers() with the corresponding component’s DataSource API to retrieve members, for example: use Table.getDataSource().getMembers("", { limit: }) so that returned member ids are consistent with filtering in the optimized story.
See Also
Keywords
optimized story, unified story, analytic application, setdimensionfilter, mdx unique name, account hierarchy, filter not applied, getselection empty, planning.getmembers, datasource.getmembers, import data model, story conversion, migration, table selection, search button , KBA , LOD-ANA-AD-INF , Analytics Designer Infrastructure , Problem
SAP Knowledge Base Article - Public