Hi all,

I recently used the following MDX query to create a dynamic subset for a view in a TI process:

MDX
FILTER(    TM1FILTERBYLEVEL(TM1SUBSETALL([Months].[Months]), 0),    [Months].[Months].CURRENTMEMBER.NAME >= "07")

This query effectively filters leaf members in the [Months] dimension to include only those starting from "07" 

This is a very simple, but helpful MDX, for example in case you want to create a dynamic view to zero out the rest of the year before you import new data to a cube. 

I'd like to appeal to IBM to enhance the IBM Planning Analytics MDX documentation.

Including real-world examples, such as filtering dimension members (e.g., months >= a specific value), would significantly improve the usability of the documentation.

It is also worth mentioning the impact of multiple hierarchies on the MDX code.

Thanks for considering this!

Hi all,

I recently used the following MDX query to create a dynamic subset for a view in a TI process:

MDX
FILTER(    TM1FILTERBYLEVEL(TM1SUBSETALL([Months].[Months]), 0),    [Months].[Months].CURRENTMEMBER.NAME >= "07")

This query effectively filters leaf members in the [Months] dimension to include only those starting from "07" 

This is a very simple, but helpful MDX, for example in case you want to create a dynamic view to zero out the rest of the year before you import new data to a cube. 

I'd like to appeal to IBM to enhance the IBM Planning Analytics MDX documentation.

Including real-world examples, such as filtering dimension members (e.g., months >= a specific value), would significantly improve the usability of the documentation.

It is also worth mentioning the impact of multiple hierarchies on the MDX code.

Thanks for considering this!