Session Abstract

How the Dataverse event execution pipeline actually works, developing testable plugins using base class patterns, debugging with tracing tools, handling long-running operations with Background Operations, and building Custom APIs for reusable business logic. Topics: * Event execution pipeline mechanics: Knowing stages and understanding when rollbacks occur and how Depth prevents infinite loops * What are plugins? Event-driven custom business logic triggered by Dataverse operations written in C# and registered to execute in response to events * Plugin base class patterns: encapsulating context extraction, service proxies with timing, tracing with timestamps, accessing everything efficiently * Synchronous vs asynchronous execution: Right now or soon and why care? * Debugging plugins with Plugin Trace Viewer: analyzing execution timing, tracing calls, troubleshooting issues, using CanaryTracer for event tracing across the pipeline * Custom APIs for reusable business logic: typed request/response parameters, binding types, MainOperation stage execution * Background Operations for long-running work: async Custom APIs with callback URLs, polling status monitor resources, retry with exponential backoff

Jonas Rapp

I'm lazy, and I'm proud of it. I build tools in my free time, so my workdays are more productive. I build tools for you as well. I work hard daily to not create a career.