Pipeline json breaking changes for git

[BramT]

I have a pipeline containing several notebooks that are in the same workspace. In the pipeline-content.json file stored in Git a reference to a notebook looks like this:

{
  "properties": {
    "activities": [
      {
        "type": "TridentNotebook",
        "typeProperties": {
          "notebookId": "6ae14a18-952d-179d-68ad-640b2ac361b3",
          "workspaceId": "00000000-0000-0000-0000-000000000000",
          "parameters": {

.....

 Note that the notebookId is the logicalId in the .platform file of the notebook in Git.

Now when editing and saving the pipeline in Fabric, the workspaceId is suddenly hard coded to the current workspace GUID and the notebookId in the json is now the notebook GUID from the url in stead of the platform file. This breaks the whole logic when commiting changes to another branch. Is this change on purpose ?

[BramT]

Hi Prasanna,
Thanks for your suggestion. We had a support ticket, but we couldn't reproduce the issue. Be aware though that the json in the UI shows different GUID's than the pipeline-content.json. The most likely scenario is that the customer edited the pipeline in Fabric and pasted the content from the json editor into the pipeline-content.json file in the Git repository.

Best regards,
Bram

[Anonymous]

Hi @BramT,

Just checking, have you had a chance to open a support ticket, as suggested. If so, we'd love to hear the current status or any updates from that.

If the issue was resolved through the support ticket, it would be great if you could share the solution here as well. It could really help other community members find answers more quickly.

Warm regards,
Prasanna Kumar

[Anonymous]

Hi @BramT,

If the issue still persists, I’d recommend raising a support ticket with Microsoft. The support team can look into the backend and provide more in-depth assistance tailored to your environment.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

Thanks & Regards,

Prasanna Kumar

[BramT]

Thanks @KevinChant 
We are already using variable libraries for other items. But this seems an undocumented change that has emerged in the last week(s). The sudden change from using notebook logicalId's to notebook itemId's in the pipeline-content.json is not documented and it breaks pull request from other branches. Also when you want to branch out to a new workspace the pipeline will be still pointing to notebooks in the old workspace. That's why I wonder if this change is on purpose.

[KevinChant]

yes, but there's workarounds. In your case i recommend looking at variable libraries:

Get Started with Variable Libraries - Microsoft Fabric | Microsoft Learn 

I hope this helps.