Getting the current value of a task's properties?

Sep 3, 2014 at 4:50 PM
Has anyone ever wondered why MS doesn't allow access to the values of the task's properties inside an expression?

For example, if a task has a property P that's a very long string and all you need to do is a simple string substitution in the expression, it seems reasonable to use the property's value in the expression like this:

REPLACE( Task.Property(P).Value, "search string", "replacement string")

Since we can't do this we have to put the entire string in a variable, use a Script task to do the replace, and then set the property to the variable in an expression. Awkward.