MSCRM Source Text Column

23 views
Skip to first unread message

Tim Huemmer

unread,
Dec 29, 2011, 3:44:53 PM12/29/11
to CozyRoc
I have a MSCRM Source control and I need to change the length of the
text column from 250 to something larger. Every time I go into
advanced editor and attempt to change the length, I get an error
message saying that the data is invalid. The column comes across as
WSTR 250. What is the proper way to handle this?

Ivan Peev

unread,
Dec 30, 2011, 1:31:54 AM12/30/11
to CozyRoc
Hi Tim,

You can change the length or type of the column in the 'External
Columns' sub-tree. After you change it go to the 'Column Mappings' tab
and remove and re-map the related column. This will initialize the
output column with the new settings.

Regards,
Ivan

Tim Huemmer

unread,
Dec 30, 2011, 11:24:15 AM12/30/11
to CozyRoc
Thanks Ivan. I noticed that each time you click the 'Refresh' button
on this page, you will have to re-do the steps that you mentioned. I
would recommend having a way to save these changes somewhere as this
will be very difficult to keep up with from a maintenance perspective
(i.e. if you go back and edit a package 6 months after it was created,
you may not remember these manual changes that were made and thus
loose them all together)
> > WSTR 250.  What is the proper way to handle this?- Hide quoted text -
>
> - Show quoted text -

Ivan Peev

unread,
Dec 30, 2011, 5:29:57 PM12/30/11
to CozyRoc
Tim,

Thank you for your feedback! You are correct, this is a hassle.
However preserving and applying the changes is not trivial. I will
explain why. Let's say you decide to modify the type of specific
attribute in the CRM system, but your SSIS packages are setup with the
old type. With the current process, the component will correctly load
the new settings. With the "preservation system", the new type will
not appear in the component and you will have to manually update the
type to the new type.

Btw the current non-preserve logic is the same logic used in most of
the standard SSIS components. I guess the MS team had the same doubts
and decision to make what should be the right approach.
Reply all
Reply to author
Forward
0 new messages