Forum Discussion

paulenomial's avatar
paulenomial
Frequent Visitor
2 years ago
Solved

"Save as" button not working for pipelines

I've made a pipeline that I wish to now create copies of and just change parameters within them for different tables, but when I try to click "Save as" in the top left of the pipeline it will just constantly spin with no resolution:

 

 

 The same happens if you try to use the save as option in the workspace as well. I've tried using different browsers and restarting computer but no change. I've also tried this with just a blank pipeline in case it was a certain activity causing the issue but the issue remains.


Thanks in advance.

 

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi paulenomial , KajaMohamed  -

    Apologies for the issue you are facing.

    I got a confirmation from the internal team, that it is identified as a bug.

    We have a workaround for you.

    Steps for Save As Mitigation via Edit JSON:

    1. If pipeline is open and has pending changes to save but Save As is hanging, navigate to 'View' tab.

     

    2. Click 'View JSON Code' to open pipeline JSON. Find "properties" field of original pipeline and copy JSON "properties" field. Paste somewhere temporarily in a file editor.



    3. Find browser's URL bar, scroll to end of URL, and append '&feature.enableJsonEdit=true' at the end. Click enter or manually refresh browser.

     

    4. Navigate to your workspace view where you wish to save this pipeline, click '+ New' then click 'Data pipeline'.

     

    5. Name your pipeline and click 'Create'

     

    6. Navigate to 'View', click 'Edit JSON Code'. Replace "properties" field of new pipeline with original pipeline. Click 'OK'




    Please follow above steps untill the issue gets fixed, so that you can save a copy till time being. Please let me know incase of further queries.

    Sorry for the inconvience, Team is working closely on this issue inorder to fix it.

18 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi paulenomial , KajaMohamed  -

    Apologies for the issue you are facing.

    I got a confirmation from the internal team, that it is identified as a bug.

    We have a workaround for you.

    Steps for Save As Mitigation via Edit JSON:

    1. If pipeline is open and has pending changes to save but Save As is hanging, navigate to 'View' tab.

     

    2. Click 'View JSON Code' to open pipeline JSON. Find "properties" field of original pipeline and copy JSON "properties" field. Paste somewhere temporarily in a file editor.



    3. Find browser's URL bar, scroll to end of URL, and append '&feature.enableJsonEdit=true' at the end. Click enter or manually refresh browser.

     

    4. Navigate to your workspace view where you wish to save this pipeline, click '+ New' then click 'Data pipeline'.

     

    5. Name your pipeline and click 'Create'

     

    6. Navigate to 'View', click 'Edit JSON Code'. Replace "properties" field of new pipeline with original pipeline. Click 'OK'




    Please follow above steps untill the issue gets fixed, so that you can save a copy till time being. Please let me know incase of further queries.

    Sorry for the inconvience, Team is working closely on this issue inorder to fix it.

    • smeetsh's avatar
      smeetsh
      Continued Contributor

      That worked for me , thanks!

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi smeetsh ,

        Glad to know that it worked.!

    • ReginaldPenguin's avatar
      ReginaldPenguin
      Advocate I

      This shouldn't be marked as solved. I still cannont modify and save my master pipeline which is a disaster. I'll open another thread

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi ReginaldPenguin ,

        Apologies for the issue you are facing. 
        Can you please share the new thread link once created, I will look into your case closely.
        As per the communication internal team resolved the 'Save a Pipeline' Issue.

        Thank you

    • Nashrin's avatar
      Nashrin
      Frequent Visitor

      It doesn't works for me. I am not able to save the pipeline.

      • smeetsh's avatar
        smeetsh
        Continued Contributor

        did you add: &feature.enableJsonEdit=true    to the end of the url? If you don't, you can't save it.

  • menchgelof's avatar
    menchgelof
    Frequent Visitor

    Two points of additional detail:

     

    Once you add '&feature.enableJsonEdit=true' to the end of the current URL, it stays attached to future URLs you visit, like you've enabled your entire Fabric session to allow JSON editing. I don't know yet if it's permanent until you proactively remove it (not enough testing yet on my part).

     

    If you continue to follow the solution directions, you need to perform an edit to your pipeline after pasting in the JSON code. I discovered that simply pasting in the JSON code did not enable the save button. It was only after making an edit of some kind that the save button was enabled, and I was then able to save the pipeline.

     

    All in all, this is a easy workaround.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Madalina2801 , Anonymous 

    I got a confirmation from internal that issue got fixed. 
    Hope you would be able to save the pipeline from UI.
    Thank you.

    • smeetsh's avatar
      smeetsh
      Continued Contributor

      I can concur, works for me now 🙂

    • Madalina2801's avatar
      Madalina2801
      Advocate II

      I checked using different browsers and it's still not working for me. Could you please check again on your side?

  • KajaMohamed's avatar
    KajaMohamed
    Regular Visitor

    Experiencing the same issue. Also the save button too stops working half way through building a pipeline.

  • smeetsh's avatar
    smeetsh
    Continued Contributor

    I am having the exact same issue, it just sits there spinning and nothing happens.

  • I can't run, validate, or save my pipelines. 

     

    I can run them actually but it has to be via the 'run' option in the schedule, there's then no obvious effect until clicking into the run in 'View Run History'

  • Hello,

     

    Are there any updates regarding this issue? When will this be fixed?

  • Anonymous's avatar
    Anonymous
    Not applicable

    Here I have the same issue, I could use the workaround but hope the team fixes this soon