Microsoft Dynamics CRM Online Help

Tracking changes for entity relationships

In Microsoft Dynamics CRM Online, audit tracking for entity relationships is handled differently than audit tracking for entities or fields. Here are some examples of how they are audited:

Entity Relationships

Scenarios

What is audited

Summary

1:N

Contact associated with a parent account

If auditing is enabled for the Contact entity, the changes to the parent account reference is tracked.

If auditing is enabled for the Account entity but not for the Contact entity, no change will be tracked for this transaction because the Account entity did not change.

In a 1:N relationship between entities, the change is reflected only on a single entity. Only changes to the entity that changed are recorded, provided the entity is enabled for audit.

N:N

Lead added to a marketing list

If auditing is enabled for the Lead entity, the marketing list it is added to is tracked for changes.

If auditing is enabled for the Marketing List entity, the lead that is added is tracked for changes.

In an N:N relationship between entities, the change is captured on both entities, provided that the entities are enabled for audit.

If auditing is enabled for one entity, the association of this entity with the other entity is tracked.

Special Cases

Lead added to an activity, such as an e-mail activity

If auditing is enabled for the e-mail entity, e-mail activity is tracked for changes.

If auditing is enabled for the Lead entity, nothing is tracked because the Lead entity did not change.

When the N:N relationship involves certain type of entities, such as an ActivityPartyBase or a PartyList, the relationship internally is handled as 1:N and the changes are tracked only on the ActivityPartyBase entity or the PartyList entity, provided ActivityPartyBase or PartyList is enabled for audit.

Related Topics

Configure and Manage Auditing

View Audit Summary

© 2012 Microsoft Corporation. All rights reserved.