It would be hella sweet to have a way to easily track the row count after each applied step in a dataflow. This can be useful for seeing the impact of a filter step - but most useful in seeing the impact of a join. I've been burned many times creating what I thought were many-to-one joins only to discover that there were duplicate values in the secondary table that I didn't expect- this results in a multiplication of the records. Example of how this would help- I've got a table with 100,000 records. I do a left-outer join to another table where I think there is a many-to-one relationship. I'd expect 100,000 records after this step is applied. If there are more than 100,000 records - then I've got a many-to-many relationship that I wasn't expecting. If I see the record count increase after this step, I can quickly identify the error of my ways and fix the problem. Otherwise I'm left having to scan through the logic to try to troubleshoot what went wrong.
... View more