IIRC, at some point they made some improvements to the contents of event-id for
an event as cached by dxevent.
Pretty sure this wasn't there in the really early versions, but my memory is
fuzzy and this opinion is mostly based on dusty examples from old cool
solutions.

Nowadays, one will see things like
Change Published to IDVault by another driver
---
DriverName#Publisher#number:GUID

Trigger
---
trigger-job:jobSetSomething#20180101110111#0#1

Direct/Replicated
---
ReplicaName#20180101110111#1#1:GUID

This last category seems to include also channel write-back (set source-attr
from a Null driver for example)

Does anyone know the following:

1. What the GUID item represents? Or even better a proper explanation of the
different iterations of event-id format.
2. Is there a way to get get changes from drivers to show up with the driver
name that made the change - even if that occured in a Null/Business Logic
driver on subscriber channel?

--
If you find this post helpful, and are viewing this using the web, please show
your appreciation by clicking on the star below