Expression property custom value danger

[Mats_Knutsson]

To GS with love,

[Rajesh Patil]

Hi, I think "Expressions" are based on one way traffic. Data collected from source elements will be considered for further processing. Any end result from the expression cannot be send back to the source elements. Once you type the new value for expression based defined property then its get converted to "custom value" and the "expression" gets override. Setting back to "Default" will collect the information from the source.

 

[Francois_MCD]

Good point @Rajesh Patil but I agree with @Mats_Knutsson the reported data from an "expression" Property should be locked / unmediatable in the schedule / label. The only way to edit the reported data from an "expression" must be to actually edit the formula in the expression in the Properties Manager only (similar to an Option Set property).

[Mats_Knutsson]

It can NOT be as it is now. We use schedules for everything...quality control and adjustments alike. One of the key features with a BIM-tool is one single source of information (well data). I need to contact GS directly to check possibility for a hotfix to lock expression property values.

[Matthew Johnson]

If we can't get a way to lock the custom overiding of expression values, the next best thing would be to have an ability to have graphic overides in schedules to highlight were values have been custom edited rather than by their default expression.

[Andreas _kerlund]

Hi!

I totally agree with Mats. We have had so many cases where users have unwittingly have changed expression values in a schedule. The broken chain symbol in the objects properties settings tells you what have happened, but only if you know what you are looking for.

It needs fixing.