KB47098: In MicroStrategy Analytics Enterprise, when the source attribute of a parent selector is not in the target, the selector has an empty element list or has no control over the child selector

SYMPTOM
In a Strategy Analytics Enterprise report services document, either the parent selector contains no concrete elements or even though it has elements, it can't control the child selector when ALL the following conditions are met:
 
      1.     A parent slicing selector targets a child slicing selector
      2.     The child selector targets a grid(s) or a panel(s) that has some dynamic texts
      3.     The source attribute of the parent selector doesn't exist in any of the grids or the panels mentioned above
 
 
STEPS TO REPRODUCE
This behavior has been explained below based on the Strategy Tutorial project 
 
Case A

• Region selector only targets Call Center selector.
• The child selector then targets the panel with the dynamic texts: {Call Center} and {Cost}. Note that source attribute 'Region' of the parent selector is not on the panel as shown below:
   
  

• When the document is executed, the 'Region' selector element list is empty as shown below: 

 
CASE B
 
If Region selector targets not only the child selector but also targets some other grids or dynamic texts that are not the child selector's targets, then the parent selector show some elements but whichever element is selected, the child selector always has all the elements available:
 

 
After executing the document,  the parent selector shows some elements as shown below, but the selector on Call Center shows all the elements.
 

 
 
CAUSE
 
In Strategy Analytics Enterprise, the element list of a slicing selector is generated based on the targets. In the example, the only target of Region selector is Call Center selector. As a result, Call Center selector's target will be considered as the target for Region selector. In this case the target is a run-time template {Call Center, Cost}. When creating the element list of Region selector, no Region elements is found in the target template so the selector has an empty list. When generating Call Center selector elements, Region elements are used to filter the target template. As Region is not included, the filter is ignored and all the Call Center elements are obtained for the child selec
 
WORKAROUND:
One of the following three workarounds can be used to make the parent selector control the child selector:

• Add the source attribute of the parent selector to the targets of the child selector.
   
  (OR)
• Make the parent selector also target the child selector’s targets. Then the source attribute of the parent selector will be added to the run-time target template at backend. So the correct element list can be generated from the target(s).
   
  (OR)
• Replace the child selector with a template selector. Take the above two cases for example. Insert a grid which only contains Call Center in rows. Use Call Center in the grid as a template slicing selector, targeting the desired object(s). Make sure the grid’s data source is the same as that of the targets. And hide the row header.

     (OR)

• Change the parent selector from a slicer to a filter selector. Right mouse click the parent selector to open Properties and Formatting window, go to Selector Tab and then check the "Apply selections as a filter" option. Dashboard in off-line Flash or mobile devices are not available once applying this workaround.