icon

[Question] How to create a script to copy the value of a 'Formula' typed attribute to an 'Entry' type attribute?

Tags:
  • Allplan 2026
uid-488369
uid-488369
29.10.2026 - 14:49 *

I have zero knowledge of Allplan's visual scripting, but I have some knowledge regarding programming and visual scripting in other software. The initial questions are:
- Is it easy enough to create a visual script tree which does the job of the title?
- Is it easy enough as someone doing it and post a screenshot?

The workflow I guess I need is to
1. Select all objects.
2. Filter them by type (I need all Reinforcing Bar objects).
3. Get the value of the Formula-typed attribute (of ID X).
4. Copy the value to the Entry-typed attribute (of ID Y).

I tried to see how I do with selecting objects and filter them, but I couldn't find my way around. I have not yet started to research online a lot, until I get some starters guidance (from here).

florian_keim
florian_ke…
30.10.2026 - 07:47

Hi, I’m not really familiar with reinforcement in Allplan, so I can’t help much with selecting and filtering the bars. But Allplan France has published some user nodes which might be useful for you, e.g. GetObjectAttribute and ChangeObjectAttribute to read and write attributes of existing elements: https://github.com/cmaignan-source/vsnodes
One question though: will attribute X be changed by the script, so that attribute Y should contain something different than the original value of X? If not, you don’t need a script. You can simply define Y as a formula attribute which refers to X.

Viele Grüße
Florian

Das "F" in Digitalisierung steht für Faxgerät!

LinkedIn-Profil

www.vollack.de

uid-488369
uid-488369
30.10.2026 - 08:10 *

I appreciate your reply!

I have started already experimenting a bit, so I am sure the templates you suggest will be of great help.

Your last comment is very correct -since I actually want the original X value- and I need to explain why I chose to go the visual scripting way. (Probably there is an even better solution.)

I recently found out that, as of Allplan 2026, some attributes (e.g. the total number of bars of the same Mark - @766@) show as they are supposed in Allplan environment, but they are exported with a different value to IFC files. Even if converted to a string or referenced by another attribute. The problem lies on the fact that these attributes were assigned different data originally (for i.e. refer to Allplan 2025) and they still get this value by the exporter in Allplan 2026, which is hard-coded and cannot be altered by the user. The only attributes that are exported, as they show in Allplan, are the 'Entry' type atts.

One way is to export the attributes to a spread sheet copy the values from the original att. to the Entry type and reimport them. In order to automate this process I would prefer a macro-style command to apply this copy-paste functionality. Since I also don't know much about Python scripting, I thought of the visual scripting method, as an easier approach to get what I desire. I am open to other solutions though...

EDIT: I managed an ugly-looking script. Unfortunately the above mentioned attribute would still pass the "wrong", hard-coded, value instead of the one that appears in Allplan. To be more precise for those who understand bar placements, if, let's say, I have 2 linear placements of 6 bars with the same Mark, totally 12 bars of this Mark, then the att. @766@ would show 12 in Allplan, but when copied to an Entry-type att. will show 6. Which is the number of bars in a placement and which was the originally assigned hard-coded data for att. @766@. I hope is a mismatch that Allplan is working to fix soon. Any other ideas to automate the process apart from the spread-sheet method?

EDIT2: Well, I spoke too soon. A misinterpretation made me believe that the above happened, but actually the script I made does not work yet. However, I have explained in more detail what I'd like to achieve.

EDIT3: So the conclusion is that it works somehow and the results are as described in the 1st EDIT. Therefore please ignore EDIT2.