Hi Ashlee
Maybe post your configurations of the combo boxes? It may just be a setting...
This is a requirement that comes up on many projects. It has the common name over the years as "Combo Edits". Essentially we want to prevent a user from adding data to dimension intersections that are unrelated other then they exist.
e.g. If a communication company has sales channels "Subscriptions" and "Equipment" , and Product hierarchies "Consumer Electronics" and "Streaming Services", you would not want a planner to have access to enter a subscription revenue data for a product like a Router that is simply sold once.
One way to accomplish this is with a lookup table that manages relevance.
With a dashboard Extender rule, you can get the selected value of the first combo box and use that to query your table where you store the names of the hierarchy or members that are relevant to the combobox choice. The results of the query are assigned to the parameter of the second combobox. This all gets passed back to the dashboard using the XFSelectionChangedTaskResult object. Then the second combobox will dispaly only the values you looked up in the dashboard extender rule.
The first combo box will need a Server Task assigned that is the Dashboard Extender rule (DER) that does the lookup.
It will also need a bound parameter.
The DER will set the bound parameter on the second combo box.
