Can auditing be done straight in Production

(0) Share

Report

Posted on by PS10

Hi,

We are on-premise d365.

Long time back we had auditing enabled on many entities and fields which we don't even use, when our log files started growing we realised the issue caused by unnecessary auditing and turned it off.

Now we have a business requirement to turn on auditing on some sensitive entities and fields.

My question is, what should be the approach.

Shall i bring in all the entities enabled for auditing in the solution , turn on and off as required and import that solution? OR

I can turn the auditing on and off as required straight in the production, will this cause any issues? What will be the consequences with future solution patches?

Thanks,

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (1)

Report
Hi PS10,

When you export a solution from the development environment, the customizations.xml file will contain an IsAuditEnabled value of 1 for all entities with auditing enabled and a value of 0 for entities that do not have auditing enabled.

1

The ideal approach is to enable the entities in your development environment for auditing, export the entities, and import the solution containing the entities into your production environment. Making the changes straight in production has some risk so it is better to do the export and import.

Was this reply helpful? Yes No