I have datasource query subjects as
A <-> B
I need this replicated 5 times. I hoped to use Alias shortcuts for A and B 5 times each to get:
A <-> B
A1 <-> B1
etc.
When I create A1 and B1 as Alias shortcuts and try creating a relationship between A1 and B1 FM says if I would like to create a shortcut for relationship that is carried over from A <-> B.
But then it crossed my mind that such alias shortcuts also bring relationships as A <-> B1 and A1 <-> B ? That is not quite what I need.
Should I use alias shortcuts here or maybe another copy data query subject is a better alternative?
Thanks,
- Alp
Do the relationships between A and B always use the same fields?
We have alias shortcuts when referring two tables in different context.
Example:
- Fact-Table "FACT" with three different date fields ORDER DATE, PRODUCTION DATE, ROLLOUT DATE.
- We have one Date-Dimension-Table "DATES".
- What the enduser wants to have are is three different date dimensions.
- What we don't want is to import the DATES-Table more than one time in our model - this would be the way to handle the whole thing without any alias shortcuts. But we don't like this, so we work with alias shortcuts.
- We model three relationships between FACT and DATES using the three different fact fields. At this point we give this relationships names like "..... (OrderDate)", "..... (Production Date)".... and so on.
- Now we create three Alias Shortcuts from the DATES-Table, Naming them like "...(OrderDate)", "...(ProductionDate)"... and so on.
- Finally, the last thing to do is to create relationships between the FactTable and all of your Alias Shortcuts. At this point, you will be asked that there already are existing relationships and if you want to create a shortcut to one of the existing relationships. Yes, you want. Now you can shoose one of your created relationships and this is the point, where a good naming helps you to find the correct one fast and easy.
IceTea,
Thanks, very helpful!
So the let me put it this way. The report studio will not join alias shortcuts with tables until we at lease create an alias to the relationship, Am I correct?
Thanks,
- Alp
... actually, I can see different SQL queries for creating the relationship between A1 and B1 as an alias to the existing one and creating the actual relationship. The actual (not a shortcut) relationship gives me SQL as expected.
- Alp