I think you need a reference set (* - *), and in one of my apps where the AuditTrail module is functioning as expected, my Log entity is the "child". The association is thus visible from the entity I want to log and not visible in the properties of the Log entity.
Hope that helps!
Thanks for your input. I must confess that I always get confused in terms of knowing when I need to use reference set (* - *) as opposed to reference (1 - *). My thinking was that each element of the entity to be logged would have multiple entries in the log table but that each of entries in the log table would point to only one element of the entity to be logged. However, based on your recommendation, I will try to convert to a reference set.
However, the more that I look at it, the more that I think I either don't understand how an association (either 1-* or -) that crosses modules differs from an association between two entities in the same module. Shouldn't they look and behave the same if they seem to be identical in terms of direction of the arrow and 1-* or -?
Here is an example: I'm going to create two entities to be logged: one called EntityInAuditTrail that lives in the AuditTrail module and one called EntityInLabOps that lives in the LabOps module.
Next I create an association from AuditTrail.Log to AuditTrail.EntityInAuditTrail and one from AuditTrail.Log to LabOps.EntityInLabOps.
Finally, I check the association properties of all three entities:
Here are the association properties of AuditTrial.Log that shows both the LogEntityInAuditTrail and LogEntityInLabOps associations:
Here are the association properties of AuditTrail.EntityInAuditTrail that shows the Log_EntityInAuditTrail association:
But here are the association properties of LabOps.EntityInLabOps that doesn't show the Log_EntityInLabOps:
Shouldn't an association of any type show up in both of the entities ... even if those entities are in different modules? Even if I change these to ReferenceSets rather than References, I see no entry in the association properties of LabOps.EntityInLabOps. Is this a problem with cross-module associatins in BusinessModeler 5.16.1 .... or am I utterly clueless as to what I should expect to see?
Thanks for your consideration,