News

Wed, 01/18/2012 - 10:08

updated Salesforce Destination

Ivan,

Thanks for your help. I think that I can work with this. Adding
another lookup in the future will be more complicated, but at least I
can store these values as variables in the configuration database
now! I also appreciate the warning in regards to the 4000 character
limit. I ended up having to split up my single Lookup+ step into

Hi Tim,

Unfortunately you cannot exactly follow the steps you have described.
What you have to do is have the complete LookupMetadataXml data stored
outside in your configuration file. Then you have to setup the
following expression on the LookupMetadataXml property:

REPLACE( @[User::DefaultLookupXml], "{DefaultGuid}",

Ivan,

Thanks for the suggestion. I followed the steps you suggested and now
I can see the XML configuration for the component in SSIS designer.
My question is how do I modify this property from script?

What I would like to do is the following:

1. Read the LookupMetadataXml
2. Use script to replace the existing Guids with ones that come from

Hi Hans,

These properties are specified in the external column element.

On Jan 16, 3:03 pm, Hans Nieuwenhuis <hansnieuwenh...@intigris.nl>
wrote:

The Salesforce Destination component documentation lists the following
options but I can't seem to find them in the properties (installed 1.5
SR-3):

RelationshipName (Salesforce Destination Input) (1.5 SR-2)
Specify relationship name for updating foreign key lookup with
external identifier.

Hi Jake,

Thank you for providing the link to the solution!

Here is the link for other customers benefit:

[link]

Regards,
Ivan

I am trying to insert large files into the annotation table, ~20 MB,
for CRM records via CozyRoc. I have updated the webconfig, added the
maxuploadfilesize registry key, and added <httpRuntime
executionTimeout="9999" maxRequestLength="50752" /> to the
machine.config file in the .net directory v2. I am able to attach the

Hi Tim,

There is a quick workaround, which will allow you to setup custom
match/no match value for the Lookup Plus. The trick is to expose the
property containing the Lookup PLus component setup available for
setup with SSIS expression. Here is how to do it:

1. Open the package containing the Lookup Plus component in a text

Excellent - thanks, this worked for me too.

Hi Tim,
Thank you for your feedback! There was indeed issue in SQL 2008. We
have issued a hotfix. Please download again SSIS+ 1.5 SR-3 and
reinstall.

Ivan, I am using SQL Server 2008

Tim,

Another requirement is to have at least SQL Server 2005 SP2 . This is
the minimum requirement for properly working installation.

Hi Tim,

I have just tested the steps below with the Script Component Plus on a
clean machine with SQL Server 2005 installed and everything worked
fine. I would recommend you reinstall your SQL Server. After the
reinstall you have to also reinstall CozyRoc SSIS+

Regards,
Ivan

I have added a Script+ component to a data flow as a Destination
item. When I go to the Advanced Tab, then Inputs and Outputs, then
Click Input | Add, I get the following:

Could not load the file or assembly
Microsoft.DataTransformationSe rvices.Design, Version-9.0.242.0 or one
of its dependencies. The located assembly's manifest definition does

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

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,

It turned out that I'd installed SP1 after SSIS+. An uninstall/
reinstall of SSIS+ solved the problem.

(Thanks to Ivan @ CozyRoc for the response.)

-- Ben

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

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?