TM1 Forum

Hi all,
my first post here and kind of a newbie to TM1 PA.
I have created a dynamic subset filtered attribute(YearNo attribute on Employee Dim, and attribute value is an element from other dimension (Year dimension). When i placed the Employee DIM as Row or column its working fine based on the Year Dim filter which is at TITLE. however its not working when i placed both the EMPLOYEE and YEAR dimensions at TITLE (context).
Dim1 - EmployeeOrguHR and YearNo is attr
Dim2 - Year and YearNo_txt is an attr
following is the MDX on EmployeeOrguHR dimension

{FILTER( {TM1SubsetBasis()}, [EmployeeOrguHR].[YearNo] = [Year].[YearNo_txt])}

Highly appreciate any suggestions.

First thing to do is correct the MDX - TM1SubsetBasis() is probably unknown in this context - typically added when recording MDX.
Replace that with the [dim].[member] or set you are starting from and try again.

Hello,

Please read this lengthy page on MDX:
https://www.wimgielis.com/tm1_mdxstatements_EN.htm

Hi, what interface are you using?
If it is tm1web, it will not work. such dynamic subsets work only when Year is in context and Employee is in rows/columns
"Both dims in filters" will work only in PAW (until you drag them out of the view to external selector widget)

gtonkin wrote: ↑Fri Jan 21, 2022 10:24 am First thing to do is correct the MDX - TM1SubsetBasis() is probably unknown in this context - typically added when recording MDX.
Replace that with the [dim].[member] or set you are starting from and try again.

Thanks for the response @gtonkin
i have used the following MDX later on, but still the same issue.

{FILTER( {TM1SUBSETALL( [EmployeeOrguHR] )}, [EmployeeOrguHR].[YearNo] = [Year].[YearNo_txt])}

Elessar wrote: ↑Fri Jan 21, 2022 12:34 pm Hi, what interface are you using?
If it is tm1web, it will not work. such dynamic subsets work only when Year is in context and Employee is in rows/columns
"Both dims in filters" will work only in PAW (until you drag them out of the view to external selector widget)

Thank you for the response @Elessar, apologies for the late response.


This is for PAW only, it is working fine when both YEAR and EmployeeOrguHR Dimensions in TITLE/filter. however, as you said, it is not working when i Drag EmployeeOrguHR dim out of the view and made them as a external filers(generic filters for multiple widgets on the same dashboard).

Is there any way to get that working? either by changing the MDX or changing something in PAW?
Thank you

Wim Gielis wrote: ↑Fri Jan 21, 2022 12:28 pm Hello,

Please read this lengthy page on MDX:
https://www.wimgielis.com/tm1_mdxstatements_EN.htm

Thank you @Win Gielis, looks an amazing document. apologies for the late response.

hisathishkumar wrote: ↑Mon Jan 24, 2022 11:39 pm
Is there any way to get that working? either by changing the MDX or changing something in PAW?

No. Somebody has already asked this on IBM community forum: IBM said that when you drag filter to external widget, MDX becomes disconnected from view.

Elessar wrote: ↑Tue Jan 25, 2022 7:12 am

hisathishkumar wrote: ↑Mon Jan 24, 2022 11:39 pm
Is there any way to get that working? either by changing the MDX or changing something in PAW?

No. Somebody has already asked this on IBM community forum: IBM said that when you drag filter to external widget, MDX becomes disconnected from view.

Thank you for the quick response.
i came across the following article,they say it works when both are at Title, tried this logic, its throwing an error "Invalid MDX expression".

https://quebit.com/askquebit/IBM/how-to ... cube-view/

Thanks

Hi,

As Ellessar has said twice already, what you are trying to do will NOT work if both dimensions are dragged outside the cube view.

I posted about this issue here, please read the whole thread:

https://community.ibm.com/community/use ... gestviewer

Hopefully IBM will resolve this at some point but feel free to add a comment saying you have the same problem, might help speed things along.

My workaround was to create some client attributes, have those as the selectors on the page and let the mdx reference those instead.

regards,

Mark

Mark RMBC wrote: ↑Tue Jan 25, 2022 10:37 am Hi,

As Ellessar has said twice already, what you are trying to do will NOT work if both dimensions are dragged outside the cube view.

I posted about this issue here, please read the whole thread:

https://community.ibm.com/community/use ... gestviewer

Hopefully IBM will resolve this at some point but feel free to add a comment saying you have the same problem, might help speed things along.

My workaround was to create some client attributes, have those as the selectors on the page and let the mdx reference those instead.

regards,

Mark

Thanks Mark, will try your workaround suggestion .