Microsoft Dynamics 365 | Integration, Dataverse...

Track who made metadata changes like adding attributes, editing forms, or modifying Optionsets?

(4) Share

Report

Posted on by AnandM

Hello everyone,

I have a general question that has become more relevant due to a current issue. We are using unmanaged solutions for our deployments, and it appears that someone may have directly edited an existing option set in a higher environment. While it's possible to check with all users who have customizer or admin roles, this approach isn't ideal, and it often leads to no responses since no one acknowledges the changes.

Is there a way to track who has made customizations in an environment, such as creating new forms, adding or deleting attributes, or modifying attribute definitions?

I would like to explore options to generate a report that can help identify this type of behavior. Any guidance or suggestions would be greatly appreciated!

Thank you in advance!

Categories:

Dynamics 365 general

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Vahid Ghafarpour 12,228 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Microsoft Power Platform provides Audit Logs that can help you track changes made in your environment.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/customization-analysis-report

https://stoneridgesoftware.com/dynamics-ax-customizations-report/

Was this reply helpful? Yes No
Suggested answer

Tom_Gioielli 3,084 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I am not aware of any auditing reports that track customization updates and changes to metadata.

If you have multiple users with admin priveleges that may make changes, you can always try to implement a more stringent deployment process through environment level permissions while still being unmanaged solutions. For example, your configurators only have access to the lower level environment to make changes, and you have a deployment account or single user authorized for production. It can add more overhead to your deployment process, but can save you a ton of headache when something like this happens.

You could also assign each user with permissions their own publisher. That way, any fields they add are "tagged" with their prefix, and you can define the first set of numbers in a custom option set value to be unique to them. You can't force users to do everything through their assigned publisher, but it might help?

Creating a Publisher in Dynamics 365 and Power Platform

Was this reply helpful? Yes No
Suggested answer

Ali Hamza 170 on at

Like (0)

Report
Copy link

Link copied!

I think OOB its not possible.

What you can do is can retrieve metadata or Entity Definitions using Web API call and track the modified on date. But it still will not show which user has changed the column or table attributes / properties.

For instance for account we can get all choice attributes with below request

ORGURL/api/data/v9.2/EntityDefinitions(LogicalName='account')?$expand=Attributes($filter=AttributeType eq Microsoft.Dynamics.CRM.AttributeTypeCode%27Picklist%27)

Was this reply helpful? Yes No