Update Power BI direct lake semantic models: add column mapping id mode support #2368
Conversation
|
@bearomorphism : 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
fabric/svc
get-started/subsvc
labels
|
Learn Build status updates of commit c6dc1af: ✅ Validation status: passed
For more details, please refer to the build report. |
bearomorphism
force-pushed
the
col-map-id
branch
from
c6dc1af to
0931cc2
Compare
bearomorphism
changed the title
|
Learn Build status updates of commit 0931cc2: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Delta Lake feature compatibility matrix to reflect that Power BI direct lake semantic models now support column mapping ID mode, in addition to the previously supported Name mode.
Key Changes
- Updated column mapping support for Power BI direct lake semantic models from "Name: Yes, ID: No" to "Name: Yes, ID: Yes"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Can you review the proposed changes? Before we can merge, this PR will need to be taken out of the draft state. 
Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
Hi, I will mark this PR as ready for review after the related feature is fully on production, thanks. |
3 participants
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).