Przejdź do treści
Biblioteka skilli
Programowanie · Analiza

d365-limits-performance

/d365-limits-performance

Utrzymuje integracje i migracje Dataverse w limitach platformy, ponawia próby przy ograniczeniach 429 i unika kosztownych zapytań.

Repozytorium
d365-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
30.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
7
Przestarzałość

Brak sygnałów. Repozytorium zmienione 30.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Utrzymuje integracje i migracje Dataverse w limitach platformy, ponawia próby przy ograniczeniach 429 i unika kosztownych zapytań.

Oryginalny opis (EN)

Keep Dataverse / Dynamics 365 integrations, migrations and queries inside the platform limits - service protection API limits (429 Too Many Requests, Retry-After, 6,000 requests / 20 minutes execution / 52 concurrent per user per 5 minutes per web server), throttling-aware retry, parallelism versus batching, bulk messages, and query anti-patterns that cause timeouts (leading wildcards, too many columns, sorting by choice or joined columns, filtering on calculated columns). Use this skill whenever the user builds a data load, migration, nightly sync, ETL into or out of Dataverse, sees 429 / "Nu

Jak działa

  1. The limits (defaults, per user, per web server, 5-minute sliding window)
  2. How to move a lot of data
  3. Query anti-patterns (Dataverse names them in the error)
  4. Review checklist for a job or integration
  5. Output
  6. References in this skill
  7. Sources (Microsoft Learn)
Sekcje z nagłówków SKILL.md, w oryginale · 79 linii, 625 słów
Podgląd SKILL.md
---
name: d365-limits-performance
description: Keep Dataverse / Dynamics 365 integrations, migrations and queries inside the platform limits - service protection API limits (429 Too Many Requests, Retry-After, 6,000 requests / 20 minutes execution / 52 concurrent per user per 5 minutes per web server), throttling-aware retry, parallelism versus batching, bulk messages, and query anti-patterns that cause timeouts (leading wildcards, too many columns, sorting by choice or joined columns, filtering on calculated columns). Use this skill whenever the user builds a data load, migration, nightly sync, ETL into or out of Dataverse, sees 429 / "Number of concurrent requests exceeded" / "Combined execution time" / PerformanceValidationIssuesCauseTimeout / LeadingWildcardCauseTimeout errors, or asks why a Dataverse query or job is slow.
---

# Dataverse limits and performance

The platform tells you how fast you may go. The client that listens to `Retry-After` finishes
first. The client that hammers gets longer and longer penalties.

## The limits (defaults, per user, per web server, 5-minute sliding window)

| Measure | Default | Error |
|---|---|---|
| Requests | 6,000 | 429, Retry-After |
| Combined execution time | 20 minutes (1,200 s) | `-2147015903` |
| Concurrent requests | 52 or higher | `-2147015898`, returned immediately |

These numbers can change and vary by environment. Do not hard-code them as a rate limiter.
Plug-ins and workflows calling Dataverse internally are not subject to these limits.
Entitlement (licensing) limits are separate and batching does not avoid them.

## How to move a lot of data

1. **Let the server set the pace.** Start low, ramp up, and on 429 wait exactly `Retry-After`
   seconds before sending more from that user. Never retry immediately in a tight loop.
2. **Parallel single requests beat big batches.** Bound the degree of parallelism with the value
   of the `x-ms-dop-hint` response header, which is the environment's recommended parallelism.
   `ServiceClient` (and `CrmServiceClient`) already wait `Retry-After` and resend for you.
3. **Batches: start at ~10 operations,** not 1,000. Large batches hit the execution-time limit
   instead of the request limit.
4. **Prefer bulk messages** (`CreateMultiple`, `UpdateMultiple`, `UpsertMultiple`) on tables that
   support them. Data must be clean: one error fails the call.
5. **Synchronous plug-ins are your hidden cost.** During a load, each row pays for every sync step.
   Consider the bypass optional parameter (privileged users only) or disabling steps during the
   window, and say clearly what logic is skipped.
6. **Several application users multiply throughput only if the business accepts it.** Limits are
   per user. Do not create identities just to evade governance.

## Query anti-patterns (Dataverse names them in the error)

| Anti-pattern id | Fix |
|---|---|
| `PerformanceLeadingWildCard` | No `like '%x'`, `ends-with`, or values starting with `_`, `[`, `-%`, `'%`. Use Dataverse search or redesign the data. |
| `LargeAmountOfAttributes` | Select only needed columns. Never `all-attributes` or no `$select`. |
| `LargeAmountOfLogicalAttributes` | Fewer logical columns (values stored in other tables). |
| `PerformanceLargeColumnSearch` | Do not filter on large text (memo) columns. |
| `OrderOnEnumAttribute` | Do not sort by choice columns. |
| `OrderOnPropertiesFromJoinedTables` | Do not sort by columns from link-entity / `$expand`. |
| `FilteringOnCalculatedColumns` | Filter on stored columns, not calculated or formula columns. |

Also: filter on indexed columns (primary keys, lookups, alternate keys), limit join depth, and
page with cookies. Simple FetchXML paging stops at 50,000 rows.

## Review checklist for a job or integration

- [ ] 429 handling reads `Retry-After` (Web API header or `OrganizationServiceFault.ErrorDetails["Retry-After"]`)?
- [ ] Bounded parallelism, no unbounded `Task.WhenAll` over thousands of rows?
- [ ] Batch size small and measured, not 1,000 by default?
- [ ] Bulk messages used where the table supports them?
- [ ] Every query has `$select`/attributes, deterministic order, cookie paging?
- [ ] None of the seven anti-patterns above?
- [ ] Sync plug-ins on the target table counted in the load plan?

## Output

For a job design: throughput plan (parallelism, batch size, bulk or not), retry policy, the list of
sync logic that runs per row, and the query fixes. For an error: the limit hit, the cause, the fix.

## References in this skill

- `references/retry-patterns.md` - retry loops for .NET SDK, Web API and PowerShell.

## Sources (Microsoft Learn)

- Service protection API limits: https://learn.microsoft.com/power-apps/developer/data-platform/api-limits
- API limits overview (service protection vs entitlement): https://learn.microsoft.com/power-apps/maker/data-platform/api-limits-overview
- Send parallel requests: https://learn.microsoft.com/power-apps/developer/data-platform/send-parallel-requests
- Optimize performance for bulk operations: https://learn.microsoft.com/power-apps/developer/data-platform/optimize-performance-create-update
- Query anti-patterns: https://learn.microsoft.com/power-apps/developer/data-platform/query-antipatterns
- Query throttling: https://learn.microsoft.com/power-apps/developer/data-platform/query-throttling
- Bypass custom business logic: https://learn.microsoft.com/power-apps/developer/data-platform/bypass-custom-business-logic
Pliki w paczce (2)
  • SKILL.md 5 KB
  • references/retry-patterns.md 2 KB

Wersje

W bazie nie ma innych skilli o nazwie d365-limits-performance.

Migawka bazy z 13.11.2026 · wersja paczki fb5da7a1d732 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 96dataverse-python-performance-optimization
    Podpowiada, jak przyspieszyć kod Dataverse dla Pythona, ograniczając liczbę wywołań i obciążenie.
  • 91add-dataverse
    Dodaje tabele Dataverse (istniejące lub nowe) do aplikacji mobilnej Power Apps, rozszerza tabele o kolumny i wdraża zatwierdzony plan modelu danych.
  • 90d365-flow-reliability
    Projektuje niezawodne przepływy Power Automate dla Dataverse i Dynamics 365: filtrowanie wyzwalaczy, obsługę błędów, ponowienia i idempotentność.
  • 96dataverse-python-modules
    Opisuje moduły Dataverse dla Pythona i zasady ich użycia w kodzie.
  • 100microsoft-dynamics-webhooks
    Odbiera i uwierzytelnia webhooki Microsoft Dynamics 365 (Dataverse) z Plug-in Registration Tool, parsuje treść RemoteExecutionContext i obsługuje zdarzenia Create, Update i Delete.
  • 100dataverse-overview
    Wprowadza w pracę z Microsoft Dataverse: mapę skilli, twarde reguły, macierz narzędzi (MCP, Python SDK, CLI, PAC, Web API), ściągę metod SDK i bezpieczny cykl zmian.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.