I have updated my Area value to parameter Script as per below. I have originally set it up for standard 4 areas namely: Porch, Ground Floor, Outdoor Living and Garage. However, I am getting a value from O.living even though this is not existing in this specific job that I am running the script. I am not sure where the Value for OLiving is coming from if it is an empty list when I ran the script. Can anyone offer an explanation and fix on how to make sure that this does not happen? Thank you in advance.
Are you sure O.Living got a value after running the script and it didn’t already had that value?
Also pinning all the preview bubbles would help a lot. At least for the ones that matter like
Element.GetParameterValueByName.
1 Like
Yes thank you. I was able to find the missing O.living Area that generates this value and was able to clean it up. However cleaning up the unused / unbounded / not placed areas is a bit tedious especially when I have removed a lot of design options from out master file.. I may need to find a script that efficiently delete this. Thank you again for your response. Cheers
This isn’t a dynamo bug; it’s just Revit Area Schedule behavior. Even though they are not visible, Revit retains orphaned or misplaced regions (often from outdated design options or schemes), and the schedule still assesses them. Dynamo simply reads the results of the revit.
A fast fix is to filter your Dynamo areas before writing values. Make sure Area > 0, adjust AreaScheme, and remove NotPlaced areas. Otherwise, Element.Zombie data will continue to be pulled by GetParameterValueByName.
In summary, you need to filter or remove the leftovers; Revit isn’t forgetting anything.
1 Like