Answered

We couldn't convert to Number.

(1) Share

Report

Posted on by JD-13041615-0

Hello I am new to Copilot. What I am trying to do is update a field on a table. My company is using BC on-premises. I am a trying to update a Sales Order Line to the actual Item No that is being ordered. I am able to get the agent to find the correct information but I am having a problem getting the agent to write back to the database. I created a tool to do the update.

I am getting the following error: Error Message: The connector 'SQL Server' returned an HTTP error with code 400. Inner Error: We couldn't convert to Number. Error Code: ConnectorRequestFailure Conversation Id: a771f51b-fb5b-4a32-bc08-6d8a6dfa2d57 Time (UTC): 2026-04-17T14:19:24.087Z

The field I am trying to update is a string field. I am not sure why I am getting this error. Please help!

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Vish WR 3,748 on at

Like
a
(1)

Report
Copy link

Link copied!

@JD-13041615-0

This could be due to a datatype mismatch. Please check the datatime if required, convert first before writing it

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Suggested answer

Sajeda_Sultana 189 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @JD-13041615-0,

The error is most likely coming from the Row id / key, not from the No_ field being text.

Your table seems to use a composite key (including Line No_, which is numeric). If the Row id is built from column names or from text values that don’t match the numeric type, the SQL connector throws “We couldn't convert to Number.”

Try this:

Ensure Row id is built from the actual key values (Document No_, Line No_, etc.), not from a pattern like [Document No_],[Line No_],[No_].

Verify Line No_ is passed as a real number (no extra spaces or formatting).

If No_ is part of the primary key, use the other key fields to find the row and avoid updating the key column itself if possible.

If you can share the table’s primary key definition and a screenshot of how Row id is set, we can be more specific.

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Sajeda_Sultana

Was this reply helpful? Yes No
Nivedipa-MSFT Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!
,Hello JD-13041615-0
The "couldn't convert to Number" error is related to the row identifier, not your string field. The SQL connector expects a numeric value (such as Line No. or Document Type), but it's receiving a string value (like Document No.).

How to resolve:

Make sure Document Type and Line No. are provided as integers (for example, use 1 for Order instead of "Order") and cast them with int() if necessary.

Recommended approach: Use a stored procedure with clearly defined parameter types to avoid type-mapping issues with the connector.

Was this reply helpful? Yes No
Suggested answer

JD-13041615-0 12 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Nivedipa,

How do I use a stored procedure with Copilot and pass the values to the stored procedure?

Thank you,

Was this reply helpful? Yes No
Verified answer

Nivedipa-MSFT Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!
Hello JD-13041615-0,
Copilot Studio doesn't allow direct SQL queries. To work around this, you can use a Power Automate flow as an intermediary:

Create a flow with input parameters that align with your stored procedure's needs.

Select the SQL Server connector and use "Execute stored procedure (V2)", mapping the flow's inputs to your procedure's parameters.

Return the results from the flow to Copilot Studio using the flow's output.

Add the flow as a tool in your agent and set its inputs to "Set by agent" so values are automatically pulled from the conversation.

Always use parameterized stored procedures and avoid generating dynamic SQL from user input for security.

Ref Doc: Call an agent flow from an agent - Microsoft Copilot Studio | Microsoft Learn

If you found the information above helpful, I would appreciate it if you could share your feedback.
Your feedback is important to us. Please rate us:

🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 Poor

Was this reply helpful? Yes No