Need help finding out how a dataverse table is being populated - it is using too much data capacity in the environment

[cpill1220]

Thank you for any guidance. I have a custom Dataverse table in our production environment that is using too much of our capacity. Our power app does not patch to it and no power bi reports use it. I'm the only developer in our environment and I want to delete the table, but as a novice, I'm a bit worried to remove the dependencies and delete the table. Is there a way to disable it for now? Or is there a way to identify what it is causing the table to populate? It actually seems associated with one of our SharePoint lists and creates a ridiculous number of records for the same action; seems somewhat like an audit table, but uses Dataverse capacity, not audit log capacity. 

[cchannon · Accepted solution]

Sure: look at your security roles, find the roles that have Create privs on the table and start taking the priv away, one role at a time. Eventually, something will break.

[Fubar · Accepted solution]

It could be many things, plugin, workflow, flow, Dataflow, something integrated.

Rather than going straight to Security Roles, look at what user(s) are in the Created By field of the records table. 

Check if it always the same user,

if they are created in batches (batches e.g. lots of records with their Created On in the same minute)

Turn on the plugin trace log, then remove security role privileges, if it is plugin or workflow you will get errors entry in the plugin trace log or process sessions tables - that will tell you what is doing it.  If its Flow you won't get an entry in those tables, but will then have to look at the Flow runs for failures.

(the extra issue if it is Flow outside of a solution or a Dataflow, is they can be hidden  from your user if you are not the owner of them)

[shashankbhide · Accepted solution]

check if there are async jobs running in the background, then remove security roles as someone suggested above, there's a chance that some application user with admin permissions is running a background power automate, check if there are azure components working in the background.