TM1 Forum

Hello,

Here is the situation, I have a cube that is going to send information to metric designer about wich order the elements in the lines are going to be displayed.

Once it's ordered by this cube, I need to validate if the user won't enter the same order in two or more of these elements.

Is there any way to do this? Like a validation at the Commit button or something?

I tried:

Once I realized that on the Control Cube }ElementAttributes of each dimension you CAN'T repeat the Alias, when you recalculate the Alias changes to the previous valid value automatically. So I tried creating an Alias for the dimension in the lines and use Rules to send values to the }ElementAttributes cube of the dimension.

This way TM1 won't change the Alias in the cube back to a previous valid value.

Does anyone have an idea if this kind of validation is possible, don't forget that I need it automatic so if the only way to test the cells is running a process, is there a way to run it while recalculating or commiting data?

Thanks in advance.

You have me stumped. I have absolutely no idea what exactly you are trying to do or why. Maybe try explaining step by step with some illustrations?

lotsaram wrote:You have me stumped. I have absolutely no idea what exactly you are trying to do or why. Maybe try explaining step by step with some illustrations?

ditto - you could look at creating a validation cube, or put some conventions such as using long numbers as the dimension? order(i.e. 1400), so that there is space to insert elements between existing(i.e. 1405), without the need to cascade the shift in order.

It is important to provide us with an indication of scale and frequency of changes likely to the order.

For the validation cube, I would create an order dimension and intersect it with the base dimension. The base dimension would require a condsolidation so that if the sum of the base dimension is greater than 1 for any given order element, then there is an issue.

Unfortunately, the limitation of using rules is circularity, so that you can't change the input based on the output. Identifying issues is easy with validation rules, however, the issues are best fixed with a process.

I do not have high expectations for a tidy solution to your problem.

Hello captnknz,

Yes I forgot about the frequency of changes...

Well, it's going to happen a lot imagine a cube on TM1 that is going to send information to Metric Designer, this information will be used to create Metric types, order of the KPIs, etc...

The order that the KPIs are going to be displayed depends on the purpose of the Meeting. So they want a "beautiful" application (TM1 Contributor) to change these settings. Then they'll be able to change before the Meeting run a process to change the KPIs' attributes.

I'm going to think about creating another cube with numbers in the lines and only one column where the user select the KPI in a Picklist. \but it may cause some trouble after...

Thanks.

Lotsaram,

I understand how you feel... This application is big that's why it's difficult to me to explain...
But I found that there is no way to check if a same value was set to more than one line in the same column of one cube, only with a TI process and that won't solve our problem completely.


By the way...

Any one of you have idea if it's possible to allow Copy/Paste in TM1 Contributor views?


Have a nice week.