Error in the "2D Plan Preview" of a schedule for an object using the GLOB_ID parameter

[Victor Vernaglia]

I created a very simple GDL object just to display a text and two lines. The text uses the GLOB_ID parameter, which refers to the element ID. In plan view, it appears correctly. In the example shown in the attached images, I have two objects named “OBJECT 1” and “OBJECT 2” (Image 1).

However, in the schedule, under “2D Plan Preview”, both objects appear as “OBJECT 1” (Image 2). Why does this happen? The correct behavior would be for the schedule to display “OBJECT 1” and “OBJECT 2”, just like in the Element ID column.
I tried using the “Refresh > Rebuild and Regenerate” command, but it did not work.

SCRIPT:

DEFINE STYLE "TEXTO"      arial, 2, 2, 1

SET STYLE "TEXTO"

TEXT2 0,0, GLOB_ID

line2 -.5,0,.5,0

line2 -.5,-.2,.5,-.2

[Laszlo Nagy]

The question is how is the 2D of your Library Part generated. Can you open the Library Part for editing, and post screenshots of its 2D Script, 2D Symbol, and 2D View?

[Victor Vernaglia]

The object is very simple. I created it only as a test for another, more complex object that was showing the same problem.

In this object, I did not create any new parameters, and the Master Script, 2D Symbol, and 3D Script are empty.

[Laszlo Nagy]

It works for me in the Schedule. Also, if I create a Text variable, and write its value using the TEXT2 command, it also works in the Schedule.

I am using Archicad 29.

I am wondering if you write GLOB_ID in the 2D Script instead of glob_id, doe sit make any difference?

[Victor Vernaglia]

Initially, when I insert the objects, the “2D Plan Preview” works correctly and shows the same texts as the “Element ID” column. However, when I apply the “Refresh > Rebuild and Regenerate” command in the schedule, the “2D Plan Preview” changes and starts showing the same text for all objects.
I tested this in Archicad 29 and Archicad 28, and I got the same result in both versions. I also tested it on other PCs, with the same behavior.

 

[Laszlo Nagy]

Unfortunately, I have no idea why it stops working after functioning correctly initially.

Please report this as a bug to your local reseller.

[Victor Vernaglia]

I opened a support ticket with Graphisoft and I am waiting for their response. If anyone would like to test whether they get the same result as I did, I have attached the GDL object and the table’s .xml file.

[Victor Vernaglia]

I received a response from Graphisoft, and they confirmed that the issue is a bug, registered as DEF-27091. They also proposed a workaround that worked. Sharing it here for anyone facing the same type of problem.

The alternative is to add a parameter (perhaps hidden?) and define it as GLOB_ID in the Parameters script using PARAMETERS GLOB_ID_=GLOB_ID, as shown in the attached screenshot.