EaseLog can only collect audit data that Dynamics 365 is recording. Where an entity or field does not have auditing enabled, you can turn it on from inside EaseLog, without going to Dynamics 365 to do it.

Where to do it

Step 2 of the Connect to Environment wizard, Entities & Fields (View Only).

Figure 1. Step 2, Entities & Fields (View Only), listing every entity with its schema name, type and audit state. An entity expands to show its attributes.

Reading the Enable Audit column

What you see Meaning Available Auditing is already enabled. Nothing to do. An enable control Auditing is not enabled. Select it to turn auditing on.

The column appears twice: on each entity row, and again on each attribute when you expand an entity. So you can enable auditing for a whole entity, or for one field within it.

Enable auditing

1. Find the entity in the list. Expand it if you want a specific field.
2. Select the enable control in the Enable Audit column.

The timing point that matters most

Auditing records from the moment you enable it. It cannot fill in the past.

Enable auditing on a field today and you get changes from today onwards. Changes made yesterday were never recorded, so there is nothing for EaseLog or anybody else to recover.

This is the single most consequential thing on this screen. A field you leave un-audited is a question you will not be able to answer later.

What to enable

Enable auditing where the answer would matter:

• Fields carrying money, entitlements, permissions or status.
• Fields subject to a regulation or a contract.
• Fields where a dispute is plausible, such as anything a customer might query.

Be more careful about enabling everything indiscriminately. Auditing has a cost in volume and storage, and very chatty fields updated by automated processes can dominate your audit data without telling you much. The Entities & Fields tab of the Dashboard shows which fields generate the most change once you have data. See Entities & Fields: What Is Creating the Noise?.

The balance to aim for: audit what you would need to explain, and leave the noise alone.

Note

This changes a setting in Dynamics 365, not in EaseLog. The effect is the same as enabling auditing in Dataverse directly, and it applies to anything else reading that audit data too.