Update add additional columns

Author: linda33wj

articles/data-factory/connector-azure-sql-data-warehouse.md

@@ -10,7 +10,7 @@ ms.service: data-factory
 ms.workload: data-services
 ms.topic: conceptual
 ms.custom: seo-lt-2019
-ms.date: 03/12/2020
+ms.date: 03/25/2020
 ---
 
 # Copy and transform data in Azure Synapse Analytics (formerly Azure SQL Data Warehouse) by using Azure Data Factory 
@@ -439,7 +439,7 @@ If the requirements aren't met, Azure Data Factory checks the settings and autom
 
 3. If your source is a folder, `recursive` in copy activity must be set to true.
 
-4. `wildcardFolderPath` , `wildcardFilename`, `modifiedDateTimeStart`, and `modifiedDateTimeEnd` are not specified.
+4. `wildcardFolderPath` , `wildcardFilename`, `modifiedDateTimeStart`, `modifiedDateTimeEnd` and `additionalColumns` are not specified.
 
 >[!NOTE]
 >If your source is a folder, note PolyBase retrieves files from the folder and all of its subfolders, and it doesn't retrieve data from files for which the file name begins with an underline (_) or a period (.), as documented [here - LOCATION argument](https://docs.microsoft.com/sql/t-sql/statements/create-external-table-transact-sql?view=azure-sqldw-latest#arguments-2).
@@ -619,7 +619,7 @@ Using COPY statement supports the following configuration:
 
 3. If your source is a folder, `recursive` in copy activity must be set to true.
 
-4. `wildcardFolderPath` , `wildcardFilename`, `modifiedDateTimeStart`, and `modifiedDateTimeEnd` are not specified.
+4. `wildcardFolderPath` , `wildcardFilename`, `modifiedDateTimeStart`, `modifiedDateTimeEnd` and `additionalColumns` are not specified.
 
 The following COPY statement settings are supported under `allowCopyCommand` in copy activity:
 

articles/data-factory/copy-activity-overview.md

@@ -10,7 +10,7 @@ ms.reviewer: douglasl
 ms.service: data-factory
 ms.workload: data-services
 ms.topic: conceptual
-ms.date: 03/24/2020
+ms.date: 03/25/2020
 ms.author: jingwang
 
 ---
@@ -175,10 +175,6 @@ While copying data from source to sink, in scenarios like data lake migration, y
 
 See [Schema and data type mapping](copy-activity-schema-and-type-mapping.md) for information about how the Copy activity maps your source data to your sink.
 
-## Fault tolerance
-
-By default, the Copy activity stops copying data and returns a failure when source data rows are incompatible with sink data rows. To make the copy succeed, you can configure the Copy activity to skip and log the incompatible rows and copy only the compatible data. See [Copy activity fault tolerance](copy-activity-fault-tolerance.md) for details.
-
 ## Add additional columns during copy
 
 In addition to copying data from source data store to sink, you can also configure to add additional data columns to copy along to sink. For example:
@@ -191,6 +187,9 @@ You can find the following configuration on copy activity source tab:
 
 ![Add additional columns in copy activity](./media/copy-activity-overview/copy-activity-add-additional-columns.png)
 
+>[!TIP]
+>This feature works with the latest dataset model. If you don't see this option from the UI, try creating a new dataset.
+
 To configure it programmatically, add the `additionalColumns` property in your copy activity source:
 
 | Property | Description | Required |
@@ -236,6 +235,10 @@ To configure it programmatically, add the `additionalColumns` property in your c
 ]
 ```
 
+## Fault tolerance
+
+By default, the Copy activity stops copying data and returns a failure when source data rows are incompatible with sink data rows. To make the copy succeed, you can configure the Copy activity to skip and log the incompatible rows and copy only the compatible data. See [Copy activity fault tolerance](copy-activity-fault-tolerance.md) for details.
+
 ## Next steps
 See the following quickstarts, tutorials, and samples: