Unable to access precode data step variables from the where-statement of an Extract transformation

[TurnTheBacon]

I've created a DI Studio job that requires complex date variables in order to function. All the date variables are calculated in a data step in the precode of an Extract transformation, and show up with correct values in the log. However, I just learned that the precode data step variables aren't accessible from the Extract's where-statement.

What's the best way of making the Extract's precode data step variables available for reference in the Extract's where-statement? I attempted putting %let in front of each variable to no avail, so I guess they're all local to the data step.

Thanks for your time.

[RichardinOz · Accepted solution]

call symput in the datastep will create macro variables for you

data somedates ;

     ...

     call symput ('firstdate', put(firstdate, yourformat.)) ;

     /* repeat for each date */

run ;

Depending on your extract transformation requirement you may need dates to be datetime numbers or formatted dates or datetimes.

Richard in Oz