I think stage variables should be imported and exported just as if they were columns in a table. It is very tedious to input these. This could save a lot of time.
The same is true for parameters. If I could import and export the parameters into a job as if they were columns in a table then adding all parameters from one job into another job like a sequence would save a lot of time.
I would also like to edit column names like you can in a transform stage on derivations. Stage variables all start with 'sv'. So if you added above features then I could import all the columns from a table then add 'sv' to the front of each column then have a stage variable for each column in a table. We had this at one customer where we had 3 stage variables for every inbound column. You quickly create this by modifying the original inbound table columns and then importing them into stage variables.
Import parameters and stage variables as if they were tables
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: