# How to Find Who Modified (and Created) a Plugin in Dynamics 365 CE / Power Platform (Dataverse)

In this post, we’ll look at how to query the **Plugin Assembly** entity directly to retrieve the creator and modifier details within **Dynamics 365 CE / Power Platform** using a simple GET request.

* * *

## The Challenge

The standard **Power Apps Maker Portal** and the classic **Dynamics 365 CE** interface often show when a solution was modified, but finding the specific metadata for a single assembly—specifically the **Modified By** and **Created By** system user details—can be a hassle.

## The Solution: Using the Dataverse Web API

Every plugin assembly in **Dynamics 365 CE / Power Platform** is stored in the `pluginassemblies` table. By targeting the specific GUID of your assembly, you can expand the record to include details from the `systemuser` table.

### The API Query

Replace `<your-org.crm.dynamics.com>` with your environment URL and `<PLUGIN_GUID>` with the unique ID of the assembly you are investigating.

HTTP

```graphql
GET https://<your-org.crm.dynamics.com>/api/data/v9.2/pluginassemblies(<PLUGIN_GUID>)?$select=name,modifiedon,createdon
&$expand=modifiedby($select=fullname,internalemailaddress),createdby($select=fullname,internalemailaddress)
```

### Breakdown of the Query:

*   `$select=name,modifiedon,createdon`: Narrows the results to the assembly name and the specific timestamps.
    
*   `$expand`: The Web API equivalent of a "Join," allowing us to reach out to the linked `systemuser` table.
    
*   `modifiedby(...)`: Retrieves the Full Name and Email of the user who last updated the assembly.
    
*   `createdby(...)`: Retrieves the Full Name and Email of the user who has created the assembly.
    

* * *

## Understanding the Output

When you run this query in your browser or a tool like Postman, you will receive a JSON response. This provides clear visibility into which account performed the deployment.

**Example Response:**

JSON

```json
{
  "@odata.context": "https://<your-org>.crm.dynamics.com/api/data/v9.2/$metadata#pluginassemblies(name,modifiedon,createdon,modifiedby(fullname,internalemailaddress),createdby(fullname,internalemailaddress))/$entity",
  "name": "XRM.ABC.CRM.Plugins.Core",
  "createdon": "2026-01-22T01:32:54Z",
  "pluginassemblyid": "5e96d04e-5435-48c0-9c01-637a210620cd",
  "modifiedon": "2026-04-22T14:22:15Z",
  "modifiedby": {
    "internalemailaddress": "AProcess@xyz.com",
    "fullname": "Auto Process"
  },
  "createdby": {
    "internalemailaddress": "AProcess@xyz.com",
    "fullname": "Auto Process"
  }
}
```

![](https://cdn.hashnode.com/uploads/covers/68b81cd5eff2027936ba607e/769cf2ea-db23-4637-a820-58488eb76cc6.png align="center")

* * *

## How to Find the Plugin GUID

If you don't have the GUID handy, you can find it using these common **Dynamics 365 CE / Power Platform** tools:

1.  **XrmToolBox**: Use the *Plugin Registration Tool* or *Metadata Browser*.
    
2.  **Web API**: Run a general query to list all assemblies: `GET https://<your-org.crm.dynamics.com>/api/data/v9.2/pluginassemblies?$select=name,pluginassemblyid`
    

![](https://cdn.hashnode.com/uploads/covers/68b81cd5eff2027936ba607e/95020b11-7306-4e21-bfb2-840228a2d3b5.png align="center")

## Why This Matters

*   **Accountability:** Easily identify which developer or service account (like "Auto Process") deployed the code.
    
*   **Troubleshooting:** Compare the `modifiedon` date with the time a bug was first reported.
    
*   **Environment Auditing:** Ensure that deployments across your **Dynamics 365 CE and Power Platform** instances follow your team's governance policies.
    

## Pro-Tip: The Browser Shortcut

You don’t need a specialized tool to run this. As long as you are logged into your **Dynamics 365 CE / Power Platform** environment, you can paste the API URL directly into a new browser tab. The browser uses your authenticated session to return the data immediately!