Request to enable the clearance of asymmetric MDX views when data processing.

Asymmetric MDX represent the general case of a data set in PA, an Asymmetric view is typically delivered with and MDX filter.

The ViewZeroOut function currently does not support the clearance of MDX views that contain a filter statement.

The lack of support for this can result in significantly increased processing times and more complex control structures when data processing.

For example this MDX views

SELECT NON EMPTY {{[M SalesCube2].[M SalesCube2].[Value]}}  ON 0, 
Filter( NONEMPTY ( {TM1FILTERBYLEVEL(TM1SubsetAll([actvsbud].[actvsbud]), 0)} * 
{TM1FILTERBYLEVEL(TM1SubsetAll([region].[region]), 0)} * 
{TM1FILTERBYLEVEL(TM1SubsetAll([model].[model]), 0)} * 
{TM1FILTERBYLEVEL(TM1SubsetAll([account1].[account1]), 0)} * 
 {TM1FILTERBYLEVEL(TM1SubsetAll([month].[month]), 0)} ) 
 ,[M SalesCube2].[M SalesCube2].[ToKeep]=0) 
 ON 1 
FROM [SalesCube2] 

Does not result in the cleance of the correct intersections.

If there are any concerns about changing the way the current ViewZeroOut function works with simple MDX views and performance impact then perhaps a new function could be introduced for use with MDX views that are asymmetric.

I have posted a more detailed write-up here https://www.tm1forum.com/viewtopic.php?t=16467, as it is hard to get his message across without screenshots.

This has been raised and rejected as a defect, since the function is performing as designed even though it clearly does not do what it says on the tin. (TS011806219 / PH52896 )