I have a problem getting a measure populated correctly. I’m converting a Transformer powercube into a TM1 cube. In the powercube there are two measures which are populated with two different query’s. One query has all the IDs to relate to all the dimensions, but the other query does not have all the IDs of the dimensions. In Transformer this is handled automatically, but how do I do this in TM1?
I have tried this in a TI process, but this forces me to create dummy IDs for the missing dimensions and this is not resulting in the correct values. Now I have created a rule using a lookup cube, but this does not retrieving any data.
The primary cube has correct values for all the dimensions and the first measure.
The lookup cube has correct values for the second measure and a subset of the dimensions of the primary cube.
The rule for populating measure2 in the cube is as follows:
['Measure 2'] = N: DB('lookup_cube', !Dim1, !Dim2, 'Measure 2');
What am I doing wrong? I’m just starting with TM1, so struggling with this.
Thanks in advance.
Rule with lookup cube
- jim wood
- Site Admin
- Posts: 3961
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Rule with lookup cube
TM1 works by mapping values to every dimension in the cube as you've more than likely already guessed. So you need to fll the gaps which is what you're trying to do.
A TI with a lookup cube or a rule, both will do the job. This is something you come across all the time in TM1 when 2 cubes have differing dimension numbers, so say detail to summary.
You started with the right approach, but here is what you need to change for your rule:
The exmaple above asumes that dims 1-3 are common between the 2 cubes. It is then mapping via a lookup for the other.
I hope this helps,
Jim.
A TI with a lookup cube or a rule, both will do the job. This is something you come across all the time in TM1 when 2 cubes have differing dimension numbers, so say detail to summary.
You started with the right approach, but here is what you need to change for your rule:
Code: Select all
['Measure 2'] = N: DB('Other Cube',Dim1,Dim2,Dim3,Dim4,DB('lookup_cube', !Dim1, !Dim2, 'Measure 2'));
I hope this helps,
Jim.
Struggling through the quagmire of life to reach the other side of who knows where.
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7