scespinoza
commented
1 month ago Didn't really have a solution. We will be able hopefully to get the filtered list of members for a cube from the backend (now its for a dimension, so it can have members that are not available on some cubes). Regarding the list of members for a query, that's not feasible at least in the short term. In any case the solution must come from the backend. In the frontend will probably involve passing the cube as a parameter to the members endpoint
Seems that we are retrieving more unique members that we need when filtering a Dimension. We have the scenario where we can select a few filter items that have not results, so a "not found" message is displayed to the user.
@scespinoza had a solution in mind for this.