Not getting result while test the dimensional package?

[vignesvar]

Hi friends,
I'm working FM 10.2. To created relational model there is no problem while test the query subject even together all query subject. Then I designed dimensional model from the relational model. When I test the result all dimension produce result except the dimension "WORK_EFFORT". To test this dimension taking too long time to testing result yet not display instead of displaying retrieving information. It is happened only this WORK_EFFORT dimension. Please help me to overcome this issues.
Note:
WORK_EFFORT is dimension name, WorkEffort is hierarchy name, Work and Work purpose are level of the dimension.

Thank you, 

[MFGF]

Hi friends,
I'm working FM 10.2. To created relational model there is no problem while test the query subject even together all query subject. Then I designed dimensional model from the relational model. When I test the result all dimension produce result except the dimension "WORK_EFFORT". To test this dimension taking too long time to testing result yet not display instead of displaying retrieving information. It is happened only this WORK_EFFORT dimension. Please help me to overcome this issues.
Note:
WORK_EFFORT is dimension name, WorkEffort is hierarchy name, Work and Work purpose are level of the dimension.

Thank you,

How many rows in the underlying table(s) need to be spanned to populate the hierarchy? Are they all from one table or from the results of joins across multiple tables? Are there any complex calculations in the attributes of either level?

MF.

[vignesvar]

Hi MFGF,
Thank you for your response, WORK_EFFORT is a single table. Around 17 k records presents in a table. No, complex calculation in this level.

[MFGF]

Hi MFGF,
Thank you for your response, WORK_EFFORT is a single table. Around 17 k records presents in a table. No, complex calculation in this level.

Ok - what about the parent/child relationships in the hierarchy? On average, how many child members belong to a parent member?

MF.

[vignesvar]

Hi MFGF,
Work_name as parent, work_purpose as child element. A parent should contain only one child from four children.

[MFGF]

Hi MFGF,
Work_name as parent, work_purpose as child element. A parent should contain only one child from four children.

Hi,

Sorry - I don't follow. What does "only one child from four children" mean? A parent has one child member? A parent has four child members? Something else?

What structure is the table? Is it a parent/child schema (ie there is a "parent" column identifying what parent a row has) or are different levels from different columns?

MF.

[vignesvar]

 In row wise Work_name as parent, work_purpose have four value(Retainer, support, bug, feature) as child. work_purpose is depend on the type of work.
Example:
work_name     work_purpose
error                  bug
create                feature
move                 support
like that.

getting measure value to link to another dimension name as work_Assign it is link to the dimension name as time. In work dimension having this attribute work_name followed by work_purpose.

Thank you for response MFGF.

[MFGF]

In row wise Work_name as parent, work_purpose have four value(Retainer, support, bug, feature) as child. work_purpose is depend on the type of work.
Example:
work_name     work_purpose
error                  bug
create                feature
move                 support
like that.

getting measure value to link to another dimension name as work_Assign it is link to the dimension name as time. In work dimension having this attribute work_name followed by work_purpose.

Thank you for response MFGF.

So does the table have this structure:

work_name   work_purpose
Error               Retainer
Error               Support
Error               Bug
Error               Feature

or does it have this structure:

row_id   description      parent_row_id
4            Error                        2
5            Retainer                  4
6            Support                  4
7            Bug                        4
8            Feature                  4