Alternate AKA Information Requirements Names ("Property Aliasing")
under review
C
Craig Walker
Allow users to add an additional column (or field) for alternate names (e.g. "Name #2" or "AKA") when defining information requirements. This helps support workflows where the same parameter might have different names across multiple modeling platforms. The system should recognize either name when checking against model elements for compliance.
Created by Louie Moran
T
Tadas Valionis
Definitely useful, especially as ArchiCAD and Revit export some parameters under different names/logic.
Clive Jordan
marked this post as
under review