Hi,
That generic error dialog with a Service Request Id and no exposed message is the Dataverse client's fallback when the Business Rule create call returns an unhandled server-side error. Microsoft Learn doesn't document this specific opaque error, but it does document the supported prerequisites for creating a Business Rule and the known causes that produce this exact "An error has occurred" dialog. Working through them in order usually clears it:
1. Confirm the table actually supports Business Rules in the modern designer
- Business Rules can only be created on tables you own (custom tables) or on the small set of system tables Microsoft explicitly enables (Account, Contact, etc.). Some system/virtual/elastic tables silently reject the create call and surface as the generic error.
- Reference: Create business rules and recommendations to apply logic.
2. Create the Business Rule from a solution, not from the table object directly
- Go to make.powerapps.com → Solutions → either open an existing unmanaged solution or create a new one with a custom publisher (not the default solution and not
CDS Default Publisher).
- Inside the solution: + New → Automation → Business rule, then pick the table.
- Creating from the table's Business Rules tab in the modern UI sometimes uses the default solution context and trips the generic error on environments where the default solution is in an inconsistent state. The in-solution path is the documented one and avoids it. Reference: Solution concepts in Power Platform ALM.
3. Try the classic designer once
If step 2 still throws the same error, open the same table in the classic experience (Advanced Settings → Customizations → Customize the System → your table → Business Rules → New). If the classic designer creates the rule successfully, the issue is specifically with the modern Business Rule designer in your environment — Microsoft Learn lists the classic designer as an officially supported alternative for now. Same reference: Create business rules and recommendations.
4. Developer environment specifics
- Developer environments have a smaller Dataverse capacity allocation and can hit transient limits that throw generic errors on process creation. Check Power Platform Admin Center → Resources → Capacity for your developer environment — if Dataverse capacity is exhausted, process create calls fail this way. Reference: Developer environments overview and Manage capacity storage.
- Also confirm you're connecting in the correct environment via the environment picker — the modern UI sometimes silently routes to the default environment, where personal admin rights don't apply.
5. Use the Service Request Id
The Service Request Id: cf36dab2-e8bf-4600-bbdd-98afc6232e6d on that dialog is the correlation ID Microsoft Support uses to look up the underlying exception in their telemetry. If steps 1–4 don't resolve it, open a support ticket from the Power Platform Admin Center (Help + Support → New support request) and quote that Service Request Id plus the UTC timestamp from the dialog — that's the only way to retrieve the actual server-side error behind the generic message. Reference: Get help and support.
Most often it's step 2 (creating from inside an unmanaged solution rather than the table object) — that's the documented path and clears the generic error on developer environments in the modern UI. If it doesn't, step 5 is the supported escalation route.
Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!
Raghav Mishra — LinkedIn | PowerAI Labs
