If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

One to many D-link or A Table

Started by Tricky, 11 Jun 2010 06:27:16 AM

Previous topic - Next topic

Tricky

Hi,

I have a number of projects with associated data.
The source package data contains one instance of the project but the target d-list may contain many instances of the same project (we sell the same product to different customers so use the .1 etc to distinguish)

Example:

Source data item                    Target d-list item
A123                                    A123.1
                                           A123.2

I would like the project information (example manufacturer) from the source to be mapped to both instances of the target.
I have tried matching on the first 4 characters but this does not work. What is the best way to do this one to many scenario?

Thanks





                             

vipul.bahl@gmail.com

Hi,

Did you use substring/cut column?
By using substring/cut column you can select the first 4 characters in the target dimension and then using match description, you can map source and target items.
To do this:
1. Create a D-Link,
2. specify source D-Cube and Target D-Cube.
3. Select the D-List in which you want to substring. All the items in the D-List will be displayed.
4. Just above the items there is a small tab (next to the name of the D-list). On clicking it, you can select the first 4 characters of the items in the D-List.

Regards,
Vipul.B

lav4you

there are different ways to implement it.
looking at the current requirement the best way will be to implement allocation table

I am sorry to say, but Vipul your method will transfer data for only first instance of target dimension i.e. A123.1 of the example

vipul.bahl@gmail.com

#3
Hi,
Yes i agree with you. my mistake.

Using Allocation is an option.
In the allocation, we can use D-Cube data as source, if there are 100s of items for which allocation needs to be defined.  Because defining allocation manually can become very tedious, time consuming (assuming company has got lots of products) and is error prone.

Kindly click on the link to see the screenshot for more details. I hope it clarifies.
http://i46.tinypic.com/ixfmf7.jpg