×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

About Attribute Roles

About Attribute Roles

About Attribute Roles

(OP)
Hello All,

I am new to this group and also to Microstrategy. I have problem understanding the working of Attribute roles. I would appreciate if somebody could help me out here.

The MSTR knowledge base and also the advanced reporting guide talk about an existing VLDB property which supports recognition of attribute roles but I am not able to find this in MSTR 7.5.1.

Also what would be a good practice scenario for undestanding attribute roles.

I look forward for responses as this would help me a lot.

Thanks

RE: About Attribute Roles

It's a long story. I'd recommend attending advanced reporting classes. The manual should also help. Basically if you have a "gender" attribute, MicroStrategy would try to automatically figuring out if you mean "employee gender", or "customer gender", so you don't have to define it as two attributes. There're some catches e.g. in my example employee should not have direct relationship with customer and such, which is hard to prevent in real life :) My recommendation would be to go ahead and create two attributes so there're no confusions.

RE: About Attribute Roles

I think I am little confused with your explanation but I thought attribute roles were applied when you have two different attributes that could use the same lookup table. An example would be Ship Date and Invoice Date. You would only need one date lookup table. My recommendation would be to create a table alias from the one lookup table you want to use so that the engine won't be confused and you can always ensure that your queries will be written correctly.


This technote might help TN5800-072-0108

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close