Update dataverse.md #569
Open
Update dataverse.md #569
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
@mscottsewell : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit f326a66: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@DougKlopfenstein Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
| @@ -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. | |||
There was a problem hiding this comment.
Since "Power BI semantic models" was changed, should the heading above this paragraph change as well (since it's currently called "Accessing large semantic models")?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.