one to many and many to many relations are not audited

(0) Share

Report

Posted on by Billy

396

Hi there,

I have been looking around how to implement audit logs, and I have read in the documentation that it is possible to measure relations as well, both one to many and many to many. Now I have been trying to measure such relations, but it seems that it isn't possible to measure this, unless I am doing something wrong or the documentation is not correct/deprecated?

I know that you can enable audit on fields, but this is just for the N:1 relations. When you have a project you can view the audit logs on the invoice but not on the list of orders from the project perspective since invoice is an N:1 (lookup field) but orders is a 1:N relation.

I thought this was possible because under the Supported for Audit header: "Audit of relationships (1:N, N:N)" is included.

So far, I have found zero references on how to enable Audit logs for 1:N and N:N.

So can someone please tell me how to enable this or if this is no longer possible?

Thanks in advance!

Billy Cottrell

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Ram Prakash Duraisamy 5,699 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello @Billy_C,

We cannot Audit N:N relation.

If you want to log the Relation for 1:N, add the respective lookup in the form to make it Auditing. Make sure you will enable Audit for lookup field to track the same.

Let me know if you need more clarity.

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

Was this reply helpful? Yes No
Billy 396 on at

Like (0)

Report
Copy link

Link copied!

Hi @rampprakash,

I see, so I can assume that 1:N relations won't work either then, since the lookup fields reside in the related entity (N side).

In that case, the following documentation on this is deprecated and should be updated correspondingly, as it gives a wrong impression of the possibilities of this feature.

Thanks in advance,

Billy Cottrell

Was this reply helpful? Yes No
Verified answer

Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @Billy_C ,

As mentioned by @rampprakash you will be able to see the lookup field on the N side in the audit if you have that lookup field audited but you would not be able to see on the "1" side that a new record was included as part of the audit.

If you have a need to track this type of auditing in the N:N world, you might want to manually create the intersect table in the middle of this relationship so you have the ability to turn on auditing of the two lookup fields on this intersect entity to track changes.

Example, if you have an N:N relationship for entities A and B you could create a table in-between so you have

A --> AB <-- B

where AB would have lookups to A and B and you would audit these fields on the AB table.

Hope this helps in some way. Please accept if answers your question or Like if helps in any way.

Thanks,

Drew

Was this reply helpful? Yes No
Fubar 8,487 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Technically they are audited, you just cannot see it against the Records themselves (except as previously mentioned by others if it is a 1:N and you view the Child record and can see the lookup field change).

You need to go to Settings->Auditing->Audit Summary View and look for the "Association" events Associate Entities and Disassociate Entities.

Was this reply helpful? Yes No