June 29, 2017 at 11:32 am
Don't forget that your variable will probably need to be an object since you're using an object to populate it.
June 30, 2017 at 4:46 am
Brandie Tarvin - Thursday, June 29, 2017 11:32 AMDon't forget that your variable will probably need to be an object since you're using an object to populate it.
Hi Brandie, I have tried both ways: String type variable and ADO Object. For String type I have described the issue faced in my previous post. For ADO object this is what is happening;
As soon as I add this and click on ‘Ok’ button on ‘Expression Builder’ window it throws the error message:
"Expression cannot be evaluated.
------------------------------
ADDITIONAL INFORMATION:
The data type of variable "User::vFileName" is not supported in an expression.
Reading the variable "User::vFileName" failed with error code 0xC00470D0.
(Microsoft.DataTransformationServices.Controls)
June 30, 2017 at 5:12 am
I assume this happens during validation? If so, have you tried setting the expression and the task involved to Delay Validation TRUE (in the properties of each)?
June 30, 2017 at 5:54 am
Just to clear things up a little. An object variable is used to hold a full result set and this is what drives the number of iterations of the FOREACH loop (FEL) container.
Within the FEL, the 'current' value of the object variable should be assigned to a string variable (cf. an array and looping around the elements within the array).
This process is described here.
Viewing 4 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply