Reason for adding a Custom Table

Answered

Comments

4 comments

  • Avatar
    Malinda Jepsen

    A really simple example is when you have some numeric or one character code in a source that you need to translate.  You could do that with a custom table (using it as a lookup table) if the code is used in multiple tables.

    0
    Comment actions Permalink
  • Avatar
    yaron schwarzman

    hi Malinda,

     

    Thanks for the quick reply.

    For the example that you had mentioned I can create an inner join between the 2 tables.The numeric field in table A is joined to the numeric field in table B and by that I can reach any field in Table B. 

    0
    Comment actions Permalink
  • Avatar
    Malinda Jepsen

    That is true.  But what if the user wants to pick "Closed" instead of 3 for example.  Part of building out the cube should be making the data more user friendly.  They shouldn't have to remember that they want to filter out all accounts that are status = 3.  You would want it to be clear that it is status = "Closed".  You can just put this in the one table if you want, but if that same set of codes is used for accounts, order, partners, etc., then one lookup table would be beneficial.  I was just giving an example of how it could be used, not that you have to.

    0
    Comment actions Permalink
  • Avatar
    yaron schwarzman

    Ok. I understand.

    Thanks for your help!

    0
    Comment actions Permalink

Please sign in to leave a comment.