Hi John, thanks for the replies. Yes you are right expressions do work, however you do get some funny messages initially and you can't leave the actual fields blank as they don't validate otherwise (so you have
to fill in the default values with something. In the expressions view you briefly get
"The object does not support type information. This occurs when the runtime attempts to get the type information from an object to populate the Properties collection. The object must support type information."
it goes away after doing a couple of other things fortunately so not a major issue. I guess if the component handled expressions directly in the UI it would be able to do the refresh or whatever it is doing
itself and you wouldn't need to populate the values with some dummy values to allow it to validate.
Another thing that I've found is that if you have the component receiving duplicate named columns in the input source the "Input columns" tab is empty. E.g. if you have a "Derived Column" Transformation
that has created a column with the same name as another. Took me a while to work it out, but finally got to the bottom of it. Not sure what the correct behaviour would be but I guess you could provide text with the reason for being blank or provide the list
with lineage ids so you can work out which one you actually want. Do you want me to create an issue/feature tracker bug for this?
This really is a great component apart from these minor issues. This along with the Kimball component has inspired me to build some custom SSIS components which I have a couple of ideas for. Thanks!