...

• Hover over SOURCE_CHANNEL_DESCRIPTIONS and press
• Run Analysis analysis on SOURCE_CHANNEL_DESCRIPTIONS to load data into the Streamstream
• Add a lookup pipe from SOURCE_CHANNEL_DESCRIPTIONS to SOURCE_CHANNEL_LIST
• Complete configuration of the pipe:
  • Call the pipe desc

  • Create a match:

    Left-hand (reference data - SOURCE_CHANNEL_LIST)	Right-hand (output - SOURCE_CHANNEL_LIST)
    CHANNEL	CHANNEL

    
    

• Drag the Attribute CHANNEL_DESC from SOURCE_CHANNEL_DESCRIPTIONS to SOURCE_CHANNEL_LIST
• Run Analysis analysis on SOURCE_CHANNEL_LIST

You should see that the data in SOURCE_CHANNEL_LIST is loaded, including the channel description looked up from SOURCE_CHANNEL_DESCRIPTIONS.
However, look at the Stream Sets for stream sets for SOURCE_CHANNEL_DESCRIPTIONS:

• From the hover menu of the stream SOURCE_CHANNEL_DESCRIPTIONS

...

• , press Image Added

You should see that it has only run once.

Compare the run dates with the Stream Sets stream sets in SOURCE_CHANNEL_LIST. You will see that SOURCE_CHANNEL_DESCRIPTIONS was not run when you ran SOURCE_CHANNEL_LIST; - SOURCE_CHANNEL_DESCRIPTIONS only ran when you ran it on its own.

...

Create and use a static pipe

• Hover over SOURCE_CHANNEL_LIST and press 
• Call the new stream Customer Channel Copy
• Copy all attributes from SOURCE_CHANNEL_LIST to Customer Channel Copy
• Hover over the pipe and press
• Run Analysis analysis on Customer Channel Copy

You will see that the data in the stream is generated, but that SOURCE_CHANNEL_LIST did not run.