Update table-partitions.md

Zhangqi910 · Apr 9, 2024 · 69798db · 69798db
1 parent e03a9c7
commit 69798db
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/docs/analysis-services/tom/table-partitions.md b/docs/analysis-services/tom/table-partitions.md
@@ -137,3 +137,9 @@ As mentioned earlier, the `dataCoverageDefinition` property helps eliminate unne
 
 The `DataCoverageDefinition` property on *DirectQuery* partitions enables you to optimize even the largest Power BI data models based on hot partitions in import mode and cold partitions in *DirectQuery* mode by avoiding unnecessary querying of the data source.
 This source query reduction helps to boost report performance when analyzing hot data. It also helps to decrease the load on the data source, and in this way helps to maximize the scale of your data source. Yet, keep in mind that optimizing a data model by using the `dataCoverageDefinition` property is still an advanced scenario. Make sure you verify the results carefully.
+
+## Known issues and limitations
+
+- Currently, the `DataCoverageDefinition` property on *DirectQuery* partitions requires static values, such as RELATED('Date'[Year]) = 2020 or RELATED('Date'[Year]) IN {2020, 2021, 2022}. Dynamic assignments are not supported, such as RELATED('Date'[DateKey]) = TODAY().
+
+- Incremental Refresh does not leverage the `DataCoverageDefinition` property. Any data coverage definitions must be reapplied programmatically after Incremental Refresh merged, dropped, or recreated partitions.