icon

Support Forum

Issue with Separating Reactivation and Association Events Using execution_event in Allplan 2025

Schlagworte:
  • Allplan
  • 2025
  • 2026
doom235
doom235
27.11.2025 - 09:06

In Allplan 2026, we have the execution_event API to separate the reactivation PythonPart and the association PythonPart using eConnection and eProperties. However, in Allplan 2025, I can’t find any way to separate these events. Could you please give me some advice on how to achieve this?

Anhänge (1)

img
execution_event.png
Typ: image/png
15-mal heruntergeladen
Größe: 50,74 KiB

Hilfreichste Antwort anzeigen Hilfreichste Antwort verbergen

bmarciniec
bmarciniec
15.01.2026 - 12:35 *

Zitiert von: doom235
In Allplan 2026, we have the execution_event API to separate the reactivation PythonPart and the association PythonPart using eConnection and eProperties. However, in Allplan 2025, I can’t find any way to separate these events. Could you please give me some advice on how to achieve this?

Hi,

These events appeared in ALLPLAN 2026 in the BaseScriptObject and replaced the "is_only_update" property for better granularity when a PythonPart is being updated. IN ALLPLAN 2025 you can use "is_only_update" to distinguish between the case of a PythonPart being modified by the user or being updated. But note, that "being updated" can occur also in other situations, like change of plane references (if the PythonPart connects to any). I guess, it should be fine for your case.

  • In case of new PythonPart being created: both is_only_update and modification_ele_list.is_modification_element() evaluate to False
  • In case of reactivation, the first one evaluates to False, the second to True.
  • In case of an update (e.g. due to an association) both evaluate to True

Cheers,
Bart

bmarciniec
bmarciniec
15.01.2026 - 12:35 * [Hilfreichste Antwort]

Zitiert von: doom235
In Allplan 2026, we have the execution_event API to separate the reactivation PythonPart and the association PythonPart using eConnection and eProperties. However, in Allplan 2025, I can’t find any way to separate these events. Could you please give me some advice on how to achieve this?

Hi,

These events appeared in ALLPLAN 2026 in the BaseScriptObject and replaced the "is_only_update" property for better granularity when a PythonPart is being updated. IN ALLPLAN 2025 you can use "is_only_update" to distinguish between the case of a PythonPart being modified by the user or being updated. But note, that "being updated" can occur also in other situations, like change of plane references (if the PythonPart connects to any). I guess, it should be fine for your case.

  • In case of new PythonPart being created: both is_only_update and modification_ele_list.is_modification_element() evaluate to False
  • In case of reactivation, the first one evaluates to False, the second to True.
  • In case of an update (e.g. due to an association) both evaluate to True

Cheers,
Bart