Table-Based Properties with External Data Support

[Pedro Melo]

Currently, Archicad properties can use single-value lists (option sets), text, numbers, or expressions — but often in real-world workflows, we need structured data with multiple related values. I'd like to propose a new type of property: Table-Based Properties.

This would allow users to create or link to a multi-column table (like an Excel or CSV), and assign a row to an element. Each column in that row could represent a related value (e.g., code, description, unit, cost, etc.), with control over which value is used where (display, label, schedule, export).

---

Core Features:

• Property type: “Table Lookup”

  • Users select one row from a table

  • Each row includes multiple columns (fields)

  • Users can choose which field to output/display per context (label, schedule, IFC, etc.)

• External Table Support:

  • Link or import data from CSV or Excel files

  • Update or refresh table content when the source changes

  • Could also be managed in the Property Manager

• Selectable Fields for Output:

  • Example: Pick a row for a wall type → Schedule displays cost, Label shows description, IFC exports classification code

• Optional Field Mapping:

  • Define which column maps to which IFC field or Archicad property (e.g., “Cost” → Classification, “Weight” → Quantity)

---

Why This Is Useful:

• Reduces Redundancy: Avoids having to create multiple properties (e.g., Material Code, Description, Cost) and maintain them manually

• Supports Data-Rich Workflows: Ideal for specification management, classification systems, pricing, cataloged components, etc.

• Improves Consistency: Selecting a single row ensures all related values are in sync — no more mismatched descriptions and codes

• Connects with Excel-Based Teams: Lets non-Archicad users (specifiers, cost consultants) maintain data that syncs back into the model

---

Example Use Case:

For a wall element, select “W-01” from a lookup table:

Code	Description	U-Value	Cost/m²	Fire Rating
W-01	Ext. Insulated	0.25	85.00	90min
W-02	Internal Stud	0.50	40.00	30min

• Label shows: “Ext. Insulated Wall”

• Schedule shows: U-Value, Cost

• IFC export includes Fire Rating

---

This kind of structured property would bring Archicad closer to data-driven design and connected workflows, making it easier to manage specifications, cost plans, and compliance data in complex projects.

---

This could work beautifully alongside Archicad’s Property Expressions and Python API — let me know if you'd like a combined post about advanced data workflows!

[s_p_b]

This is a really well-explained proposal, and I can think of many applications - luminaires, furniture, millwork, storage systems, really anything which can be fully described in the specifications and just needs a symbol on plans to show its location.

There have been other wishes for a system of 'instancing' objects so that their parameters can be kept consistent with a certain type they're meant to be members of, and it seems to me that GS needs to develop a system for creating relationships between object parameters and properties. It is frustrating that GDL objects still cannot access their own properties, and well defined 'types' pretty much need to be hard-coded into custom objects.

[s_p_b]

In a schedule, I would imagine that you'd have the option to pick which field of the table record should be displayed, similar to how classifications can be displayed by Id, name, or description

[Christian Muntean]

This would be a great addition indeed!