Bug when Renaming Attributes in Dynamic Component

[nathan_storybook]

I’ve found an annoying bug when renaming dynamic component attributes.

If an attribute name is height for example
And another attribute is named sashheight
And the value of another attribute “test” is a formula (=height-sashheight-6)

If you change the name of the “height” attribute to say “aaheight”
Then the formula in the “test” attribute changes to (=aaheight-sashaaheight-6)

I often need to change the attribute names so they order in the options menu. This bug means I break a lot of formulas when I change an attributes name.

Anyone found a workaround ???

Here’s the link to my test file

[Geo]

@nathan_storybook

Here’s the link to my test file…

File not shared…

[jim_foltz]

Can confirm. Renaming an attribute appears to rename any other attribute that merely contains the original name.

[Geo]

@nathan_storybook

I often need to change the attribute names so they order in the options menu.
This bug means I break a lot of formulas when I change an attributes name.

Anyone found a workaround ???

AFAIK there’s no way to order/reorder attributes other than by the way they sort by name.
In situations where order in the Options dialog is important, I setup the aesthetics of the Options dialog first.

A simple letter prefix for each custom attribute establishes their order.

A_name
B_name
C_name

Establishing attribute order ahead of time doesn’t fix the bug, but it does help avoid it.

Dynamic Components Options

I letter them A, B, C … to establish the order. But that doesn’t mean the lettering has to be visible in the Component Options display. Click the blue Details icon to open the Info dialog and enter whatever Display label you want.

[jim_foltz]

Here’s an image showing the problem.

So when we rename the height attribute to zz_height, the sash_height attribute is renamed in the formula of total_height.

Also, the total_height shows no error even though sash_zz_height is not a valid attribute name.

.

[nathan_storybook]

Yeah, this is what I found. Geo’s workaround to the problem (ie; starting with a unique name to begin with) stops this from happening, but it is a bug if you ask me, and very annoying…

[atsu85]

There seems to be a similar problem when renaming dynamic component object name (when some attribute from that dynamic component is used in formula for another object).
It screwed up my whole model - it was too late when i noticed the corrupt formulas Should start to make backup files every now and then