Table Mapping Replaces Alias tables also

building semantic layer
1

I have a main table (MT) and 2 aliases (AL1, AL2) to it. I mapped a table replacement for the main table (MT to ZT). During run time, all - main and 2 alias tables, gets replaced (MT, AL1 and AL2 becomes ZT). Is there any way to prevent replacing the alias tables (MT should become ZT and AL1, AL2 stay as AL1, AL2)? I am aware that Table mapping is just a string replacement during runtime. If anybody has a workaround and share it, it will be helpful.

Thanks
Peter

gpngrj :us: (BOB member since 2008-02-11)

2

Possible work-around:
Create a view of your MT table in the database (defined as: SELECT * FROM MT), include this view in your universe and create your aliases AL1 and AL2 based on this view.

Andreas :de: (BOB member since 2002-06-20)

3

As a best practice, you should never use the base table once it has been aliased. In other words, you should have not two but three aliases in your case. I would then suspect that you could to table-mapping on the alias and it would get only the value you provide. Can you try that and report back on the results?

Dave Rathbun :us: (BOB member since 2002-06-06)

4

Andreas & Dave,
Thanks for your responses.

  1. Dave - I tried your suggestion before posting my problem. It did not work. I appreciate your response.

  2. Andreas - I tried your solution using a view. It worked.
    -Created an Alias (AMT) for main table (MT) in the database.
    -Mapped MT to ZT
    -Used AMT for intended (lookup) purposes.
    -During run time MT became ZT and AMTs remained AMTs.

  3. Another solution that worked given below (alternative to creating alias in database)

    • Created a dervied table (DMT - select * from maintable) in the Universe from main table (MT)
    • Aliased derived table (DMT) as two aliases - ADMT1, ADMT2
    • Mapped MT to ZT
    • Used ADMT1 and ADMT2 for intended (lookup) purposes.
    • During run time MT became ZT. ADMT1 and ADM2 were replaced by sub-query - though not appealing, functionally it was as good as database alias tables.

Thanks again for your responses
Peter

gpngrj :us: (BOB member since 2008-02-11)

5

Can you provide a diagram of what you have?
The ZT seems a bit confusing.

Also, have you checked that you are picking up the correct version of the universe within your reporting tool?

6

ZT has all columns in MT in addition it has some authorization data, so that at runtime authorization kicks in. ZT is restricted from design time use.

Let me know, if you still need the picture post.

Thanks

gpngrj :us: (BOB member since 2008-02-11)

7

What does that mean? Does it mean that you can’t use it in Designer?

8

It can be accessed in Designer. The customer has put restrictions on using certain tables during design time, for data security.

gpngrj :us: (BOB member since 2008-02-11)

9

What do you mean by design time?