Timeline - Rename Feature - Unexpected behavior

Timeline - Rename Feature - Unexpected behavior

Christoph_360
Collaborator Collaborator
556 Views
3 Replies
Message 1 of 4

Timeline - Rename Feature - Unexpected behavior

Christoph_360
Collaborator
Collaborator

Hello

 

Christoph_360_2-1725601853758.png

 

When I want to Rename this Feature, "RemoveInstance" cannot be deleted from the Comment, but it makes the Comment very confusing.

 

Christoph_360_0-1725601002687.png

 

This also makes the Comments in the Configuration Table very confusing.

 

Christoph_360_1-1725601178700.png

 

Is there a possibility that this Feature behaves the same as the other Features when renamed?

 

 

Thanks

 

Christoph

0 Likes
Accepted solutions (3)
557 Views
3 Replies
Replies (3)
Message 2 of 4

gautham_kattethota
Autodesk
Autodesk
Accepted solution

Hi @Christoph_360 

Many thanks for reporting this issue.  We can reproduce it and have created a defect to track it.  We will be looking at fixing this in the near future.  Although I can say that this issue itself is minor, the fact that it affects in downstream workflows in the Configuration table makes it more important for us to fix, given the wasted real estate in the Configuration dialog when you expand the columns to view the full name.

 

Regards

Gautham



Gautham Kattethota
Software Development
Message 3 of 4

gautham_kattethota
Autodesk
Autodesk
Accepted solution

@Christoph_360 

Happy to inform you that we have fixed this defect and it will find its way to a future Fusion update in a few months.  This was a good find, and thankfully it didnt take us long to fix it.  Thanks again for reporting.

 

Gautham

 



Gautham Kattethota
Software Development
Message 4 of 4

Christoph_360
Collaborator
Collaborator
Accepted solution

Hello

 


@gautham_kattethotawrote:

 

Happy to inform you that we have fixed this defect and it will find its way to a future Fusion update in a few months.  This was a good find, and thankfully it didnt take us long to fix it.  Thanks again for reporting.




Thanks, works fine with the new update.

 

Christoph