Forum Discussion

gmarc's avatar
gmarc
Advocate I
2 years ago
Solved

Import renaming notebooks

Hi,

 

I'm facing the issue that when I delete one or multiple notebooks and import them again right afterwards, the newly created file is renamed to <filename>(1), although the previous file with the same name does not exist anymore.

 

This happens when deleting manually and also when deleting using the GIT repostory.

 

Is it planned to fix this behavior?

 

As currently the only way to import existing Jupyter Notebooks into Fabric is the usage of the UI import or the REST API, it is really important that the Fabric workspace is aware of deleted files as soon as they are deleted.

 

Best regards,

Marc

 

 

CICD
data engineering
  • gmarc's avatar
    gmarc
    2 years ago

    Hi Anonymous 

     

    According to the support team, this behavior is as designed due to the asynchronous implementation.

     

    I have now created an idea for the enhancement of this matter here: Microsoft Idea

     

    Best regards,

    Marc

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi gmarc 
    Thanks for using Fabric Community and providing your valuable feedback.
    Can you please provide me the screenshots related to this behaviour? This helps me in understanding the issue better.
    Thanks.

    • gmarc's avatar
      gmarc
      Advocate I
      2 years ago

      Hi Anonymous,

       

      Sure.

       

      Initial state:

       

      Notebooks deleted and commited:

       

      Notebooks imported anew from local machine:

       

      Deployment file now was named "Deployment(1)" as for the workspace the file "Deployment" still exists

       

       

      • Anonymous's avatar
        Anonymous
        Not applicable
        2 years ago

        Thanks for the screenshots gmarc .
        Apologies for the issue you have been facing. I will report this to the internal team. I will update you once I hear back from them. Appreciate your patience.