Conversation
Removed redundant explanation about exporting semantic model definitions in Direct Lake mode.
|
@NickyvVr : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
Change sent to author
powerbi-premium/subsvc
powerbi/svc
labels
|
Learn Build status updates of commit 9394af6: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR removes redundant documentation about exporting semantic model definitions when working with Direct Lake tables in a Power BI Project (PBIP), keeping the guidance focused and avoiding repetition.
Changes:
- Removed a duplicated explanatory paragraph before the export section.
- Kept a single consolidated explanation under “Export to a Power BI Project”, with minor formatting emphasis retained.
| ## Export to a Power BI Project | ||
|
|
||
| To support professional enterprise development workflows of semantic models in Direct Lake mode, you can export the definition of your semantic model after opening it for editing, which provides a local copy of the semantic model and report metadata that you can use with Fabric deployment mechanisms such as [Fabric Git Integration](../cicd/git-integration/intro-to-git-integration.md). The Power BI Desktop report view becomes enabled letting you view and edit the local report, publish directly from Power BI Desktop isn't available but you can publish using Git integration. The **Save** button is also enabled to save the local model metadata and report in the Power BI Project folder. | ||
| To support professional enterprise development workflows of semantic models in Direct Lake mode, you can export the definition of your semantic model after opening it for editing, which provides a local copy of the semantic model and report metadata that you can use with Fabric deployment mechanisms such as [Fabric Git Integration](../cicd/git-integration/intro-to-git-integration.md). The Power BI Desktop **report view** becomes enabled letting you view and edit the local report. **Publish** directly from Power BI Desktop isn't available but you can publish using Git integration. The **Save** button is also enabled to save the local model metadata and report in the Power BI Project folder. |
There was a problem hiding this comment.
The sentence about publishing is grammatically awkward and a bit unclear ("Publish directly from Power BI Desktop isn't available..."). Consider rephrasing to clearly state that the Publish action/button in Power BI Desktop is disabled/unavailable and that publishing should be done via Git integration (and/or split into two sentences for readability).
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
This pull request has been inactive for 14 days, and an |
Removed redundant explanation about exporting semantic model definitions in Direct Lake mode.
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.
Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.
For internal Microsoft contributors, check off these quality control items as you go
1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.
2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).
3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.
4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.
5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the Pull Request. If you need to cancel that sign-off, type#hold-offinstead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.Merge and publish
#sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.#sign-offagain. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).