Forum Discussion

gmarc's avatar
gmarc
Icon for Advocate I rankAdvocate 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 t...
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

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
Icon for Advocate I rankAdvocate 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.

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      Hi gmarc 
      The internal team wants you to create a support ticket. If its a bug, we will definitely would like to know and properly address it. Please go ahead and raise a support ticket to reach our support team: Link 

      After creating a Support ticket please provide the ticket number as it would help us to track for more information.

      Thanks.

      • gmarc's avatar
        gmarc
        Icon for Advocate I rankAdvocate I
        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