Step 2 is titled Entities & Fields (View Only), and that title is the most important thing on the screen.

There is nothing to choose here

EaseLog captures every entity and every field. You do not select what to audit, and there is no subset to pick. The checkboxes are inactive because there is no choice to make.

This step exists so you can see what will be captured before you commit.

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.

Select Next when you have finished looking.

What the list shows

Column Meaning Display Name The entity's friendly name. Schema Name The name the system uses. Metadata ID Its unique identifier. Type For example Standard or Virtual. Enable Audit Whether Dataverse auditing is already available for it.

Expand any entity to see its attributes, each with its own Display Name, Schema Name, Data Type, Status and Enable Audit.

The one action available: enabling auditing

Enable Audit shows one of two things.

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

This is the only thing you can change in step 2, and it is worth doing while you are here. See Enabling Auditing on a Field.

Why it matters more than it looks

EaseLog reports on audit data. It does not create it. Dynamics 365 does the auditing.

So an entity or field without auditing enabled produces no audit records, and EaseLog will have nothing to show for it. Worse, auditing you enable today starts recording today. It cannot fill in the past.

That makes this step the moment to notice a gap, rather than discovering months later that the history you need was never recorded.

Note

The full list is long, because it covers every entity in your environment including system ones. The wizard Summary in step 4 shows the total, which commonly runs to a couple of thousand entities.