It does show up in the preview.
Without deleting and recreating the component (with all the ensuing broken metadata fixes 'downstream' that this always entails), how can I get it to recognise the change?
In future I will do all LUs as a sql statement so at least I can control columns. This again defeats the purpose of the drag and drop environment..... If it were a harry potter character, it would be a dementor
Unfortunately, Lookup does not automatically updates the reference metadata, but you can do this using Advanced UI. Right click the component, select 'Show Advanced Editor'. Click Refresh button in the lower-left corner, click OK.
Now open regular Lookup Editor, you should see the new columns.
|||My workaround was to script out the table as a select and change the type to sql stmt.The column names were all the same so this didn't seem to break it.|||
Adolf,
More than a workaround; that is the best way of using a lookup transformation. There are several negative effects performance wise when you select the table from the list as opposed to provide a sql statement.
Lookup transformation by default uses RAM and you can reduce that impact by trimming the number of columns and rows that it uses (via query).
