Hi,
Not sure about the specific issue but you don't need the UNION as the following should work:
{EXCEPT(
{TM1SORT( {TM1FILTERBYLEVEL( {TM1SUBSETALL( [Business Lines] )}, 0)} , ASC )},
{ TM1FILTERBYPATTERN( {TM1SUBSETALL( [Business Lines] )}, "No *"), TM1FILTERBYPATTERN( {TM1SUBSETALL( [Business Lines] )}, "Input *")}
)}
I tend to use this approach, i.e. including the Excepted sets within curly braces and separated by commas, rather than nesting the EXCEPTS.
regards,
Mark
------------------------------
Mark Wragg
------------------------------
Original Message:
Sent: Wed March 09, 2022 01:25 PM
From: Bruna Garcia
Subject: MDX with nested { EXCEPT ( functions stopped working
We have had this subset in place for quite some time; on Feb 24th, we started to receive this error.
After comparing the MDX in architect vs what was rendering in PAW, it looks like it is reading as 3 EXCEPT statements, vs the 2 that are really in there.
Is there any reason this MDX should not work? MDX's with nested EXCEPT statements no longer work through PAW.
We implemented a workaround with this updated MDX.
{ EXCEPT ( {TM1SORT( {TM1FILTERBYLEVEL( {TM1SUBSETALL( [Business Lines] )}, 0)} , ASC )}, { UNION ( { TM1FILTERBYPATTERN( {TM1SUBSETALL( [Business Lines] )}, "No *")}, { TM1FILTERBYPATTERN( {TM1SUBSETALL( [Business Lines] )}, "Input *")} )} )}
------------------------------
Bruna Garcia
Master Consultant
QueBIT Consulting
------------------------------
#PlanningAnalyticswithWatson