Troubleshoot the API Pages
This article covers the messages that the API pages of the MCP Guard extension return in Microsoft Dynamics 365 Business Central when an AI assistant creates or changes production orders, calculates a plan, works with assembly orders, or changes project tasks and project planning lines, and when the BC MCP Pro connector reports usage. Each heading is the message as it is returned. The words in italics stand for a value that differs per case.
For the message that starts with Your MCP Guard rule gives you, see Troubleshoot Rules and Licences.
A production order cannot be created as finished.
Cause: The request creates a production order with the status finished. A finished order only comes from finishing a released order.
Solution: Create the order with another status: simulated, planned, firm planned or released.
A production order needs a source. Send the source type and the source number, for example an item number.
Cause: The request creates a production order without a source number.
Solution: Send sourceType and sourceNumber, then quantity and dueDate. See Production API.
Production order number is finished and cannot be deleted.
Cause: The request deletes a production order that is finished. A finished order is history and stays.
Solution: None through the API. A finished production order is not deleted.
Deleting a released production order is refused
Cause: Output, consumption or capacity is posted on the released order. Business Central refuses to delete it with its own message.
Solution: Reverse those postings and finish the order instead. See Production API.
The status and the number of a production order cannot be changed here. Use the release action to release the order.
Cause: The change contains another status or another number for an existing production order. The status and the number identify the order, so they cannot be changed in a change request.
Solution: Leave status and number out of the change. To release the order, use the release action. See Production API.
Production order number is finished and cannot be changed.
Cause: The request changes or refreshes a production order that is finished.
Solution: None through the API. A finished production order is not changed.
Production order number has status status and cannot be released.
Cause: The release action was called for an order that is not simulated, planned or firm planned. For example, the order is already released.
Solution: Read the order first and check its status. Only call release for a simulated, planned or firm planned order.
A starting date and an ending date are required.
Cause: The action calculatePlan or calculateCalendar was called without startingDate or without endingDate.
Solution: Send both startingDate and endingDate in the request body. See Planning and Assembly API.
The ending date date must not be before the starting date date.
Cause: The action calculatePlan or calculateCalendar was called with an ending date that is before the starting date.
Solution: Send an endingDate that is on or after the startingDate.
Only assembly orders can be changed here; document type number is not one.
Cause: The request addresses an assembly document that is not an order, for example an assembly quote or a blanket assembly order. The assembly API pages only work with assembly orders.
Solution: Use the API only for assembly orders. Change other assembly documents in Business Central.
The project number and the task number of a project task cannot be changed.
Cause: The change contains another projectNumber or taskNumber for an existing project task. These fields identify the task.
Solution: Leave projectNumber and taskNumber out of the change. To use another number, create a new task. See Projects API.
The project, the task and the line number of a project planning line cannot be changed.
Cause: The change contains another projectNumber, taskNumber or lineNumber for an existing project planning line. These fields identify the line.
Solution: Leave these three fields out of the change. To move a line to another task, create a new line there.
Usage can only be reported for today (date was given).
Cause: The connector reported usage for a day other than today. One day before or after today is accepted, for time zones.
Solution: Report the usage on the day of the calls. See Usage per User.
The number of calls must be between 1 and number.
Cause: The connector reported fewer than 1 call, or more than one report may hold.
Solution: Report at least 1 call, and split a larger number over several reports.
The duration cannot be negative.
Cause: The connector reported a negative durationMs.
Solution: Report a duration of 0 or more.
The assistant is required.
Cause: The connector reported usage without assistant.
Solution: Send the name of the AI assistant, such as Claude, ChatGPT or Copilot.
Only reading works, creating and changing do not
Cause: One of the conditions for writing is not met. Writing through the extension's API pages needs all of them at the same time.
Solution:
- Check that Unblock Edit Tools is turned on in the MCP configuration, and that the page has the operation turned on. See MCP Configurations.
- Check that the access level on the user's rule is Modify or higher. See Access Levels per Module.
- Check that the user has the permission set MCP GUARD - USER. On the MCP Guard User Settings page, the User Permission Set column shows Not found when no assigned set includes it. The sets MCP GUARD - PROD, MCP GUARD - ASSEMBLY and MCP GUARD - PROJECTS no longer exist and have no effect. See Permission Sets.
- Check that the user has Business Central's own permissions on the data.