String values are not shown in my cube

[smile_netz]

Hi All,

I'm still quite new to TM1 world so please bear with me.
I have an issue here of showing string values to my cube. It sounds easy but I don't know why the string values don't show up in my case.

Here is the scenario:
TM1 Architecture 9.5.2 (with hot fix 2)
Cube Criteria - Cost Centre (hierarchical organisational chart) & Period
Column : Names
Rows : Measures (StringA, StringB, Amount, etc...)

----------------------------------
Cost Centre Dropdown values:
DeptAParent (consolidated element)
DeptAChild1 (consolidated element)
DeptAGrandChild1 (base element)
DeptAGrandChild2 (base element)
DeptAChild2
etc ...

----------------------------------

TI Process: From CSV to CubeA
*** All codes are system generated.

----------------------------------

Things tried:
1. Using the ATTRS in the TI process, the StringA value is populated
Example: Using the Criteria DeptAGrandChild1 & Period1, the StringA value is shown BUT when you choose its parent with DeptChildA, StringA DOES NOT show the value anymore.

To solve it, I have to do it in the rules and comment out the CELLPUTS I have created in the TI because it will have the error "Cell applies to the rule"

2. This is the code I put:
SKIPCHECK;
['StringA' ] =S: IF(ELLEV('Name', !Name)=0, ATTRS('Name', !Name, 'Status'), '');
FEEDERS;

*** StringA NO longer shows any value even in the base level

3. StringB is not populated in the parent level. How can I retain the value using the rule?

Please point out what is wrong with my code.

Thanks in advance for your help.

[winsonlee]

is your measure dimension the last dimension in the cube ?

[smile_netz]

Yes, My cube dimensions: CostCentre, Names, Period, Measure

[lotsaram]

Using the Criteria DeptAGrandChild1 & Period1, the StringA value is shown BUT when you choose its parent with DeptChildA, StringA DOES NOT show the value anymore.

Maybe you haven't described your "issue" very well but from my reading it seems your problem is that you are expecting string values to consolidate and display for parents when loaded to a child. This can't work and simply shouldn't be expected to work as string values can't be consolidated, if siblings have different text values then what should the value of the parent be? Therefore string values can be loaded at any dimension level, to a string all cells are like leaf cells.

Using rules you can fairly easily force a text value down to all descendants but going the other way is more difficult as elements can have multiple parents and as already mentioned siblings could have different values, so which one so you take ...

[smile_netz]

I do not expect the String to be Consolidated as there is no way it will be consolidated.
The requirement is simply to have that value into the cell even if the criteria chosen is the parent.

Example:

Criteria chosen is the base cost centre : DeptAGrandChild1 and Period1
*** The Cube shows the value F on the StringA Measure (Below is how the cube looks like)
StringA
Name1 F

Criteria chosen is the parent cost centre : DeptAChild1 and Period1
*** The cube shows the value empty on the StringA Measure (Below is how the cube looks like)

StringA
Name1

Issue: StringA measure should still show the value F

[Martin Ryan]

Sounds to me that what you're describing is exactly as lotsaram is suggesting, you're expecting the parent to show the same thing as the child. That doesn't happen in consolidations for text.

For a more concrete example let's say you have a Country dimension with elements "World", "USA" and "UK". From what I can gather you are saying that if "USA" says "Sales up", and you choose "World", then you'd expect "World" to show "Sales up" as "USA" did. TM1 simply won't do that.

Text doesn't consolidate, and for good reason. In my example, say "UK" says "Sales down", what would you expect "World" to say in light of the two contradictory statements?

If we're still not getting what you're saying then perhaps try screenshotting a picture of the cube as it stands at the moment and where you expect to see different text information so we can get a clearer understanding of what you're trying to achieve.

Martin

[Duncan P]

The key thing is that a string will only show for a non-leaf string cell if
1. there is a specific S: rule statement (not STET) defining it for that cell
2. someone or something has put a string in that actual cell

So if your process is putting strings in non-leaf cells and they are not showing that is interesting.
If you are expecting the non-leaf cell to show the string put in the leaf cell below it the questions is which leaf cell?, the first? the last?, on which dimension?

It might be helpful to see the source data CSV and the import process. Is it possible for you to upload these?

Duncan.

[smile_netz]

Thanks for all your replies. Here are the screenshots:

[Martin Ryan]

So are you expecting to see this then?

tempPicture.JPG (27.62 KiB) Viewed 7193 times

This won't happen because text information won't get consolidated, as lotsaram and myself have outlined above.

What you could do is load the gender against the employee as an attribute then write a rule that says
['Employee Type'] = S: attrs('Employee', !Employee, 'Gender');

Though I'm not sure that really makes a lot of sense to repeat the information all the time. The other option is make "F" and "M" consolidations in the Employee dimension.

Martin

[smile_netz]

I could say to the users that this is a limitation of TM1, but the argument is:
"Manager A who is in Cost Centre Taylor Village supervises Cost Centre 3553. Therefore, whatever values in the Cost Centre 3553, he should be able to see because in reality, Employee A still reports to him even if Employee A's supervisor is in Cost Centre 3553."

Things I tried in the rule:
1.
SKIPCHECK;

['Employee Type' ] = S: ATTRS('Employee', !Employee, 'Status');

FEEDERS;

*RESULT: Empty value is shown EVEN FOR THE LEAF! ((((

2. Removed the SKIPCHECK and FEEDERS
['Employee Type' ] = S: ATTRS('Employee', !Employee, 'Status');

* RESULT: All rows were populated with correct Status BUT ALL Employees are now displayed despite of the suppress 0 which is more wrong because it displays ALL ROWS

3.
SKIPCHECK;

['Employee Type' ] =S: IF(ELLEV('Employee', !Employee)=0, ATTRS('Employee', !Employee, 'Status'),'');

FEEDERS;

*RESULT: Empty value is shown EVEN FOR THE LEAF! ((((. Same as #1.

I'm so out of ideas anymore!

[Martin Ryan]

"Manager A who is in Cost Centre Taylor Village supervises Cost Centre 3553. Therefore, whatever values in the Cost Centre 3553, he should be able to see because in reality, Employee A still reports to him even if Employee A's supervisor is in Cost Centre 3553."

That's a permissions argument, not an argument for why text should consolidate. Text should not consolidate. I guess you could choose to view that as a limitation of TM1 if you want to, but I'd view it as a limitation of text.

The only reason why this particular bit of text can logically be the same up the hierarchy is because the information is one dimensional. Employee A is "F" irrespective of where she is. No other dimension will ever change that.

As for the reason it's not getting displayed it's because you've got a rule without a feeder. You can search for feedstrings to resolve this.