Publishing failed: Ambiguous match found — Microsoft Dynamics Business Central

Naresh Vaneshwar
Nareshwar R.
Published in
1 min readDec 2, 2018

If you ever come across this issue when you create new fields in any tables on Business Central, you might be missing a config property on launch.json.

This bug is pretty ambiguous as it states in the title, can be only found on the event viewer. My event viewer log denotes as:

Message Failed request — Method:POST; Url:http://localhost:7149/BC130Ext/dev/apps?SchemaUpdateMode=synchronize; StatusCode:422; ReasonPhrase:Unprocessable Entity; Token: ProcessId: 15064

Originally my launch.json was:

After some digging, I understood, I have to specify the SchemaUpdateMode should be specified when launching.

When I updated the launch.json with,

“schemaUpdateMode”: “Synchronize”

My web client was kickstarted again.

--

--

Naresh Vaneshwar
Nareshwar R.

Technical findings and new developments on Business Central