Microsoft Dynamics 365 | Integration, Dataverse...

Auditing configuration impacts from multiple solutions

(0) Share

Report

Posted on by Noodles2302

I am looking to understand how Attribute or Entity auditing definitions are affected by multiple solutions.

For example, if i have the definition of my entity in Solution A, which also specifies that attributes A1, A4, and A5 of Entity E1 are to have auditing enabled and all other attributes for that entity disabled for auditing and Solution B which extends Entity E1 with additional attributes BA10, BA12, BA20, with auditing enabled across the entire E1 entity, will this result in all attributes being audited? What if only attribute BA10 was enabled for auditing in Solution B, what will be the resultant auditing setting for attributes A1, A4, A5? Will the "enabled" setting from Solution A be preserved?

All responses (2)

Answers (0)

Noodles2302 30 on at

Like (0)

Report

RE: Auditing configuration impacts from multiple solutions

Thanks for the reply Bipin.

Can I just confirm your last point?
[quote user="Bipin Kumar"]If Solution B does have those fields which are part of solution A then it will be preserve the settings from Solution A.[/quote]
Did you mean "If Solution B does not have those fields which are part of Solution A...."?
Suggested answer

Bipin D365 28,959 Super User 2024 Season 1 on at

Like (0)

Report

RE: Auditing configuration impacts from multiple solutions

HI,

It will override the auditing settings of Solution A by Solution B field property. Only last solution import takes precedence.

If Solution B does have those fields which are part of solution A then it will be preserve the settings from Solution A.

Check below article to understand this clearly.

docs.microsoft.com/.../introduction-solutions

Please mark my answer verified if i were helpful