topic Re: IFC Property Mapping & Incorrectly Merged Items in Schedules in Project data & BIM

IFC Property Mapping & Incorrectly Merged Items in Schedules

Gerry Leonor — Fri, 08 Aug 2025 13:19:18 GMT

is there any reason why only a single Surface is displayed in a schedule and not the others?

The full Surface name to called up is G1: glass: Viridian: Evantage "Grey": --

this is assigned to the glass surface of a window & I have this mapped to two IFC properties with Split operations ( ":" delimeter) & both are called up to a schedule:

however only G1 is displayed despite all the other surfaces are called up in the schedule (G2, G3 & even a test Surface "TC-") when the items are Unmerged.

Operating system used: Windows 11 24H2

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

Laszlo Nagy — Fri, 08 Aug 2025 13:30:45 GMT

What I am noticing on your schedule, when items are not merged:

The "Glazing Description" IFC Property has a correct value ("Viridian.....").

All the others do not seem to have a correct value as they start with "--" characters. That may indicate that the IFC Property mapping did not work as expected in their case, maybe? And that could be ther reason for them missing in the Schedule when items are merged?

So, I would try to solve this so that their "Glazing Description" IFC Property is correct.

By the way, is there any reason you are doing this using IFC Properties? You should be using Archicad-native Properties and use Property Expressions. (There is no need for the use of IFC Properties since native Properties were introduced around Ac20-21 - unless something cannot be done using Properties, but can be done using IFC Properties.) Then, if you need to export these in IFC files, then you could map the values of the Properties to those IFC Properties for IFC Export.

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

Gerry Leonor — Sat, 09 Aug 2025 10:30:59 GMT

to answer the second question, unfortunately AC Properties do not provide an option to call up Surfaces for Doors & Windows

this was an extension to my previous question from December of last year which, thanks to your help, it worked for me by bringing in the Parameters as Add as Library Part Independent.

cheers for that. I'm now able to a schedule in our Notes & Legends page that calls up these Glass codes with their description. unfortunately the error with the Merge Items come up. going back to the first question...

i forgot to screenshot the Mapping Rules & Rule Content of these IFC Mapping:

if you allow me to elaborate for posterity's sake / interested people:

Glazing Description (Sp_Glazing) is a combination of two Rules from one Library Parameter. this Parameter calls up the glass surface of the window. the Surface name is composed of:

(code): (material): (manufacturer): (description): (item code if available)

G1: glass : Viridian: EVantage "Grey": --

G2: glass : --: clear float laminated/toughened (as req): --

the ":" is delimeter / splitter and i've added a single dash to separate between manufacturer and description when it appears in schedule. this is the reason why it previously showed as "-- - Glass frosted..."

i added test 1 and test 2 in the surface names to differentiate them, but G2 & G3 still don't appear in the Merge Item version of the schedule

even adding "test" in the Glass Code doesn't fix it. it still gets Merged

hell, even TC- gets combined...

the only element this schedule is calling up are Windows. no Doors. i wonder if this is a bug in the schedule? shame -- because i really thought i could push through & automating some parts of the Notes & Legends Page.

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

Laszlo Nagy — Sat, 09 Aug 2025 13:05:44 GMT

OK, I see why you are using IFC Properties.

Can you try something? Can you modify the Surface name of, e.g., G2 so that the name does not have "--" for Manufacturer in it? Just like Surface G1? I would like to see if it is the content of Surface Name that may be the reason for this issue or not.

Another question: are those G2, G3, and TC items doors or windows?

Could you also post a screenshot of the Scheme Setup Dialog for this Schedule? The one with the Criteria and Schedule fields?

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

Gerry Leonor — Mon, 11 Aug 2025 09:27:00 GMT

unfortunately, still no joy after ensuring there are no "--" in the surface names.

the only "-" is in the IFC Rule

for now, these rules are set only for IFCWindow. it's probably a mistake at my end & it should've been higher up in the heirarchy -- OR i duplicate this for the Door later on if/when it works. the Timber surface was just something outrageous for me to use to double-check that things were working fine. obviously we won't be calling up a Timber surface for what's meant to be glass.

screenshot below of the Schedule Scheme:

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

Laszlo Nagy — Mon, 11 Aug 2025 09:44:11 GMT

Very curious. I don't see anything wrong with the Schedule Scheme either.

Are these all the same Window library part? Or are there any differences like G1 is a specific Window Library Part, and G2, G3 are other Window Library Parts? I am trying to find what could be the difference between the elements that appear and ones that don't.

By the way, I think it is good that you created these IFC Properties on the IfcWindow level of the IFC hierarchy because you are using a Window-specific GDL parameter in the IFC Property mapping rule. It is probably better to just do the same for IfcDoors than go one level higher.

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

Gerry Leonor — Mon, 11 Aug 2025 23:08:23 GMT

it's using the Window 27 object, but the placed windows use the Horizontal Multi-Sash Window 27 object.

i understand it shouldn't matter, but i made another Rule & grabbed the IFC Parameter from the Multi-Sash object just to check & it still merges incorrectly.

i also tried to see if the Merge command is looking at another parameter -- perhaps the element ID (just throwing it out there), but i've got a few windows with differing IDs already, despite not yet numbering any at this stage:

at this point, i'm guessing this is a bug. the Merge command in the Schedule must be looking at something else & not necessarily the end result of the split command of the IFC Rule. i wonder if it's too deep in the coding / IFC Ruling for the Schedule to do Merge correctly...unfortunately this stops the ability of automating the Notes & Legends page for me when it comes to surface callups -- at least the doors and windows, for now.

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

AllanP — Tue, 12 Aug 2025 06:19:56 GMT

Hi Gerry,

what are the merge setting you are using?

click on the first column, click on the "double square" at the end of the column to get the settings (it hides...)

this normally causing problems for me when merging items in ArchiCAD 25.

Regards

Re: IFC Property Mapping & Incorrectly Merged Items in Schedules

Gerry Leonor — Tue, 12 Aug 2025 20:53:49 GMT

yup -- i think that fixed it...

didn't know about the Field Merge Options & also both the Headline & Heading were both hidden.

had to do a quick read on AC27 Help to find out more.

thanks champ!