Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hey data i've imported contains several duplications, I've tried distinct load but to no luck. could you please suggest some course of actions to remove the duplications?
at present it looks something like...
balanceCurrent | balanceFuture | PostingDate | documentDate
433.50 -230.53 30/09/2014 30/09/2014
202.97 -108.24 1/09/2014 28/06/2014
202.97 -108.24 1/09/2014 28/06/2014
202.97 -108.24 30/09/2014 30/09/2014
94.73 0.00 1/09/2014 28/06/2014
94.73 0.00 1/09/2014 28/06/2014
94.73 0.00 30/09/2014 30/09/2014
thanks
Bon.
Hi,
How do you link APPeriodSummary table to the data model?
If your tables doesn't join properly (no join means cartesian product) you experience duplicate records.
There is key field between MasterCalendar and APInvoice tables but I don't see any common field with the 3rd table.
Ersen
Hey Ersen.
thank you for your reply.
sorry i have only just pasted parts of the codes in what i had posted.
APPeriodSummary is linked to APInvoice with the 'mySupplier' field, ( which was not on what I've posted earlier )
should the links be created somewhere else?
thanks.
Hi,
Do you have any Join statements to any of the tables providing any of the listed fields?
Or any duplicated key in any associated tables in the final model ?
My guess the data is duplicated in your final data model this is the case 99 percent of the time. Placing distinct in any load statements without knowing the problem may cause you more problems.
Ersen
Be careful using distinct with concatenate functions. It gets weird fast.
For example:
Facts:
Load distinct x,y,z
Resident fact1;
Concatenate(Facts)
Load x,y,z
Resident fact2;
This will continue to use distinct to enforce uniqueness, even if not specified in the second table. Whereas:
Facts:
Load distinct x,y,z
Resident fact1;
Concatenate(Facts)
Load distinct x,y,z
Resident fact2;
No longer guarantees that distinct will be enforced on the second (and subsequent) tables.
Weird.