Power BI Project PBIP - How to Separate Report Measures from Semantic Model Measures

[delish68]

I am using Power BI Projects and I'm having an issue separating Report and Dataset/Semantic Model development. 

• My semantic model is separate from my reports. 
• I have multiple reports that point to my semantic model.
• When I open one of my reports (pbir connects byPath) it also loads the semantic model.

My question is, how can users add report-only measures? That is, measures that are defined in the report and are not added to the semantic model. I don't want the semantic model to be modified.  

[v-junyant-msft]

Hi @delish68 ,

If you can, use Live Connection mode to connect to your data source. In Live Connection mode in Power BI, report-level measures are supported.

Power BI Connection Types: DirectQuery, Live, or Import? Tough Decision! - RADACAD
Report level measures with Power BI live connections - YouTube

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[erickeu]

1) Publish your datasets to powerbi service

2) open a blank report and connect live to that dataset and save the report as .pbip

3) you'll have the url that you need to change the definition.pbir:
example:

{
"version": "1.0",
"datasetReference": {
"byPath": null,
"byConnection": {
"connectionString": "Data Source=powerbi://api.powerbi.com/v1.0/myorg/AAAAAA;Initial Catalog=\"BBBB\";Access Mode=readonly;Integrated Security=ClaimsToken",
"pbiServiceModelId": null,
"pbiModelVirtualServerName": "sobe_wowvirtualserver",
"pbiModelDatabaseName": "XXXXX-xxxxx-xxXxxx-XXXXX",
"name": "EntityDataSource",
"connectionType": "pbiServiceXmlaStyleLive"
}
}
}

example :BBBB
AAAAAA: Production Finance Workspace
BBBB : Sales Datamodel
XXXXX-xxxxx-xxXxxx-XXXXX = Semantic model gui

if this helps, please mark it as a solution 🙂

[delish68]

I've done this but the issue is that the Power BI service doesn't support "byConnection" so when you publish or update from the Git integration, the service changes it back to "byPath". The report then shows that it's out of sync with what's in Git and you get stuck in an endless loop of conflicts and/or Git being updated with "byPath" which brings us back to the original problem.