Employee Dimension is not showing all the nodes while browsing

  • I have a Employee DImension. It has four columns EmployeId,Employee Type,First Name & Last Name. EmployeeId is a unique column. All four columns makes a row unique. There can be a duplicate value for First & Last Name but with different Employee Type (Permanent or Temporary). I have select Employee Type, Last Name & First Name in Hierarchy and Attribute relationship is
    Employee Id  --> First name --> Last Name --> Employee Type. I have successfully Deployed and Processed the dimension. While browsing the data it is not showing all the columns for some employees (it is ONLY displaying the Last Name) and also in case there are multiple employees with same LastName and different First Name, it is displaying the selective names.

    Please advise how to resolve this problem.

    Thanks,

    Anil

  • amurjani - Friday, February 24, 2017 10:31 AM

    I have a Employee DImension. It has four columns EmployeId,Employee Type,First Name & Last Name. EmployeeId is a unique column. All four columns makes a row unique. There can be a duplicate value for First & Last Name but with different Employee Type (Permanent or Temporary). I have select Employee Type, Last Name & First Name in Hierarchy and Attribute relationship is
    Employee Id  --> First name --> Last Name --> Employee Type. I have successfully Deployed and Processed the dimension. While browsing the data it is not showing all the columns for some employees (it is ONLY displaying the Last Name) and also in case there are multiple employees with same LastName and different First Name, it is displaying the selective names.

    Please advise how to resolve this problem.

    Thanks,

    Anil

    Firstly, what benefit is there in having First Name and Last Name in a cube at all, let alone a user-defined hierarchy? Is there ever going to be a time when someone asks "How many employees of x surname have x fact"?
    Anyway from the behaviour that you describe it seems like either one of two things is happening; 1, the hierarchy is behaving as expected (grouping last names together etc.) 2, you have not set up composite key columns for the attributes correctly. 

    I would re-evaluate your modelling here. Perhaps have the first and last name attributes as properties of a key and then disable them.


    I'm on LinkedIn

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply