I appreciate all your help Gerry. That sound like a deal breaker though...as I imagine changing the units in all tables would have unwanted consequences...
What I still don't understand is why the property values get added together for identical items when the property is an expression. The schedule clearly does NOT add together the values that are returned by the basic 'Width' and 'Length' parameters, even with the 'Merge Uniform Item' option checked. It only happens in the column driven by the expression.
I would have expected the schedule to not know the difference, and not discriminate between data returned from the basic property 'Width', and data returned from the exact same element attribute delivered through the use of an expression simply pointing to that very same property.
ie: If 'Width' = 10, and 'Expression (Width)' also = 10...why does the schedule multiply 'Expression (Width)' x 'Quantity', but not 'Width' x Quantity?
First, I hope that you and your loved one are doing well during these challenging times!
Thank you for your question!
Reading through the thread, I guess the question now is why
Merge Uniform Items
sometimes take the summary of similar items, but sometimes not?
In your particular case, I believe because the
value has gone through an expression, therefore, schedule has no way of telling
is similar to
. Thus, Merge Uniform Items will add all value from similar items into one cell when activated.
In general, I sometimes don't understand why some parameters get the total, while others get only singular value. Barry showed a great example of that issue: let's say we have 2 identical walls. In Walls schedule, if we activate
Merge Uniform Items
parameter is not added up together, whereas
Length of Reference Line
does, which is hard to understand for me. The same goes for Zone areas and more.
I will ask the developers to see their opinion about this issue!
Thank you very much!
Technical Support Engineer