Suggestions Needed... 1

[zxzzzzzz]

I have two separate tables in my warehouse with a common element named current_unit_retail. My problem is that the values are not the same in the two tables (don't know why they didn't give these different names...!). I want this value in MSTR to be an attribute as there will be no calcs done against it. Is there a way to create this element and tell it NOT to look at the value in the table that isn't correct/updated? I tried to modify the lookup table using only the valid table, but it still generates the join in the SQL thus pulling back no data.

Help!!

 

[reisw]

When creating the attribute you should be able to uncheck that table that you don't want it to use in the joins. Just change the mapping method to manual and remove the source table from the attribute definition.

 

[NaughtyVicar]

As an add on to what my esteemed colleague reisw said in the previous post...

After changing the mapping method to manual for this attribute DON'T change it back to automatic again or you will have the same problem all over again!