Null value needed for dimensional parameters with scheduling capability

[bosborne]

Dimensional parameters (i.e. length, area, volume, force, etc) cannot have an empty value - their default is 0.  In some cases this is ok, but in other cases getting a value of 0" is incorrect if perhaps the parameter does not apply to a particular case.  

Example: We have this issue very often where we have 5 dimensional parameters for specifying the depth of a post-tensioned tendon from the top of a beam. The schedule has columns for all 5 parameters.  In some cases, all 5 are used, while in other cases we may only need 3 or 4 of the 5 parameters.  In these instances, the remaining unused parameters read 0" - which is not correct, the tendon should not be 0" from the top of the beam.  That parameter should really read "-", as in "does not apply" or "ignore me".

What we need is some way to specify a null value to parameters that have units so that they can read either the default null (displayed as either a blank or as a dash "-"), or as a value with units.

Alternatively - if we could mix strings and dimensions in a schedule and do some dimension to string casting in calculated values, we could test: if(value == 0", "-",value).  Currently this is impossible because "-" is a string and value is a dimensional parameter.

[darwin_valenzuela]

Dimensional parameters definitely need this. But as an extension, I would add non-dimensional parameters could benefit from this. As an example the attached schedule shows the reinforcement as blanks. These parameters are text parameters. This, submitted as a conceptual issue, has the dimensions but deliberately omits reinforcement, to be added (or disclosed) later.

The way I envision this implementation is that there would be a graphical switch applicable to the column where null/blank values would automatically be filled with some text string, “---“ for example.

Historically, (structural) engineers fear blank cells in schedules as a liability in case of problems, lest some one fill a value in after the fact....

[lionel.kai]

Related idea: be able to reset parameter to NULL

[joakeson]

This should be a no-brainer.  Null is a very significant parameter that could be used in conditional formatting, view filters, etc across all trades.  There is a huge difference between 0 and null.  Currently right now, only the zero parameter can be flagged by conditional formatting.  All of the other devices that have no data entered into them, that should, show as null but you can't flag those ones.  This is an across the board upgrade to everyone.  Quite frankly, I'm shocked this isn't already in there after more than 6 or 7 years of using Revit.  When I took programming in college, every program had a way to identify null (array was empty, variable had been created but assigned no value, etc)  This is a big hole in our quality control desires.

[Anonymous]

This causes many issues during tagging and it would be great if null value could be input, instead of zero. 

[YarUnderoaker]

This is so simple task for developer, maybe one day of coding and testing, but during years not yet implemented, sad...

[ebiesingerKWR5M]

i agree, its such a simple change but being able to differentiate null values and use then in conditional statements (especially for calculated parameters in sche4dules) is necessary. This need to be addressed

[ccherryWY7LZ]

Now coming up on 8 years of this post being created with no resolution, i have seen countless other post with an issue similar to this.