Dependent Items as trigger name macros, not last data

[janlange]

I have an item to look at an windows event log. To parse the output I have made two dependet items with reg exp preprocessing. These values I want to use in the trigger name.

Triggername: Neuer Benutzer {ITEM.LASTVALUE1} angelegt durch {ITEM.LASTVALUE2}

Triggerexpression: {Windows Event Log - Usermanagement:event.usermanagement.accountname.st r(NULL)}=1
or {Windows Event Log - Usermanagement:event.usermanagement.requestorname. str(NULL)}=1
or {Windows Event Log - Usermanagement:eventlog[Security,,,,^(4720|4726)$,,].logeventid(4720)}=1

problem 1: it triggers two or three times at once, after one event.
problem 2: it shows not the lastvalue, of the actual data, instead the last historic data in item.lastvalue1/2.

Any ideas?

See screenhots. I only have added user test13 and test14. But he also displays test12 (that was already added and triggered)

[janlange]

Thank you for your explanation. I have solved it myself with ITEM.LASTVALUEx.regsub() function directly in the trigger name and reduced it to only one item.

Now it works.

[cyber]

Problem with triggers using multiple items, is, that they get recalculated each time any of items gets new value. Even if they are dependent items, there is a very-very small delay between storing them (like.. maybe a 10 thousands part of second). Trigger like yours gets 3 recalculations at very short time. And that may also cause the other issue... if your 3rd item gets its data first, (which is presumably true, as it is a main item and others are dependent ones), then during recalculation, there is yet no "new" value for other two items, what you are displaying in trigger name. So it seems like it is displaying previous value, but in real life, that is the ITEM.LASTVALUEx of that moment.

This is often seen also as 0 length Problems.0 sec is actually 0.000000x between 2 items receiving values and 2 recalculations opening and closing the event..