Update dataverse.md #569
Update dataverse.md #569
Conversation
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")?
There was a problem hiding this comment.
Yes - that should be ### Accessing large amounts of Dataverse data
|
Learn Build status updates of commit 3306ece:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| powerquery-docs/connectors/dataverse.md | Details |
powerquery-docs/connectors/dataverse.md
- Line 120, Column 19: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#accessing-large-semantic-models' in 'connectors/dataverse.md'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
|
Learn Build status updates of commit 09e6383: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
#sign-off |
prmerger-automator
bot
added
ready-to-merge
and removed
do-not-merge
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.