Forum Discussion
Does byPath work with Live Connection report?
byPath is for PBIP‑local models, not for pointing at an already‑published one. for live‑connect reports u keep byConnection and just swap workspace/model IDs with deployment rules.
Hi sahabatsuria ,
Thanks for reaching out to Microsoft Fabric Community.
Kagiyama_yutaka is right -- byPath is not meant for cross-workspace live connect scenarios. Keep byConnection in your definition.pbir and use deployment pipeline rules to swap the connection string across your dev/test/prod stages.
On the measure editing issue you ran into -- the docs actually cover this. You can maintain two .pbir files in the same project, one with byPath for opening locally in Desktop when you need to work on report-level measures, and one with byConnection for deployment. That way both sides work without conflicting with each other.
Reference: Power BI Desktop project report folder - Power BI | Microsoft Learn
Hope this helps. Please reach out for further assistance.
Thank you.
Hi sahabatsuria ,
Thanks for reaching out to Microsoft Fabric Community.
Kagiyama_yutaka is right -- byPath is not meant for cross-workspace live connect scenarios. Keep byConnection in your definition.pbir and use deployment pipeline rules to swap the connection string across your dev/test/prod stages.
On the measure editing issue you ran into -- the docs actually cover this. You can maintain two .pbir files in the same project, one with byPath for opening locally in Desktop when you need to work on report-level measures, and one with byConnection for deployment. That way both sides work without conflicting with each other.
Reference: Power BI Desktop project report folder - Power BI | Microsoft Learn
Hope this helps. Please reach out for further assistance.
Thank you.