Import renaming notebooks

[gmarc]

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

[Anonymous]

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]

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]

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]

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 · Accepted solution]

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