Skip to content

Commit f1c37df

Browse files
authored
Merge pull request #286688 from MicrosoftDocs/main
Publish to live, Friday 4 AM PST, 9/13
2 parents 03f6c98 + 9fede4e commit f1c37df

34 files changed

+58
-57
lines changed

articles/data-factory/connector-salesforce-service-cloud.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 04/01/2024
10+
ms.date: 08/21/2024
1111
---
1212

1313
# Copy data from and to Salesforce Service Cloud using Azure Data Factory or Azure Synapse Analytics
@@ -165,8 +165,8 @@ To copy data from and to Salesforce Service Cloud, set the type property of the
165165
| Property | Description | Required |
166166
|:--- |:--- |:--- |
167167
| type | The type property must be set to **SalesforceServiceCloudV2Object**. | Yes |
168-
| objectApiName | The Salesforce Service Cloud object name to retrieve data from. | No for source (if "SOQLQuery" in source is specified), Yes for sink |
169-
| reportId | The ID of the Salesforce Service Cloud report to retrieve data from. It is not supported in sink. Note that there are [limitations](https://developer.salesforce.com/docs/atlas.en-us.api_analytics.meta/api_analytics/sforce_analytics_rest_api_limits_limitations.htm) when you use reports. | No for source (if "SOQLQuery" in source is specified), not support sink |
168+
| objectApiName | The Salesforce Service Cloud object name to retrieve data from. The applicable self-hosted integration runtime version is 5.44.8984.1 or above. | No for source (if "query" in source is specified), Yes for sink |
169+
| reportId | The ID of the Salesforce Service Cloud report to retrieve data from. It is not supported in sink. Note that there are [limitations](https://developer.salesforce.com/docs/atlas.en-us.api_analytics.meta/api_analytics/sforce_analytics_rest_api_limits_limitations.htm) when you use reports. The applicable self-hosted integration runtime version is 5.44.8984.1 or above. | No for source (if "query" in source is specified), not support sink |
170170

171171
> [!IMPORTANT]
172172
> The "__c" part of **API Name** is needed for any custom object.
@@ -203,7 +203,7 @@ To copy data from Salesforce Service Cloud, set the source type in the copy acti
203203
| Property | Description | Required |
204204
|:--- |:--- |:--- |
205205
| type | The type property of the copy activity source must be set to **SalesforceServiceCloudV2Source**. | Yes |
206-
| SOQLQuery | Use the custom query to read data. You can only use [Salesforce Object Query Language (SOQL)](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm) query with limitations. For SOQL limitations, see this [article](https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/queries.htm#SOQL%20Considerations). If query is not specified, all the data of the Salesforce object specified in "ObjectApiName/reportId" in dataset will be retrieved. | No (if "ObjectApiName/reportId" in the dataset is specified) |
206+
| query | Use the custom query to read data. You can only use [Salesforce Object Query Language (SOQL)](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm) query with limitations. For SOQL limitations, see this [article](https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/queries.htm#SOQL%20Considerations). If query is not specified, all the data of the Salesforce object specified in "objectApiName/reportId" in dataset will be retrieved. | No (if "objectApiName/reportId" in the dataset is specified) |
207207
| includeDeletedObjects | Indicates whether to query the existing records, or query all records including the deleted ones. If not specified, the default behavior is false. <br>Allowed values: **false** (default), **true**. | No |
208208

209209
> [!IMPORTANT]
@@ -233,7 +233,7 @@ To copy data from Salesforce Service Cloud, set the source type in the copy acti
233233
"typeProperties": {
234234
"source": {
235235
"type": "SalesforceServiceCloudV2Source",
236-
"SOQLQuery": "SELECT Col_Currency__c, Col_Date__c, Col_Email__c FROM AllDataType__c",
236+
"query": "SELECT Col_Currency__c, Col_Date__c, Col_Email__c FROM AllDataType__c",
237237
"includeDeletedObjects": false
238238
},
239239
"sink": {
@@ -343,9 +343,9 @@ The Salesforce Service Cloud connector offers new functionalities and is compati
343343

344344
|Salesforce Service Cloud |Salesforce Service Cloud (legacy)|
345345
|:---|:---|
346-
|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 are not supported. <br>• Aggregate Functions such as COUNT() are not supported, you can use Salesforce reports to implement them. <br>• Date functions in GROUP BY clauses are not supported, but they are supported in the WHERE clause. <br>• Compound address fields or compound geolocation fields are not supported. As an alternative, query the individual components of compound fields. <br>• Parent-to-child relationship queries are not supported, whereas child-to-parent relationship queries are supported. |Support both SQL and SOQL syntax. |
347-
|Objects that contain binary fields are not supported.| Objects that contain binary fields are supported, like Attachment object.|
348-
|Support objects within Bulk API. For more information, see this [article](https://help.salesforce.com/s/articleView?id=000383508&type=1).|Support objects that are not supported by Bulk API, like CaseStatus.|
346+
|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. |
347+
| Objects that contain binary fields aren't supported when specifying query. | Objects that contain binary fields are supported when specifying query.|
348+
| Support objects within Bulk API when specifying query. | Support objects that are unsupported with Bulk API when specifying query.|
349349
|Support report by selecting a report ID.|Support report query syntax, like `{call "<report name>"}`.|
350350

351351
## Related content

articles/data-factory/connector-salesforce.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 07/11/2024
10+
ms.date: 08/21/2024
1111
---
1212

1313
# Copy data from and to Salesforce using Azure Data Factory or Azure Synapse Analytics
@@ -209,8 +209,8 @@ To copy data from and to Salesforce, set the type property of the dataset to **S
209209
| Property | Description | Required |
210210
|:--- |:--- |:--- |
211211
| type | The type property must be set to **SalesforceV2Object**. | Yes |
212-
| objectApiName | The Salesforce object name to retrieve data from. | No for source (if "query" in source is specified), Yes for sink |
213-
| reportId | The ID of the Salesforce report to retrieve data from. It isn't supported in sink. There are [limitations](https://developer.salesforce.com/docs/atlas.en-us.api_analytics.meta/api_analytics/sforce_analytics_rest_api_limits_limitations.htm) when you use reports. | No for source (if "query" in source is specified), not support sink |
212+
| objectApiName | The Salesforce object name to retrieve data from. The applicable self-hosted integration runtime version is 5.44.8984.1 or above. | No for source (if "query" in source is specified), Yes for sink |
213+
| reportId | The ID of the Salesforce report to retrieve data from. It isn't supported in sink. There are [limitations](https://developer.salesforce.com/docs/atlas.en-us.api_analytics.meta/api_analytics/sforce_analytics_rest_api_limits_limitations.htm) when you use reports. The applicable self-hosted integration runtime version is 5.44.8984.1 or above. | No for source (if "query" in source is specified), not support sink |
214214

215215
> [!IMPORTANT]
216216
> The "__c" part of **API Name** is needed for any custom object.
@@ -247,7 +247,7 @@ To copy data from Salesforce, set the source type in the copy activity to **Sale
247247
| Property | Description | Required |
248248
|:--- |:--- |:--- |
249249
| type | The type property of the copy activity source must be set to **SalesforceV2Source**. | Yes |
250-
| query | Use the custom query to read data. You can only use [Salesforce Object Query Language (SOQL)](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm) query with limitations. For SOQL limitations, see this [article](https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/queries.htm#SOQL%20Considerations). If query isn't specified, all the data of the Salesforce object specified in "ObjectApiName/reportId" in dataset is retrieved. | No (if "ObjectApiName/reportId" in the dataset is specified) |
250+
| query | Use the custom query to read data. You can only use [Salesforce Object Query Language (SOQL)](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm) query with limitations. For SOQL limitations, see this [article](https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/queries.htm#SOQL%20Considerations). If query isn't specified, all the data of the Salesforce object specified in "objectApiName/reportId" in dataset is retrieved. | No (if "objectApiName/reportId" in the dataset is specified) |
251251
| includeDeletedObjects | Indicates whether to query the existing records, or query all records including the deleted ones. If not specified, the default behavior is false. <br>Allowed values: **false** (default), **true**. | No |
252252

253253
> [!IMPORTANT]
@@ -388,8 +388,8 @@ The Salesforce connector offers new functionalities and is compatible with most
388388
|Salesforce |Salesforce (legacy)|
389389
|:---|:---|
390390
|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.| Objects that contain binary fields are supported, like Attachment object.|
392-
|Support objects within Bulk API. For more information, see this [article](https://help.salesforce.com/s/articleView?id=000383508&type=1).|Support objects that are unsupported with Bulk API, like CaseStatus.|
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.|
393393
|Support report by selecting a report ID.|Support report query syntax, like `{call "<report name>"}`.|
394394

395395
## Related content
7.91 KB
Loading
10.4 KB
Loading
-328 Bytes
Loading
-2.34 KB
Loading
-1016 Bytes
Loading
-193 Bytes
Loading
-226 Bytes
Loading
-5.77 KB
Loading

0 commit comments

Comments
 (0)