You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Salesforce V2 | GA version available | • Need configure the Connected Apps in Salesforce portal before using the connector. <br><br> • Support SOQL query only.<br><br>• Support report by selecting a report ID.<br><br>• `readBehavior` is replaced with `includeDeletedObjects` in the copy activity source or the lookup activity.|
380
+
381
+
### <aname="upgrade-the-salesforce-linked-service"></a> Upgrade the Salesforce connector from V1 to V2
373
382
374
383
Here are steps that help you upgrade your Salesforce connector:
375
384
@@ -379,18 +388,7 @@ Here are steps that help you upgrade your Salesforce connector:
379
388
380
389
1. If you use SQL query in the copy activity source or the lookup activity that refers to the V1 linked service, you need to convert them to the SOQL query. Learn more about SOQL query from [Salesforce as a source type](connector-salesforce.md#salesforce-as-a-source-type) and [Salesforce Object Query Language (SOQL)](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm).
381
390
382
-
1. readBehavior is replaced with includeDeletedObjects in the copy activity source or the lookup activity. For the detailed configuration, see [Salesforce as a source type](connector-salesforce.md#salesforce-as-a-source-type).
383
-
384
-
## <aname="differences-between-salesforce-and-salesforce-legacy"></a> Differences between Salesforce V2 and V1
385
-
386
-
The Salesforce V2 connector offers new functionalities and is compatible with most features of Salesforce V1 connector. The following table shows the feature differences between V2 and V1.
387
-
388
-
|Salesforce V2 |Salesforce V1|
389
-
|:---|:---|
390
-
|Support SOQL within [Salesforce Bulk API 2.0](https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/queries.htm#SOQL%20Considerations). <br>For SOQL queries: <br>• GROUP BY, LIMIT, ORDER BY, OFFSET, or TYPEOF clauses aren't supported. <br>• Aggregate Functions such as COUNT() aren't supported, you can use Salesforce reports to implement them. <br>• Date functions in GROUP BY clauses aren't supported, but they're supported in the WHERE clause. <br>• Compound address fields or compound geolocation fields aren't supported. As an alternative, query the individual components of compound fields. <br>• Parent-to-child relationship queries aren't supported, whereas child-to-parent relationship queries are supported. |Support both SQL and SOQL syntax. |
391
-
| Objects that contain binary fields aren't supported when specifying query. | Objects that contain binary fields are supported when specifying query.|
392
-
| Support objects within Bulk API when specifying query. | Support objects that are unsupported with Bulk API when specifying query.|
393
-
|Support report by selecting a report ID.|Support report query syntax, like `{call "<report name>"}`.|
391
+
1.`readBehavior` is replaced with `includeDeletedObjects` in the copy activity source or the lookup activity. For the detailed configuration, see [Salesforce as a source type](connector-salesforce.md#salesforce-as-a-source-type).
394
392
395
393
## Related content
396
394
For a list of data stores supported as sources and sinks by the copy activity, see [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).
0 commit comments