Troubleshoot your Business Central automated workflows
When you connect Business Central with Power Automate to create automated workflows, you might run into error messages. This article provides suggested solutions to recurring problems.
Flow doesn't run on all records created or changed
Problem
If an event creates or changes many records, the flow doesn't run on some or all records.
Possible cause
Currently, there's a limit on how many records a flow can process. If more than 1000 records are created or changed within 30 seconds, the flow isn't triggered.
Note
For developers, the flow triggering is done via webhook notifications, and this limitation is due to the way the Business Central connector handles collection notifications. Learn more at Working with Webhooks in Dynamics 365 Business Central in the Developer and Admin help.
"The response from the Business Central service is too large" error
Problem
When using an action that interacts with records (such as Create record (V3) and Get record (V3)), Power Automate might display an error similar to this one:
The response from the Business Central service is too large
Possible cause
Even though Business Central has no set limit on the size of records returned by APIs, the Dynamics 365 Business Central connector for Power Automate can handle only records up to 8 MB.
All the Business Central APIs provided by Microsoft return records under this limit, but APIs provided by partners might not. If you see an error "The response from the Business Central service is too large," reach out to the partner who created the API you're using.
"Entity set not found" error
Problem
When you create a new Power Automate flow using a Business Central approval trigger, such as When a purchase document approval is requested, you might get an error message similar to this one:
Entity set not found: \<name\>
The placeholder, \<name\>, is the service name of the missing web service, such as workflowWebhookSubscriptions or workflowPurchaseDocumentLines.
Possible cause
Using Power Automate for approvals requires certain page and codeunit objects to be published as web services. By default, most of the required objects are published as web services. But in some cases, your environment might have been customised so these objects are no longer published.
Fix
Go to the Web Services page and make sure the following objects are published as web services. There should be an entry in the list for each object, with the Published check box selected.
| Object Type | Object ID | Object Name | Service Name |
|---|---|---|---|
| Codeunit | 1544 | WorkflowWebhookSubscription | WorkflowActionResponse |
| Page | 6408 | workflowCustomers | workflowCustomers |
| Page | 6406 | workflowGenJournalBatches | workflowGenJournalBatches |
| Page | 6407 | workflowGenJournalLines | workflowGenJournalLines |
| Page | 6409 | workflowItems | workflowItems |
| Page | 6405 | Purchase Document Line Entity | workflowPurchaseDocumentLines |
| Page | 6404 | workflowPurchaseDocuments | workflowPurchaseDocuments |
| Page | 6403 | Sales Document Line Entity | workflowSalesDocumentLines |
| Page | 6402 | workflowSalesDocuments | workflowSalesDocuments |
| Page | 6410 | workflowVendors | workflowVendors |
| Page | 831 | workflowWebhookSubscriptions | workflowWebhookSubscriptions |
Note
The Service Name value must be exactly as shown in the table. Don't change or translate the service name.
Learn more about publishing web services at Publish a Web Service.
See also
Use Power Automate Flows in Business Central
Workflow
Set Up Automated Workflows
Switch on Instant Flows
Manage Power Automate Flows