Glossary
Idempotency
By Emil Björk · Microsoft business apps consultant, Gothenburg
The property of an operation where running it multiple times gives the same result as running it once — essential for safe retries in integrations.
Idempotency is the property of an operation where running it multiple times produces the same result as running it once. Essential for Dynamics 365 integrations because distributed systems retry — network timeouts, webhook redeliveries, Service Bus retries all produce duplicate message arrivals. A non-idempotent integration receiving the same event twice creates duplicate records, double-charges customers, sends repeated notifications. Patterns for idempotency: Upsert with alternate key (Dataverse's natural idempotency for record creation), check-before-create (query for existence first; acceptable at low volume), correlation IDs (track processed event IDs and skip duplicates), natural keys (business identifiers that detect duplicates inherently). Design every integration for idempotency; the cost is small, the protection is substantial.
Related terms
Mentioned in these guides
- AL runtime errors in Business Central
- Business Central API errors
- Event-driven architecture for Dynamics 365
- Eventually consistent integrations with Dynamics 365
- Idempotency in Dynamics 365 integrations
- Integrating Dataverse with Azure Cosmos DB
- Integrating Dynamics 365 with Stripe and PayPal
- Integration patterns for Dynamics 365 CRM
- Integration testing patterns for Dynamics 365
- Message replay and poison queue handling for D365
- Polling vs push patterns for Dynamics 365 integrations
- Attended vs unattended RPA in Power Automate Desktop
- Power Automate error handling patterns
- Error monitoring patterns for Power Automate
- Data integration for real-time marketing
- Retry policies with Azure services
- The outbox pattern with Service Bus
- Webhooks vs events in Dataverse