SSIS Integration Toolkit

You can find the SOQL reference document at the following URL: http://www.salesforce.com/us/developer/docs/soql_sosl/index.htm

This error occurs when multiple records have the same text value. During the Text Lookup process, these values are translated into the same Salesforce ID. When the second record is processed, the system throws this exception because the record with that ID has already been deleted.

To avoid this issue, ensure that there are no duplicate values in the system when using the Text Lookup feature with the DELETE action. If duplicates already exist and you must use Text Lookup for DELETE, you can modify your source query to return only distinct records. For example, if your source is Salesforce and you want to delete all Contact records with a LastName starting with "Lastname", you can use a query like the following:

SELECT Name
   FROM Contact
  WHERE LastName LIKE 'Lastname%'
  GROUP BY Name
  LIMIT 2000

Using this approach, you may need to run the DELETE data flow task multiple times to complete the deletion. 

The following tips can help improve the performance of the Salesforce Destination Component.

From an SSIS development perspective, consider the following:

• Minimize the number of object fields you write to Salesforce
• Use an appropriate batch size
• Consider using the Salesforce Bulk API option in the Salesforce Destination Component
• Consider implementing BDD (Balanced Data Distributor) functionality to write data to Salesforce in parallel.

This error occurs when the connection user is configured to use multi-factor authentication (MFA). Our software is designed for non-interactive use, and MFA requires manual human intervention, which is not possible in a non-interactive process. Therefore, MFA is not supported. The alternative is to use a different connection user that does not have MFA enabled.

There are different ways to upload local files to a SharePoint document library. You can use the Premium File Transfer task to transfer files. You can also use the SSIS Import Column transformation component with our SharePoint Destination Component to help upload files to the library.

The Opportunity API, Company API, and Sales Person API are not supported for CRM-enabled subscriptions.

This issue occurs because Marketo attempts to detect differences when using the updateOnly method for the Sales Person object. If the input data is identical to the existing data, a "System error" may occur.

To avoid this error from failing your package, you can enable the "Redirect rows to error output" option on the Error Handling page in the Marketo Destination Component. Alternatively, you can use the Upsert (Create or Update) method.

The number (for example, 3388) is the ErrorCode returned from the Dynamics GP stored procedure. You can query the table Dynamics.dbo.taErrorCodes to find the corresponding error description.

Yes, it does. If you need to work with custom stored procedures created in the Dynamics GP database, you can navigate to:

• C:\Program Files\KingswaySoft\SSIS Integration Toolkit\Schemas\DynamicsGP
• Then modify the schema files accordingly by adding the schema for your procedures
• Make sure to create a full backup of the file before making any changes so you have a working reference
• If you want to store schema files in a different folder, you can add a registry entry under:
• HKLM\SOFTWARE\KingswaySoft\SSIS Integration Toolkit for Microsoft Dynamics GP
• Create a new entry called SchemaDirectory and point it to the desired folder (where you store your schema files)