Distinct load on tables

Hi,

if you set a primary key on your dimension table and have the default Error setting on violations you will never encounter duplicates. I prefer to know that duplicates appear versus “preventing” them by using distinct.

If you have more complex needs you can create a table based on distinctness: you can either use an Aggregate table without aggregate fields (this is literally a distinct) or use  Add Related Records with a where not exists condition to avoid duplicates.

Good suggestions @rory.smith . Sometimes it just is the way it is and you get the data the way you get the data. Putting a selection box in tthe settings to be able to set the table to a distinct load would be very helpful in some situations as i'm not a great fan of load the data again to get the results that I want. haveing a work around with te PK options is nice, for now, but in my eyes not a real solution. I could reload the table through a view and materialize that view, but still a work around in my eyes.

I think this feature can improve on the flexibility you have in TX.