Sparse Dynamic Members in Data Maps on Hybrid
SummaryData maps defined with dynamic sparse members an issue on hybrid cubes
With the introduction of hybrid to Planning Cloud cubes, it is challenging to define data maps that do not include a reference to a dynamic sparse member. Whether defining a source dimension definition as Descendants of a sparse dynamic “Total” member or defining it as Level 0 Descendants of a sparse dynamic “Total” member, the data map validates only the member referenced in the relationship function as sparse dynamic and then will error as an invalid selection. Ideally the full list of members defined in the relationship function would be evaluated and would be considered valid if one or more members are stored.