Fill s-Elements in the 1st Dimension

恭喜发财1

Hey there,

I am experiencing difficulties to write strings into my cube.

The cube contains 6 dimensions. I want to add a text into the 1st dimension in an s-Element (in perspectives). However, even though I chose n-elements on all other dimensions - the desired input-cell stays gray (as in not writable). If I choose another cube where the text-input-element is contained in the last of all dimensions it is writable. Does anyone know a solution to this phenomena?

Thank you in advance and with best regards,
Konstantin

P.S.: I am using the latest Hotfix of 9.4.1

玩美123

Konstantin

To load values in a cube onto an s-type element, that s-type element must be part of the last dimension of the cube. If not, it will default to capture only numeric values (but still be a white cell at the lowest level in the cube and a gray cell for consolidations, for example).

Wim

krc

Hello Wim,

thank you for your answer. That implies though, that there is no work-around?
I mean other than a copy of the cube with  a different order of the dimensions?

zerofeng111

rks1 wrote:That implies though, that there is no work-around?

Konstantin,

Only the last dimension in the cube can be used to define the measure type.

If you have created the cube with the dimension order, a work-around would be to use the "Re-Order Dimensions" feature to change the last dimension in the cube to your measure dimension. Jut right-click on the cube and you'll find the option.

This internally re-orders the dimensions and will make the measure dimension take precedence in determining the cell type. However, be warned that it is a little confusing for users, as the order shown in TM1 Perspectives will be the original dimension order, not the updated one.

This kind of thing shows a degree of inexperience, so perhaps it might help you to adopt a few "best practice" techniques on your project, to avoid development and maintenance issues in the future.

For instance, my own methodology is to have a measure dimension for each cube (even if there's only one measure), and to always name the measures dimension as the cube name followed by the word "Measure". This makes sure it is clear in both the dimension list and the cube that the function of the dimension is to contain measures.

If you're interested in some conventions to use, I wrote a  a while ago that covers some good practices for developers. At the conclusion of the article, I have a sample document detailing naming conventions for TM1 objects.

You'll find it very helpful as you get further into the project to adhere to a naming convention and perform as much standardization as you can upfront.