From 5095669579592c6623b52ea9db6a93b8b3e9ceaf Mon Sep 17 00:00:00 2001 From: Janet Revell Date: Mon, 8 Jul 2024 14:45:30 -0700 Subject: [PATCH] Fixed link in agent deploy --- soda-agent/deploy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/soda-agent/deploy.md b/soda-agent/deploy.md index 77279410..8a175771 100644 --- a/soda-agent/deploy.md +++ b/soda-agent/deploy.md @@ -1294,7 +1294,7 @@ See also: [Use a file reference for a BigQuery data source connection](#use-a-fi During its initial scan of your datasource, Soda Cloud discovers all the datasets the data source contains. It captures basic information about each dataset, including a dataset names and the columns each contains. -In the editing panel, specify the datasets that Soda Cloud must include or exclude from this basic discovery activity. The default syntax in the editing panel instructs Soda to collect basic dataset information from all datasets in the data source *except* those with names that begin with `test_`. The `%` is a wildcard character. See [Add dataset discovery]({% link soda-cl/profile.md %}l#add-dataset-discovery) for more detail on profiling syntax. +In the editing panel, specify the datasets that Soda Cloud must include or exclude from this basic discovery activity. The default syntax in the editing panel instructs Soda to collect basic dataset information from all datasets in the data source *except* those with names that begin with `test_`. The `%` is a wildcard character. See [Add dataset discovery]({% link soda-cl/profile.md %}#add-dataset-discovery) for more detail on profiling syntax. *Known issue:* SodaCL does not support using variables in column profiling and dataset discovery configurations.