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

Vendor IDs and Ampersands

(5) Share

Report

Posted on by JE-20081519-0

3,226

Hi:

We have migrated an end user from Dynamics GP to Business Central.

When clicking on any vendor in the "Vendors" list screen whose ID contains an ampersand, the issue shown below occurs.

So, I created a new vendor ID with an ampersand. Upon clicking on that ID, I received the same error.

Does Business Central not like Vendor IDs containing an ampersand? Is there a fix?

Thanks!

John

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

Ramesh Kumar 7,529 Super User 2025 Season 2 on at

Like (1)

Report

Hi John,

It's generally not a good idea—and I personally wouldn't recommend—using special characters in the Name or No. fields. This can cause issues such as exceptions or incorrect results when searching or applying filters.

https://experience.dynamics.com/ideas/idea/?ideaid=1ede4f65-3af0-e911-b862-0003ff68ac6b&utm

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
Suggested answer

Jainam M. Kothari 15,639 Super User 2025 Season 2 on at

Like (1)

Report

hello,

Business Central has known issues with handling special characters like ampersands in Vendor IDs, which can interfere with URL encoding and other processes. To address this, you can replace special characters with alternatives, ensure proper URL encoding, or write custom code to handle these characters. If these solutions don't work, contacting Microsoft support for further assistance is recommended.

Was this reply helpful? Yes No
Suggested answer

Teddy Herryanto (Th... 14,284 Super User 2025 Season 2 on at

Like (0)

Report

You shouldn't put any special characters under the Code field (such as Vendor No, Item No, Customer No field).

It will cause issue on filtering.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 20,601 Super User 2025 Season 2 on at

Like (1)

Report

special characters like ampersands (&) in primary keys or IDs (e.g., Vendor IDs) can cause unexpected behavior. The best fix is to avoid using special characters in primary keys.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,729 Super User 2025 Season 2 on at

Like (0)

Report

Generally, symbols related to filtering cannot be used in field values.

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-entering-criteria-in-filters?wt.mc_id=DX-MVP-5004336

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Suresh Kulla 50,245 Super User 2025 Season 2 on at

Like (1)

Report

You should not be using any special characters in the Vendor No. field, especially when that is the primary key value for the table, if you want to have those create a new text field and populate that.

Was this reply helpful? Yes No
Vahid Ghafarpour 12,166 Super User 2025 Season 2 on at

Like (1)

Report

If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

Thanks for being an active part of the Dynamics 365 Community!

Was this reply helpful? Yes No