In case there is a log entry within the XLR the entry dataset contains the
targetId


In order to get the complete visibility, one would need the
sourceId,
as well


Please, complete the log entry generation with this, in order to make the user able to process the data in multidirected/transitive way

Comments

  • Thank you the idea. Could you specify which logs you are referring to?
    Could you provide an example of a log entry where the sourceId would be useful? Specifically, what entity or reference should be considered the sourceId in your use case?