Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreShape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.
Scenario
to utilize the new Preview feature, Live edit Power BI semantic models’ semantics in direct lake mode using for following links:
https://powerbi.microsoft.com/en-us/blog/live-edit-of-direct-lake-models-in-power-bi-desktop/
https://learn.microsoft.com/en-us/fabric/get-started/direct-lake-power-bi-desktop
After enabling the feature and signing in with proper right I Opened my Live edit Power BI semantic models semantics in direct lake mode,
from modeling tab >>> Logistic Model >>> Import YAML File
As the guides in above State
I applied 2 cases in YAML as:
Version: 4.1.0
Language: en-US
Entities:
dim_customer.customer_name:
Definition:
Binding: {Table: Dim Customer, Column: Customer Name}
State: Generated
Terms:
- customer name: {State: Generated}
- cus: {State: Generated, Weight: 0.97}
- client: {State: Generated, Weight: 0.97}
NameType: Name
GlobalSubstitutions:
- COOP - Odense: GSTEST
Output
The Result in Copilot chat, it should recognize the synonyms and global substitution, in the YAML file
but upon checking the ADO Repo and BIM file 3 things are noticed:
What am I missing here?
And why Copilot is not capturing the global substitution through they are in BIM file
And why these Extra additions added to BIM file though they are not in the context of YAML file?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @you5ufb,
The extra entities being generated could be due to the initial setup of the Q&A feature. When Q&A is enabled for the first time, it might automatically generate some default synonyms and content. You can manually clean these up if they are not relevant to your model.
Please ensure that the entities in your YAML file are correctly defined and that the bindings are accurate. Double-check the table and column names to make sure they match exactly with what is in your model. The global substitutions should be recognized if they are correctly defined in the YAML file. Make sure that the syntax and format are correct.
Best regards.
Community Support Team_Caitlyn