Hi Lotsaram and Mark, thanks for taking time to read and answer my post, I am aware that MDX is another way to create a temp subset for a temp view (removed the view in epilog in TI), the code was developed by a developer which I just admin the TM1 model. Mark's point is to create a zero-out view process that fit all cubes, do I understand him correctly?
1) The code does have a loop using tabdim to obtain every vTgtdim for the view, I extracted only one dimension of the view which I do not need all 0 children, I need to put a filter to exclude certain children to insert into the subset. 1090-1000 is the principal name of the element, not an alias, I used subst(vTgtelement, 5,4), not working either.
2) The weird thing is that I removed the view and subset destroy code in Epilog, so the view got generated, I can see what elements are in the account dim subset, I saw 1090-1000 did not get excluded, but when I used the zero-out view as a data source, played below code, I did not text output 1090-1000.
Code: Select all
## starting position 6, length 4 retrieved the last four digit subacct. correctly
#ASCIIOUTPUT(vFile, vstring, h_accounts);
3) I recently ran into an issue that I used a MDX to create a temp subset, then included it in a temp view, but I can not delete the temp view because it is not a static subset, even I put 1 in the end of SubsetCreatebyMDX(SubName, MDX_Expression,1) per some suggested, I ended up not getting the dynamic subset I intended to build, I will create another thread to discuss it when I have a chance.
4) I will use planning sample to create a test cube to see whether I can reproduce the same issue there today. We recently did TM1 server p2v, hope the issue is not related to that.