Rule from different dimension with same elements.

[tomok]

In the Provider cube:
[]=N:DB('Occupancy_cube','Provider_UBR,!Provider_region,!GBS_month,!GBS_Version,!GBS_Year,!Provider_FSI');

In the Occupancy cube:
[]=>DB('Provider_cube','Occupancy_UBR,!Occupancy_region,!GBS_month,!GBS_Version,!GBS_Year,!Occupancy_FSI');

[qml]

help me.

Mate, you pretty much sabotaged any attempt to do just that. I'm really impressed by tomok and Gregor, who decided to fight the fight and help you no matter how hard you were trying to make it.

[Gregor Koch]

tomok, I thought about bringing up the according feeders as well...but looking at one of the screen shots, I'd bet that the OP will get a compile error cause it's missing a certain something. Seemingly the Cricket scores are more important than the TM1 Rules Guide or any sort of documentation on TM1.

qml, it's one of these situation where it's bound to fail but I don't want TM1 to take the blame for it. On the other hand I ask myself whether I really want to keep helping people who have no idea about TM1 but who are the cheap replacement for somebody who would get the job done (by him/herself).
I appreciate that more and more people are trying to learn TM1 but in this case I don't really see any attempt to learn or to provide all the needed information.

[charan]

Gregor.
Thank you very much for your support.
But please do not say help is not required in my situation. I am alone in this project trying do that but i am facing errors.
That is why I have posted.
The rule is still giving errors.Find the attachment.

[charan]

please any suggestions for this

[Alan Kirk]

Gregor.
Thank you very much for your support.
But please do not say help is not required in my situation. I am alone in this project trying do that but i am facing errors.
That is why I have posted.
The rule is still giving errors.Find the attachment.

I think that a few things need to be clarified.
First, the objective of the forum isn't to dump on new users. And if you look through the majority of threads you'll see that that doesn't generally happen. Questions are welcome, new users are welcome.
However, and this is a big however... given that the people who are answering the questions are giving up their valuable time to do so, there are certain expectations. In particular, that:
(a) The asker put in at least a reasonable effort to find an answer for themselves and not automatically resort to asking here for things that could be found in a couple of minutes worth of searching in the manuals;
(b) When the asker is asked for further information, they provide that information. (I'd also add that requests or suggestions not be ignored, but that's more in relation to another poster that I can think of who isn't particularly new and should know better by now.)
(c) That all relevant information be supplied in the original question.

In short, that the Request For Assistance Guidelines be followed.

The information that Tomok asked you for in his very first post was the information that was needed to resolve the issue, but instead of supplying that you supplied some screenshots which didn't give it. Then you rubbed salt into the wound by saying that you had supplied the information which, in fact, you hadn't. That's bound to put some noses out of joint.

Nobody's saying that you don't need help but the other issue is that you don't seem to have done one main thing to help yourself, which is to read through the Rules Manual because you seem to be missing some basic understanding of how rules work.

(And in relation to your follow up question, bear in mind that it's Easter weekend. Even TM1 gurus have down time occasionally.)

Now, turning to your specific question, consider the following:
(a) You are creating the rule in the Provider_Cube, right?
(b) The rule is pulling a value from the Occupancy_Cube via a DB function.
(c) The DB function must contain the name of an element for each of the dimensions in the Occupancy_Cube, agreed?
(d) Now the question is where to get the names of those elements.

You have two choices. You can either hard code an element name by putting it inside single quotes. Or, you can derive the element name from an element that exists in a corresponding dimension in the Provider_Cube. As others have already explained, you do that by putting an exclamation mark before the dimension name.

Now look at what you've typed; []=N:DB('Occupancy_Cube', is OK, but the next bit is !Occupancy_UBR. You are telling the rule to take the element from the Occupancy_UBR dimension and pass it into the DB function. BUT... the Provider_Cube doesn't have the Occupancy_UBR dimension in it. It has the Provider_UBR dimension. Consequently the rule has no idea what you are talking about, because you need to supply the source of the element name to the DB() function. You therefore need to use the expression !Provider_UBR, not !Occupancy_UBR. When the DB() function does the lookup it'll punch that element into the formula to seek the corresponding !Occupancy_UBR element. The same situation will occur with the _FSI dimension. If you look at Tomok's post at the head of page 2 of this thread, you'll see that he has in fact told you this. Try making the change to those two dimension names in your formula and see what the outcome is.