Tips & Tricks | PluginTypeStatistic

-

Performance considerations 

When you add the business logic for your plug-in you need to be very aware of the impact they will have on overall performance. The business logic in plug-ins should take no more than 2 seconds to complete.

Time and resource constraints


There is a 2-minute time limit for message operations to complete. There are also limitations on the amount of CPU and memory resources that can be used by extensions. If the limits are exceeded an exception is thrown and the operation will be canceled.

If the time limit is exceeded, a TimeoutException will be thrown. If any custom extension exceeds threshold CPU, memory, or handle limits or is otherwise unresponsive, that process will be killed by the platform. At that point, any current extension in that process will fail with exceptions. However, the next time that the extension is executed it will run normally.

Optimize assembly development


The assembly should include multiple plug-in classes (or types) but can be no larger than 16 MB. It is recommended to consolidate plug-ins and workflow assemblies into a single assembly as long as the size remains below 16 MB. More information: Optimize assembly development

  Details


In order to plugin performance monitoring, we can query [PluginTypeStatistic] Entity

Entity Attributes that can support performance monitoring:

•	AverageExecuteTimeInMilliseconds
•	CrashContributionPercent
•	CrashCount
•	CrashPercent
•	CreatedBy
•	CreatedByName
•	CreatedOn
•	CreatedOnBehalfBy
•	CreatedOnBehalfByName
•	CreatedOnBehalfByYomiName
•	ExecuteCount
•	FailureCount
•	FailurePercent
•	PluginTypeId
•	PluginTypeIdName
•	PluginTypeStatisticId
•	TerminateCpuContributionPercent
•	TerminateHandlesContributionPercent
•	TerminateMemoryContributionPercent
•	TerminateOtherContributionPercent


Note: The Statistics updated periodically not after each transaction.

  Recommendations


Monitor PluginTypeStatistic Entity, Especially AverageExecuteTimeInMilliseconds to monitor Logic. In addition to ExecuteCount to monitor unused Plugins or CustomSteps. 


  References

Popular posts from this blog

Tips & Tricks | Solution Layers [Remove Active Customization]

-
Image
How to remove Unmanaged customizations away from a top of a managed solution Managed and unmanaged solutions exist at different levels within a Common Data Service environment. In Common Data Service, there are two distinct layer levels: Unmanaged layer . All imported unmanaged solutions and unmanaged customizations exist at this layer. The unmanaged layer is a single layer. Managed layers . All imported managed solutions and the system solution exist at this level. When multiple managed solutions are installed, the last one installed is above the managed solution installed previously. This means that the second solution installed can customize the one installed before it. When two managed solutions have conflicting definitions, the runtime behavior is either “Last one wins” or a merge logic is implemented. If you uninstall a managed solution, the managed solution below it takes effect. If you uninstall all managed solutions, the default behavior defined within the system solution is a
Read more

Tips & Tricks | Impersonation

-
Image
Impersonation is used to execute business logic (code) on behalf of another Dynamics 365 for Customer Engagement apps user to provide a desired feature or service using the appropriate role and object-based security of that impersonated user. To impersonate a user, set the CallerId property on an instance of OrganizationServiceProxy before calling the service’s Web methods. Workflow Impersonation Background Workflow In case Triggered workflow (create, update...) the workflow will run in the context of Workflow Owner/UserId In case On-Demand the workflow will run in the context of Initiating User . Real-time Workflow In case Triggered workflow (create, update...) the workflow will run according to selected option in execute as: - The owner of the workflow. (UserId) - The user who made changes to the record. (InitiatingUser) In case On-Demand the workflow will run in the context of Initiating User. Plugin/Custom Step Impersonation You can specify in your code which user context to ex
Read more

Tips & Tricks | Power Apps Community Plan [Development Environment]

-
Image
Power Apps Community Plan: a free development environment for individual use If you want to build skills and learn more about Power Apps, Power Automate, and the Common Data Service, the Power Apps Community Plan is the right plan for you. The Power Apps Community Plan gives you a free development environment for individual use. Will my Power Apps Community Plan subscription ever expire? You can use your Power Apps Community Plan subscription perpetually for free. If you are actively using an individual environment, then you won't lose access to any of the resources or functionality in that environment. You may, however, notice a delay when accessing your Common Data Service Database for the first time after a long period of inactivity. This delay does not impact the data or entities stored in the Common Data Service. To create a development environment to build skills and learn more about Power Platform it is recommended to create a Power Apps Community Plan over Power Apps Trial
Read more