Let’s see how we can efficiently manage D365 storage without bloating the storage with data that you might not need.
In my opinion, we don’t really need to know that the background process was successful or not, we typically care for what failed.
So, from an Asynchronous plugin standpoint, the logs in D365 is registered in the System Jobs and they create a ton of System Events if you are Importing data in D365 and your Async process is on the create of such records.
Check your Async plugin step
- Now, you can preserve this storage space by choosing to Delete the Async plugin logs.
- In the screenshot below, you can see an option to ‘Delete AsyncOperation is StatusCode = Successful’
In this case, the System Jobs for the will not be created, thus, saving you valuable storage space if your plugin is run frequently.
Hope this helps.