Hi Rahul,
I believe that note was a related but different issue, even though it looks the same. I assume that your transformations are running OK as long as you don't change them, but if you try to reactivate them you are getting syntax errors? (Or not? If not, you do need an OSS message and just disregard what I'm saying below.) The note, I think, was to fix a problem where you would get runtime errors even if you didn't try to change your transformations.
What you're running into is that transformations just semantically work differently in 7.3 vs. 7.0. In 7.0 all fields appeared in the end-routine but only mapped fields would update to the data target by default. In 7.3 you have to manually choose which un-mapped fields show up in the end-routine and these fields all get updated in the target. Because of this you may need to rethink your transformation logic a bit.
In your case the solution is going to be to add the additional fields to the end-routine in the new transformation when you modify it. Just be careful because those fields will get updated in your target.
Regards,
Ethan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.