From f326a667aaec595ebe588888d9ab37df5711bd2c Mon Sep 17 00:00:00 2001 From: Scott Sewell Date: Tue, 12 Nov 2024 07:50:57 -0600 Subject: [PATCH 1/3] Update dataverse.md I think the wording got messed up with the bulk effort to change all instances of "Data model" to "semantic model" - In this instance, the "data model" was referring to the schema in Dataverse, not Power BI - As a result, the first sentence in the paragraph became completely inaccurate since there is no "Power BI Semantic Model *IN* Dataverse. --- powerquery-docs/connectors/dataverse.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerquery-docs/connectors/dataverse.md b/powerquery-docs/connectors/dataverse.md index a8b9265ee..43ed5c9df 100644 --- a/powerquery-docs/connectors/dataverse.md +++ b/powerquery-docs/connectors/dataverse.md @@ -175,7 +175,7 @@ Misspelling a column name might result in an error message about query folding i ### Accessing large semantic models -Power BI semantic models contained in Dataverse can be very large. If you're using the Power Query Dataverse connector, any specific query that accesses the model has a fixed five (5) minute timeout irrespective of the size of the data. For more information, go to [limitations](/power-apps/developer/data-platform/dataverse-sql-query#limitations). So you might need to query the data multiple times to access all of the data in the model. Using multiple queries can take a considerable amount of time to return all the data. +Queries on Dataverse tables can return large amounts of data. If you're using the Power Query Dataverse connector, any specific query that accesses the model has a fixed five (5) minute timeout irrespective of the size of the data. For more information, go to [limitations](/power-apps/developer/data-platform/dataverse-sql-query#limitations). So you might need to query the data multiple times to access all of the data in the model. Using multiple queries can take a considerable amount of time to return all the data. If you're using the [Common Data Service (Legacy)](common-data-service-legacy.md) connector, you can use a single query to access all of the data in the semantic model. This connector works differently and returns the result in "pages" of 5-K records. Although the Common Data Service (Legacy) connector is more efficient in returning large amounts of data, it can still take a significant amount of time to return the result. From 3306ece266ae9a3edd5bb6b416b5a38ecc510906 Mon Sep 17 00:00:00 2001 From: Doug Klopfenstein Date: Tue, 4 Feb 2025 07:54:36 -0800 Subject: [PATCH 2/3] Updated per review --- powerquery-docs/connectors/dataverse.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/powerquery-docs/connectors/dataverse.md b/powerquery-docs/connectors/dataverse.md index 43ed5c9df..b5a6f8c68 100644 --- a/powerquery-docs/connectors/dataverse.md +++ b/powerquery-docs/connectors/dataverse.md @@ -173,13 +173,13 @@ in Misspelling a column name might result in an error message about query folding instead of missing column. -### Accessing large semantic models +### Accessing large amounts of Dataverse data Queries on Dataverse tables can return large amounts of data. If you're using the Power Query Dataverse connector, any specific query that accesses the model has a fixed five (5) minute timeout irrespective of the size of the data. For more information, go to [limitations](/power-apps/developer/data-platform/dataverse-sql-query#limitations). So you might need to query the data multiple times to access all of the data in the model. Using multiple queries can take a considerable amount of time to return all the data. -If you're using the [Common Data Service (Legacy)](common-data-service-legacy.md) connector, you can use a single query to access all of the data in the semantic model. This connector works differently and returns the result in "pages" of 5-K records. Although the Common Data Service (Legacy) connector is more efficient in returning large amounts of data, it can still take a significant amount of time to return the result. +If you're using the [Common Data Service (Legacy)](common-data-service-legacy.md) connector, you can use a single query to access all of the data. This connector works differently and returns the result in "pages" of 5-K records. Although the Common Data Service (Legacy) connector is more efficient in returning large amounts of data, it can still take a significant amount of time to return the result. -Instead of using these connectors to access large semantic models, we recommend that you use [Azure Synapse Link](/powerapps/maker/data-platform/export-to-data-lake) to access large models. Using Azure Synapse Link is even more efficient than either the Power Query Dataverse or Common Data Service (Legacy) connectors, and is specifically designed around data integration scenarios. +Instead of using these connectors to access large amounts of Dataverse data, we recommend that you use [Azure Synapse Link](/powerapps/maker/data-platform/export-to-data-lake) to access large models. Using Azure Synapse Link is even more efficient than either the Power Query Dataverse or Common Data Service (Legacy) connectors, and is specifically designed around data integration scenarios. ### Performance issues related to relationship columns From 09e638360bd306e91c93e3cbbe4e6eef2b62358e Mon Sep 17 00:00:00 2001 From: Doug Klopfenstein Date: Tue, 4 Feb 2025 07:57:45 -0800 Subject: [PATCH 3/3] Fixed broken link --- powerquery-docs/connectors/dataverse.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerquery-docs/connectors/dataverse.md b/powerquery-docs/connectors/dataverse.md index b5a6f8c68..8e238c406 100644 --- a/powerquery-docs/connectors/dataverse.md +++ b/powerquery-docs/connectors/dataverse.md @@ -116,7 +116,7 @@ There are certain Tabular Data Stream (TDS) data types that are supported in ODa All of these features will be added to the Dataverse connector in the future, at which time the Common Data Service (Legacy) connector will be deprecated. -More information: [Accessing large semantic models](#accessing-large-semantic-models) +More information: [Accessing large amounts of Dataverse data](#accessing-large-amounts-of-dataverse-data) ## Limitations and issues