Skip to content

Commit 2da8e1b

Browse files
tiburdtiburd
authored
Merge pull request #93509 from linda33wj/master
Update ADF connector articles
2 parents e9d38a6 + ebfcf50 commit 2da8e1b

12 files changed

+64
-102
lines changed

‎articles/data-factory/connector-amazon-marketplace-web-service.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Amazon Marketplace Web Service using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Amazon Marketplace Web Service using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Amazon Marketplace Web Service to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -16,13 +16,10 @@ ms.date: 08/01/2018
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Amazon Marketplace Web Service using Azure Data Factory (Preview)
19+
# Copy data from Amazon Marketplace Web Service using Azure Data Factory
2020

2121
This article outlines how to use the Copy Activity in Azure Data Factory to copy data from Amazon Marketplace Web Service. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
2222

23-
> [!IMPORTANT]
24-
> This connector is currently in preview. You can try it out and give us feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
25-
2623
## Supported capabilities
2724

2825
This Amazon Marketplace Web Service connector is supported for the following activities:

‎articles/data-factory/connector-drill.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Drill using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Drill using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Drill to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -12,17 +12,14 @@ ms.workload: data-services
1212
ms.tgt_pltfrm: na
1313

1414
ms.topic: conceptual
15-
ms.date: 09/04/2019
15+
ms.date: 10/25/2019
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Drill using Azure Data Factory (Preview)
19+
# Copy data from Drill using Azure Data Factory
2020

2121
This article outlines how to use the Copy Activity in Azure Data Factory to copy data from Drill. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
2222

23-
> [!IMPORTANT]
24-
> This connector is currently in preview. You can try it out and give us feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
25-
2623
## Supported capabilities
2724

2825
This Drill connector is supported for the following activities:

‎articles/data-factory/connector-dynamics-ax.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Dynamics AX by using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Dynamics AX by using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Dynamics AX to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -16,7 +16,7 @@ ms.date: 08/01/2019
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Dynamics AX by using Azure Data Factory (Preview)
19+
# Copy data from Dynamics AX by using Azure Data Factory
2020

2121
This article outlines how to use Copy Activity in Azure Data Factory to copy data from Dynamics AX source. The article builds on [Copy Activity in Azure Data Factory](copy-activity-overview.md), which presents a general overview of Copy Activity.
2222

‎articles/data-factory/connector-dynamics-crm-office-365.md

Lines changed: 15 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.workload: data-services
1212
ms.tgt_pltfrm: na
1313

1414
ms.topic: conceptual
15-
ms.date: 07/01/2019
15+
ms.date: 10/25/2019
1616
ms.author: jingwang
1717

1818
---
@@ -71,7 +71,7 @@ The following properties are supported for the Dynamics linked service.
7171

7272
| Property | Description | Required |
7373
|:--- |:--- |:--- |
74-
| type | The type property must be set to **Dynamics**. | Yes |
74+
| type | The type property must be set to **Dynamics**, **DynamicsCrm**, or **CommonDataServiceForApps**. | Yes |
7575
| deploymentType | The deployment type of the Dynamics instance. It must be **"Online"** for Dynamics online. | Yes |
7676
| serviceUri | The service URL of your Dynamics instance, e.g. `https://adfdynamics.crm.dynamics.com`. | Yes |
7777
| authenticationType | The authentication type to connect to a Dynamics server. Specify **"Office365"** for Dynamics online. | Yes |
@@ -114,7 +114,7 @@ The following properties are supported for the Dynamics linked service.
114114

115115
| Property | Description | Required |
116116
|:--- |:--- |:--- |
117-
| type | The type property must be set to **Dynamics**. | Yes |
117+
| type | The type property must be set to **Dynamics**, **DynamicsCrm**, or **CommonDataServiceForApps**. | Yes |
118118
| deploymentType | The deployment type of the Dynamics instance. It must be **"OnPremisesWithIfd"** for Dynamics on-premises with IFD.| Yes |
119119
| hostName | The host name of the on-premises Dynamics server. | Yes |
120120
| port | The port of the on-premises Dynamics server. | No, default is 443 |
@@ -156,43 +156,21 @@ The following properties are supported for the Dynamics linked service.
156156

157157
For a full list of sections and properties available for defining datasets, see the [Datasets](concepts-datasets-linked-services.md) article. This section provides a list of properties supported by Dynamics dataset.
158158

159-
To copy data from and to Dynamics, set the type property of the dataset to **DynamicsEntity**. The following properties are supported.
159+
To copy data from and to Dynamics, the following properties are supported.
160160

161161
| Property | Description | Required |
162162
|:--- |:--- |:--- |
163-
| type | The type property of the dataset must be set to **DynamicsEntity**. |Yes |
163+
| type | The type property of the dataset must be set to **DynamicsEntity**, **DynamicsCrmEntity**, or **CommonDataServiceForAppsEntity**. |Yes |
164164
| entityName | The logical name of the entity to retrieve. | No for source (if "query" in the activity source is specified), Yes for sink |
165165

166-
> [!IMPORTANT]
167-
>- When you copy data from Dynamics, the "structure" section is optional but highly recommanded in the Dynamics dataset to ensure a deterministic copy result. It defines the column name and data type for Dynamics data that you want to copy over. To learn more, see [Dataset structure](concepts-datasets-linked-services.md#dataset-structure-or-schema) and [Data type mapping for Dynamics](#data-type-mapping-for-dynamics).
168-
>- When importing schema in authoring UI, ADF infer the schema by sampling the top rows from the Dynamics query result to initialize the structure construction, in which case columns with no values will be omitted. The same behavior applies to copy executions if there is no explicit structure definition. You can review and add more columns into the Dynamics dataset schema/structure as needed, which will be honored during copy runtime.
169-
>- When you copy data to Dynamics, the "structure" section is optional in the Dynamics dataset. Which columns to copy into are determined by the source data schema. If your source is a CSV file without a header, in the input dataset, specify the "structure" with the column name and data type. They map to fields in the CSV file one by one in order.
170-
171166
**Example:**
172167

173168
```json
174169
{
175170
"name": "DynamicsDataset",
176171
"properties": {
177172
"type": "DynamicsEntity",
178-
"structure": [
179-
{
180-
"name": "accountid",
181-
"type": "Guid"
182-
},
183-
{
184-
"name": "name",
185-
"type": "String"
186-
},
187-
{
188-
"name": "marketingonly",
189-
"type": "Boolean"
190-
},
191-
{
192-
"name": "modifiedon",
193-
"type": "Datetime"
194-
}
195-
],
173+
"schema": [],
196174
"typeProperties": {
197175
"entityName": "account"
198176
},
@@ -210,16 +188,20 @@ For a full list of sections and properties available for defining activities, se
210188

211189
### Dynamics as a source type
212190

213-
To copy data from Dynamics, set the source type in the copy activity to **DynamicsSource**. The following properties are supported in the copy activity **source** section.
191+
To copy data from Dynamics, the following properties are supported in the copy activity **source** section.
214192

215193
| Property | Description | Required |
216194
|:--- |:--- |:--- |
217-
| type | The type property of the copy activity source must be set to **DynamicsSource**. | Yes |
195+
| type | The type property of the copy activity source must be set to **DynamicsSource**, **DynamicsCrmSource**, or **CommonDataServiceForAppsSource**. | Yes |
218196
| query | FetchXML is a proprietary query language that is used in Dynamics (online and on-premises). See the following example. To learn more, see [Build queries with FetchXML](https://msdn.microsoft.com/library/gg328332.aspx). | No (if "entityName" in the dataset is specified) |
219197

220198
>[!NOTE]
221199
>The PK column will always be copied out even if the column projection you configure in the FetchXML query doesn't contain it.
222200
201+
> [!IMPORTANT]
202+
>- When you copy data from Dynamics, explicit column mapping from Dynamics to sink is optional but highly recommanded to ensure a deterministic copy result.
203+
>- When importing schema in authoring UI, ADF infers the schema by sampling the top rows from the Dynamics query result to initialize the source column list, in which case columns with no values in top rows will be omitted. The same behavior applies to copy executions if there is no explicit mapping. You can review and add more columns into the mapping, which will be honored during copy runtime.
204+
223205
**Example:**
224206

225207
```json
@@ -274,12 +256,13 @@ To copy data from Dynamics, set the source type in the copy activity to **Dynami
274256

275257
### Dynamics as a sink type
276258

277-
To copy data to Dynamics, set the sink type in the copy activity to **DynamicsSink**. The following properties are supported in the copy activity **sink** section.
259+
To copy data to Dynamics, the following properties are supported in the copy activity **sink** section.
278260

279261
| Property | Description | Required |
280262
|:--- |:--- |:--- |
281-
| type | The type property of the copy activity sink must be set to **DynamicsSink**. | Yes |
263+
| type | The type property of the copy activity sink must be set to **DynamicsSink**, **DynamicsCrmSink**, or **CommonDataServiceForAppsSink**. | Yes |
282264
| writeBehavior | The write behavior of the operation.<br/>Allowed value is **"Upsert"**. | Yes |
265+
| alternateKeyName | Specify the alternate key name defined on your entity to perform "Upsert". | No |
283266
| writeBatchSize | The row count of data written to Dynamics in each batch. | No (default is 10) |
284267
| ignoreNullValues | Indicates whether to ignore null values from input data (except key fields) during a write operation.<br/>Allowed values are **true** and **false**.<br>- **True**: Leave the data in the destination object unchanged when you do an upsert/update operation. Insert a defined default value when you do an insert operation.<br/>- **False**: Update the data in the destination object to NULL when you do an upsert/update operation. Insert a NULL value when you do an insert operation. | No (default is false) |
285268

‎articles/data-factory/connector-google-adwords.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Google AdWords using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Google AdWords using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Google AdWords to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -12,17 +12,14 @@ ms.workload: data-services
1212
ms.tgt_pltfrm: na
1313

1414
ms.topic: conceptual
15-
ms.date: 08/01/2019
15+
ms.date: 10/25/2019
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Google AdWords using Azure Data Factory (Preview)
19+
# Copy data from Google AdWords using Azure Data Factory
2020

2121
This article outlines how to use the Copy Activity in Azure Data Factory to copy data from Google AdWords. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
2222

23-
> [!IMPORTANT]
24-
> This connector is currently in preview. You can try it out and provide feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
25-
2623
## Supported capabilities
2724

2825
This Google AdWords connector is supported for the following activities:
@@ -52,7 +49,7 @@ The following properties are supported for Google AdWords linked service:
5249
| developerToken | The developer token associated with the manager account that you use to grant access to the AdWords API. You can choose to mark this field as a SecureString to store it securely in ADF, or store password in Azure Key Vault and let ADF copy activity pull from there when performing data copy - learn more from [Store credentials in Key Vault](store-credentials-in-key-vault.md). | Yes |
5350
| authenticationType | The OAuth 2.0 authentication mechanism used for authentication. ServiceAuthentication can only be used on self-hosted IR. <br/>Allowed values are: **ServiceAuthentication**, **UserAuthentication** | Yes |
5451
| refreshToken | The refresh token obtained from Google for authorizing access to AdWords for UserAuthentication. You can choose to mark this field as a SecureString to store it securely in ADF, or store password in Azure Key Vault and let ADF copy activity pull from there when performing data copy - learn more from [Store credentials in Key Vault](store-credentials-in-key-vault.md). | No |
55-
| clientId | The client id of the google application used to acquire the refresh token. You can choose to mark this field as a SecureString to store it securely in ADF, or store password in Azure Key Vault and let ADF copy activity pull from there when performing data copy - learn more from [Store credentials in Key Vault](store-credentials-in-key-vault.md). | No |
52+
| clientId | The client ID of the Google application used to acquire the refresh token. You can choose to mark this field as a SecureString to store it securely in ADF, or store password in Azure Key Vault and let ADF copy activity pull from there when performing data copy - learn more from [Store credentials in Key Vault](store-credentials-in-key-vault.md). | No |
5653
| clientSecret | The client secret of the google application used to acquire the refresh token. You can choose to mark this field as a SecureString to store it securely in ADF, or store password in Azure Key Vault and let ADF copy activity pull from there when performing data copy - learn more from [Store credentials in Key Vault](store-credentials-in-key-vault.md). | No |
5754
| email | The service account email ID that is used for ServiceAuthentication and can only be used on self-hosted IR. | No |
5855
| keyFilePath | The full path to the .p12 key file that is used to authenticate the service account email address and can only be used on self-hosted IR. | No |

‎articles/data-factory/connector-impala.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Impala by using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Impala by using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Impala to supported sink data stores by using a copy activity in a data factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -16,13 +16,10 @@ ms.date: 09/04/2019
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Impala by using Azure Data Factory (Preview)
19+
# Copy data from Impala by using Azure Data Factory
2020

2121
This article outlines how to use Copy Activity in Azure Data Factory to copy data from Impala. It builds on the [Copy Activity overview](copy-activity-overview.md) article that presents a general overview of the copy activity.
2222

23-
> [!IMPORTANT]
24-
> This connector is currently in preview. You can try it out and provide feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
25-
2623
## Supported capabilities
2724

2825
This Impala connector is supported for the following activities:

‎articles/data-factory/connector-jira.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Jira using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Jira using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Jira to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -12,17 +12,14 @@ ms.workload: data-services
1212
ms.tgt_pltfrm: na
1313

1414
ms.topic: conceptual
15-
ms.date: 08/01/2019
15+
ms.date: 10/25/2019
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Jira using Azure Data Factory (Preview)
19+
# Copy data from Jira using Azure Data Factory
2020

2121
This article outlines how to use the Copy Activity in Azure Data Factory to copy data from Jira. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
2222

23-
> [!IMPORTANT]
24-
> This connector is currently in preview. You can try it out and give us feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
25-
2623
## Supported capabilities
2724

2825
This Jira connector is supported for the following activities:

‎articles/data-factory/connector-salesforce-marketing-cloud.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Salesforce Marketing Cloud using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Salesforce Marketing Cloud using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Salesforce Marketing Cloud to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -12,17 +12,14 @@ ms.workload: data-services
1212
ms.tgt_pltfrm: na
1313

1414
ms.topic: conceptual
15-
ms.date: 08/01/2019
15+
ms.date: 10/25/2019
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Salesforce Marketing Cloud using Azure Data Factory (Preview)
19+
# Copy data from Salesforce Marketing Cloud using Azure Data Factory
2020

2121
This article outlines how to use the Copy Activity in Azure Data Factory to copy data from Salesforce Marketing Cloud. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
2222

23-
> [!IMPORTANT]
24-
> This connector is currently in preview. You can try it out and give us feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
25-
2623
## Supported capabilities
2724

2825
This Salesforce Marketing Cloud connector is supported for the following activities:

‎articles/data-factory/connector-xero.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Copy data from Xero using Azure Data Factory (Preview) | Microsoft Docs
2+
title: Copy data from Xero using Azure Data Factory | Microsoft Docs
33
description: Learn how to copy data from Xero to supported sink data stores by using a copy activity in an Azure Data Factory pipeline.
44
services: data-factory
55
documentationcenter: ''
@@ -12,17 +12,14 @@ ms.workload: data-services
1212
ms.tgt_pltfrm: na
1313

1414
ms.topic: conceptual
15-
ms.date: 08/01/2019
15+
ms.date: 10/25/2019
1616
ms.author: jingwang
1717

1818
---
19-
# Copy data from Xero using Azure Data Factory (Preview)
19+
# Copy data from Xero using Azure Data Factory
2020

2121
This article outlines how to use the Copy Activity in Azure Data Factory to copy data from Xero. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
2222

23-
> [!IMPORTANT]
24-
> This connector is currently in preview. You can try it out and provide feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
25-
2623
## Supported capabilities
2724

2825
This Xero connector is supported for the following activities:

0 commit comments

Comments
 (0)