Hello all,

In a project, TI processes are used to update dimensions, whereby all consolidated elements are removed completely. Not only unwound. That's not my choice, it's the customer's choice. They use TM1 for 30+ years.

As a consequence, in static subsets, consolidated elements will disappear.

One easy solution would be to create a subset, select the elements manually, and save the subset containing the MDX (which is generated in real time and is correct).

However, in cases where the subset is just a simple list of elements, the MDX is not saved. In the *.sub subset file, the subset shows as static with the selected elements, not the MDX representation.

Hence, we are stuck. One workaround is creating subsets with TI: not a viable solution.

Another workaround is inserting fake MDX to trick PAW. It's even worse as a solution.

For instance, this works:

Union( {[Period_01].[Period_01].[fake element]}, {
[Period_01].[Period_01].[202001],
[Period_01].[Period_01].[202002]
})

But this does not (becomes static):

{
[Period_01].[Period_01].[202001],
[Period_01].[Period_01].[202002]
}

Any ideas @Svetlana Pestsova, @STUART KING

In Architect we could save subsets with an MDX for 40 years ;-)

------------------------------
Wim Gielis
Senior Consultant
Aexis International
Sint-Stevens-Woluwe
0496225001
------------------------------

Hi Wim,

I am a bit scared that changing this behaviour in workspace could have all sorts of ramifications, so I am not sure it is something you will see in the next release!

I know you said TI is not viable but...

Deleting the consolidations and then rebuilding them is pretty standard in my experience.

Now that workspace is used more and more we keep all our subset definitions in a cube, we define the subset name, the mdx, whether it should use an alias, whether it should be dynamic or static, among other things.

We have a process, whose data source is the aforementioned subset defintions cube, to build all the subsets, and this includes a pDimName paramater so it can be run for all or a single dimension.
The process uses SubsetCreateByMDX for every subset it builds but converts to static where the static flag is set to yes (well actually it makes every subset static unless the dynamic flag is set to yes).

We call this process where relevant, e.g, during dimension updates.

Any time we want to add a new subset we update the cube, and run the process.

I think this approach is the way to go, as having the mdx in a cube means the mdx is not lost.

regards,

Mark