We use one table as a parameter table, whose values affect subsequent processing. At present, I read the values in a Python script component and update the variables via the context. It works, are there some built-in functions for this, such as the Export tab of a Table Input component? As I see it, the Export tab is only for runtime information. https://redshiftsupport.matillion.com/customer/portal/articles/2037630?b_id=8915#header3
3 Community Answers
Ian Funnell —
Using a Python script is absolutely fine, and you’ll see an example syntax in the comments when you create a new Python Script component:
The other way is to use the Table Iterator component. You would use this as a loop driver, and it’s great if you want to run the same task(s) multiple times, with one iteration per record in the table. The values of variables are set according to the column values in the table. The iterator’s Column Mapping property allows you to specify which columns go into which variables.
Yes, the export tab is mainly for exporting runtime metadata like rowcounts and durations. It won’t let you export custom variables in the way that the Python and the Table Iterator do.