storage

New ‘Capacity’ analytics on PowerPlatform Admin Center

priyeshwagh777 CRM with .NET Web Applications, Power Platform , ,

We are quickly transitioning over from Organization Insights which came as a managed solution inside D365 to CDS For Apps Analytics on the PowerPlatform Admin Center. My past blog on the same (CDS For Apps Analytics instead of Organization Insights. Power Platform Admin Center).

And now, the same is revamped as Capacity in PowerPlatform Admin Center.

So, if you go to Storage in CDS For Apps analytics, you’ll see this –
movedOver

Capacity

You can access Capacity section directory from this URL – https://admin.powerplatform.microsoft.com/analytics/capacity

Or from the left hand menu as below –

menuItem

Now, as opposed to previously summarized % of the total capacity available, Microsoft is providing new entitlements for different types of storage consumption –

capacityView
Zoomed below

zoomedCapacity

As mentioned above, the bifurcation is as follows –

DATABASE: All other entities apart from the ones mentioned below.

FILE: Attachment, AnnotationBase tables

LOG: AuditBase, PluginTraceLogBase tables

Per Environment View

A Per Environment View looks like below and you can click on the Graph icon to go into the details
perEnvironmentView
At this point, information for the Graphical details are yet to be available. I’ll update post this is available for me too.

Availability

New Capacity model differs and will be available once the current term ends. More information from the links in the More Information section below
waitingForRenewal.png

More Information

You can refer more on Capacity here – https://docs.microsoft.com/en-us/power-platform/admin/capacity-storage

Microsoft’s FAQs – https://docs.microsoft.com/en-us/power-platform/admin/capacity-storage#faq

Hope this quick summary helps!

Advertisement

Delete Async Plugin Logs if plugin succeeds, save D365 storage space

priyeshwagh777 CRM with .NET Web Applications, Dynamics 365, dynamics 365 customization , , , ,

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.

sysjobs

Check your Async plugin step

  1. Now, you can preserve this storage space by choosing to Delete the Async plugin logs.
  2. In the screenshot below, you can see an option to ‘Delete AsyncOperation is StatusCode = Successful’
    deletelog

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.