TM1 Forum

Hello all,

i used nested DB for my current task which is min salary as per grade.
In my first cube i included grade element in measure diemension and also created picklist into grade element like 1 2 3 4 5.
and in my second cube 1r_Salary_Count, Min salary value is there for 1 2 3 4 & 5 Grade.

I used nested DB() like this
['Min Basic' ] = N: DB('1r_Salary_Master', DB('1r_Headcount', 'Grade', !t_Period, !v_Version, !1h_Hierarchy), DB('1r_Salary_Master', !v_Version, 'Min Salary'));

But the value doesnt get fetched??

is it correct form of using nested db??

If the measure is a Numeric element then it will need to be converted to string before being used as an element name.

which element??
Grade??

If the "grade" element where people choose the picklist drop down is an N element it can not be directly used in a DB statement.
You can either swap it to an S element which I probanly would as you don't get much benefit from it being a number. Or you could convert it to string within the rule which would be less efficient but still functional.

It could of course be something completely different but on the little information you have given that would be the first thing I would be inclined to check.

Declan is very likely right. The DB() function only takes strings as parameters. So if another, nested DB() function returns a number it will need to be converted to a string before being injected as a parameter for another DB(). To convert a number into a string use the STR() function.

can u plz tell me how to attach screenshots to this reply??

i mean if i want to attch screenshot with post in this forum??

Abhi30 wrote:can u plz tell me how to attach screenshots to this reply??

i mean if i want to attch screenshot with post in this forum??

Below the post window there's an area with Options and Attachments tabs. Go to Attachments, click 'Add files' and then 'Place inline' once your upload is finished.

Abhi30 wrote:which element??
Grade??

No. Specifically, not Grade.
In the code sample you provided 'grade' is a hardcoded string so we have to assume this is a fixed reference and an element name in the 2nd dimension of the 1r_Headcount cube.
DB('1r_Salary_Master', DB('1r_Headcount', 'Grade', !t_Period, !v_Version, !1h_Hierarchy), DB('1r_Salary_Master', !v_Version, 'Min Salary'))
but is this the actual code? ... because you seem to have some kind of weird circular reference . You are looking up a value in 1r_Salary_Master with a nested DB from the same cube. How many dimensions does 1r_Salary_Master have? and what are they? because your "lookup" looks very odd indeed. From the DB ref it looks like 1r_Salary_Master has 2 dimensions being v_Version and I assume a measure, yet v_Version is being looked up from 1r_Headcount which has MORE dimensions INCLUDING v_Version. Well that just doesn't make sense, not even a tiny speck.

If you need help (and just the dimension names alone indicate that you do because it seems pretty clear that the "solution architect" of this model's knowledge of TM1 could be written on a postage stamp) then I suggest you include screenshots of the 3 cubes showing the dimensionality and a proper description of what you are trying to do.

qml wrote:Declan is very likely right. The DB() function only takes strings as parameters. So if another, nested DB() function returns a number it will need to be converted to a string before being injected as a parameter for another DB(). To convert a number into a string use the STR() function.

Have a look at the nested DB with references to 1r_Salary_Master within 1r_Salary_Master. Beyond ensuring the data is type string it would seem likely that there could be a fundamental error of wrong cube reference or missing/wrong dimensionality.

here i am attaching my 2 cubes..

if u can see their is a grade element in Headcount cube
i just want to do if i select grade 6 in that element

then the value should be fetched from 2nd cube which is salary master

You don't need the second nested DB(). Something like below should work, provided you store Grade in 1r_Salary_Master as a number. If you store it as a string then you don't need the STR() treatment.
You will also need to supplement it with a feeder, but in this case I would not do an intercube feeder and just feed within 1r_Salary_Master from 'Grade' to 'Min Basic'.

Edit: You will also need a v_Version reference in the rule somewhere, like in Wim's code, but it's impossible to know from your screenshots what the order of dimensions in your cube is.

Please help the helpers. It's worthless to show a screenshot of cube names and dimension names,
if we cannot see what dimensions go in what cube. Including, the order of dimensions in each cube.

1 step in the good direction, a guess (of course):
I assume measures dimensions to be the last in the cube.

Please do not waste your own time by guessing and trial and error. Read the documentation on the DB function, and follow training courses. This is basic TM1 rule writing.