This page describes how to create Calculated Attributes in dRofus. Using the Calculated Attributes feature, you can build formulas dynamically using available dRofus fields to create additional fields. Calculated Attributes are available for Rooms, Items, Occurrences, and Products and allow you to build simple to very complex results. We explain how to do this for Room Calculated Attributes, and on this page, we will go over how this can be done for items. The Calculated Attribute Formats are the same across dRofus. A good baseline understanding of how Item Composite Text Attributes work is a great place to start since the rules can be combined with these attributes. The Room Subtraction Example was a simple one that could be applied to items, but we will go more complex for this example.
Info |
---|
You need admin access to the database to create calculated attributes, as the setup is done in the Administration settings. Please refer to Project Administrator. |
Note |
---|
This feature can not be exported to xml or PDF, but is available in Excel Exports and Revit/ArchiCAD Add-On configurations. |
Item If/Then Example
You might be familiar with if/then formulas if you have ever built complex rules in Excel. The syntax of IF-THEN is = IF (logic text, value if true, value if false). The first argument tells the function what to do if the comparison is valid. The second argument tells the function what to do if the comparison is false. A quick search on the internet will result in several examples of this concept. In our example, we will use several rules to pull from item data to inform some results. If you have ever tried to determine Door Calculations, you will want to bookmark this page and impress your office. Our team in Australia came up with this idea, and we all think it’s a great example of using item data to inform other decisions.
...
Clear Opening combines subtractions with if/then formula to determine the clear width available for any person or object to pass through when the door is fully open. The calculation takes into account considers the differing calculations if identified as a single or double door.
We begin with the Panel A and B widths, ; if Panel A is zero, we are not concerned about the door as the required dimension have not yet been nominated. Then, if Panel B width is zero, we assume the door is a single door, ; the calculation then subtracts the Panel thickness, Frame Stop, and Hinge Allowance from Panel A. Finally, if Panel B is not zero, we assume it is a double door, Panel A and B are added together, followed by the Panel thickness and Hinge Allowance being subtracted twice.
...
Clear opening width is often dictated by compliance standards involving accessibility, ; this example has the potential to identify non-compliant doors during the planning and design stages.
...
When scheduling frames for ordering, the Panel size is often not the key information, instead Reveal Height and Width is are required; therefore, therefore the following two examples could be helpful for frame ordering:
Reveal Height is the simple addition of Panel height and the Floor finish allowance, ; if necessary, panel undercut and Floor finish allowance could be incorporated separately.
...
When doors are retrofitted or hosted in masonry walls, the structural opening size is required, the following two examples are a good example examples of using a Calculated Attribute as a field:
...
These examples show how important project calculations can be provided to all users , whilst while simultaneously ensuring the calculations are performed the same every time.
These examples aim to give you a sense of what is possible using item calculations.
...
Explore how to do this with Occurrence Calculated Attributes.