Small and medium business | Business Central, N...

Sales Order Agent Copilot - Get Permissions error when confirming Sales order

(3) Share

Report

Posted on by KC Lai

341

Hi,

I have activated sales order agent copilot for Business Central online. I was able complete the steps of creating sales quote. As I clicked Confirm to create sales order I got the following error could not proceed further.

A permission error was encountered while attempting to convert the sales quote 1293 to a sales order. The error message is: 'Sorry, the current permissions prevented the action. (TableData 28003 Address ID Delete: Base Application)'. Please assist in resolving this issue.

I am having the following Permssion Sets

- SOA - EDIT

- SOA - READ

- Agent Admi

- Super

- created a new Permission Set to give full permissions to TableData 280003

Does anyone face similar issue?

Screenshot 2025-05-17 064229-Sales Order Agent.png

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Gerardo Rentería Ga... 26,509 Most Valuable Professional on at

Like (4)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

Permissions allowing user to create Sales Quotes, but prevent Sales Order creation

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 22,365 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hope this helps as well:https://www.dynamicsuser.net/t/sorry-the-current-permissions-prevented-the-action-tabledata-21-cust-ledger-entry-insert-base-application/87255

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,175 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Maybe this will help you:

You're encountering a permissions issue when confirming a sales order in Business Central using the Sales Order Agent Copilot. Try these steps:

Verify TableData Permissions Ensure your new permission set includes **Delete** permissions for TableData 280003. You can check missing privileges in Dynamics 365 (https://learn.microsoft.com/en-us/troubleshoot/sales-copilot/crm-permissions-and-configurations/missing-privileges-sign-in).

Was this reply helpful? Yes No
Suggested answer

Ramesh Kumar 7,555 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Even if you're assigned SUPER, the Copilot/agent itself runs under the Copilot runtime context, and not necessarily as your user. So you’ll need to explicitly add full access for that table.

If not you need to raise ticket with Partner/Microsoft

Thanks

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Was this reply helpful? Yes No
KC Lai 341 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I have set TableData 280003 RIMD = Yes . But still no luck.

I was able to convert Sales Quote to Sales Order manually.

Should I apply this permissions to my user ID?

Regards

KC

Was this reply helpful? Yes No
Suggested answer

Sagar Dangar, MCP 813 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi,

Yes. Please assign permissionset "FIXSOAGENT" to your user and check.

Was this reply helpful? Yes No
JL-03051535-0 4 on at

Like (0)

Report
Copy link

Link copied!

Ramesh's note is the key one to internalize. The Sales Order Agent runs under its own dedicated agent account, not your interactive user, so SUPER on your account will not propagate. Two specific things to check before chasing more table-level permissions. First, on the Agents page, open the Sales Order Agent record and confirm the agent's permission set actually includes Delete on the underlying tables touched by the quote-to-order conversion (TableData 280003 Address ID is the one you are seeing, but the same chain often pulls Customer, Customer Address, Sales Header, Sales Line). Microsoft's default SOA AGENT - EDIT is intentionally narrow, and Sagar's FIXSOAGENT extension is the practical patch most installs land on. Second, the Agent record needs to be company-bound; if it is still in Preview (per the Apr Payables Agent thread on this same forum), BC will block company-level access regardless of SUPER. Worth naming for anyone landing on this later: agent identity is the new operational gotcha across the BC + Copilot Studio surface area. Same pattern hits the Payables Agent. We hit a similar architecture choice when wiring eyko's MCP integrations into JD Edwards and other customer systems: the tool layer holds its own identity with scoped, audit-logged permissions, separate from the calling user, so a controller can answer 'who actually ran this' without unpacking a trace. The 'agent identity equals user identity' assumption is the thing that breaks. Disclosure: I work at eyko.

Was this reply helpful? Yes No