Viewing 15 posts - 226 through 240 (of 2,278 total)
Try making the variable an object type. Although you are really only returning a single value, the task views it as a set that might contain more than one...
November 13, 2012 at 11:13 am
anthony.green (11/13/2012)
Ray K (11/12/2012)
jasona.work (11/12/2012)
opc.three (11/12/2012)
The Dixie Flatline (11/12/2012)
pattycakepattycake
bakers'
man
CAKE!!!!!!!!!!!!!!
Pie!!
November 13, 2012 at 9:47 am
-Create a variable to hold your return value.
-Change your ResultSet: None to SingleRow
-Map your variable to your result set
November 12, 2012 at 9:38 am
Usually I go back to the original query at that point and resolve the issue there.
November 12, 2012 at 9:31 am
If you have some sort of ID column, use a lookup transform to lookup data that is already in your table and match it to the data coming in from...
November 7, 2012 at 12:11 pm
=JOIN(Parameters!ParameterName.Value,", ")
November 7, 2012 at 8:55 am
Are you using a stored procedure? Maybe it has more parameter inputs than you are sending.
November 7, 2012 at 8:53 am
Brandie Tarvin (11/7/2012)
Lee Crain (11/6/2012)
Knowledge, Skills, and Abilities
- In...
November 7, 2012 at 8:47 am
R2 must have a parameter that you feed with the variable value from R1.
Set up your parameter in R2. Build R2 so that it will run when given the...
November 6, 2012 at 11:25 am
If my other suggestion doesn't work you could also create 2 target files tasks and use a conditional split that would channel the data to the correct output format.
November 5, 2012 at 2:50 pm
I don't remember if this in 2005 or not, but in the connection properties there is a delimiter value that can be set by an expression. Right click on...
November 5, 2012 at 2:41 pm
Viewing 15 posts - 226 through 240 (of 2,278 total)