DSXchange

I didn't take the SQL into account either, just going by the phrasing in the original post. A more complete / complex example may have helped. [shrug]

Everything you are passing around is considered a 'parameter' in this context. However, clarify for us what you mean by 'User Variables', are you referring to something you've actually done in a User Variables Activity stage? Note that you don't need to pass anything to the Exception Handler (nor ca...

Edit your first post and check "Disable Smilies in this post".

If something supports parameters, like an email subject line, it also has an instance of the External Parameter Helper associated with it. Rather than typing in things by hand, use it to 'pick' the appropriate downstream parameter value from the list it shows you. Added bonus: it knows whether it ne...

And I suspect you are... under-thinking it.

I got the impression the derivation was dependent on the results across the data set by account and currency, not just what was present on each line.

Of course, just haven't really bothered yet. It's on my Rainy Day List, page 12.

Based on your breaks, you either want to set the derivation to Score for a new group or append using something like StageVariable : ',' : Score for the rest inside the loop for that group.

eli.nawas_AUS wrote:Is this normal behavior?

Yes.

Perhaps a scripted approach is in order for these 50+ commands?

While you certainly could use the Field() function over and over to parse the string out to fields, the Column Import stage would automate all that for you.

With the same number of rows going out as coming in, you don't really have a 'vertical pivot' IMHO, you just need to decide what one of several output columns a particular input value needs to go in based on what is in each 'group' it belongs to. Which to me implies a fork join design where one path...

True! Good point. :D

Simplifies the 'appending' part.

Off the top of my head, looping should work and they have specific functions that allow you to hold on to a record and keep appending fields to it until the group changes at which point you send it on its way. While not exactly your scenario, the functions are listed here with a decent amount of det...

Your comments on the Lookup File Set are spot on, IMHO, but they do come in handy if you have a situation where the same set of lookup data is needed by multiple jobs. Build once, leverage many. And Ray mentioned the 'time shifting' aspect of them, if they are static enough the build could be shifte...