Merge pull request #212789 from liudan66/AddFaqs

Add faqs and update dataset parameters

Author: prmerger-automator[bot]

articles/synapse-analytics/cicd/continuous-integration-delivery.md

@@ -428,9 +428,12 @@ Here's an example of what a parameter template definition looks like:
         }
     },
     "Microsoft.Synapse/workspaces/datasets": {
-        "properties": {
-            "typeProperties": {
-                "*": "="
+        "*": {
+            "properties": {
+                "typeProperties": {
+                    "folderPath": "=",
+                    "fileName": "="
+                }
             }
         }
     },
@@ -490,11 +493,48 @@ If you're using Git integration with your Azure Synapse workspace and you have a
 
 ## Troubleshoot artifacts deployment 
 
-### Use the Synapse workspace deployment task
+### Publish failed: workspace arm file is more then 20mb 
 
-In Azure Synapse, unlike in Data Factory, some artifacts aren't Resource Manager resources. You can't use the ARM template deployment task to deploy Azure Synapse artifacts. Instead, use the Synapse workspace deployment task.
+There is a file size limitation in git provider, for example, in Azure DevOps the maximum file size is 20Mb. Once the workspace template file size exceeds 20Mb, this error happens when you publish changes in Synapse studio, in which the workspace template file is generated and synced to git. To solve the issue, you can use the Synapse deployment task with **validate** or **validate and deploy** operation to save the workspace template file directly into the pipeline agent and without manual publish in synapse studio.  
 
+
+### Use the Synapse workspace deployment task to deploy Synapse artifacts
+
+In Azure Synapse, unlike in Data Factory, artifacts aren't Resource Manager resources. You can't use the ARM template deployment task to deploy Azure Synapse artifacts. Instead, use the Synapse workspace deployment task to deploy the artifacts, and use ARM deployment task for ARM resources (pools and workspace) deployment. Meanwhile this extension only supports Synapse templates where resources have type Microsoft.Synapse 
+
+
 ### Unexpected token error in release
 
 If your parameter file has parameter values that aren't escaped, the release pipeline fails to parse the file and generates an `unexpected token` error. We suggest that you override parameters or use Key Vault to retrieve parameter values. You also can use double escape characters to resolve the issue.
+
+### Integration runtime deployment failed 
+
+If you have the workspace template generated from a managed Vnet enabled workspace and try to deploy to a regular workspace or vice versa, this error happens. 
 
+### Unexpected character encountered while parsing value
+
+The template can not be parsed the template file. Try by escaping the back slashes, eg. \\\\Test01\\Test
+
+### Failed to fetch workspace info, Not found. 
+
+The target workspace info is not correctly configured. Please make sure the service connection which you have created, is scoped to the resource group which has the workspace.
+
+### Artifact deletion failed. 
+
+The extension will compare the artifacts present in the publish branch with the template and based on the difference it will delete them. Please make sure you are not trying to delete any artifact which is present in publish branch and some other artifact has a reference or dependency on it.
+
+### Deployment failed with error: json position 0 
+
+If you were trying to manually update the template, this error would happen. Please make sure that you have not manually edited the template. 
+
+### The document creation or update failed because of invalid reference.
+
+The artifact in synapse can be referenced by another one. If you have parameterized an attribute which is a referenced in an artifact, please make sure to provide correct and non null value to it
+
+### Failed to fetch the deployment status in notebook deployment 
+
+The notebook you are trying to deploy is attached to a spark pool in the workspace template file, while in the deployment the pool does not exist in the target workspace. If you don't parameterize the pool name, please make sure that having the same name for the pools between environments. 
+
+
+
+