web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Writing back Sales Positions through ODataV4 in Business Central

(2) ShareShare
ReportReport
Posted on by 4
Hello everybody
 
We are currently facing a synchronization problem with our third-party app.
 
Situation / Process:
We are Reading all our Orders (SalesOrder) and the Positions (SalesLine) the orders contain. The Items will be scanned by the Warehouse (Barcodes are also saved in Business Central) and so they can pick by scan all our orders. In case the amount, the customer ordered is not available in the Warehouse we write the according amount (Qty. to Shop) back into the corresponding Positions in BusinessCentral. A special part in this process is also, that we split the Items into Temperature zones, because of the workflow in the warehouse. So we have 4 different temperature zones for each Order and they can be scanned by 4 different Workers at 4 different times.
When we started the App, we realised very quick, that BusinessCentral has issues, when we don't respect the Linenumbers while writing back. We fixed that by waiting until the last Zone of an order is scanned and then send all the positions back with the same position number like in the original Version.
 
Guess:
- The Lines in the Orders (We have item, description, empty and title lines) might cause the error
- Multiple orders can be combined to one in BC maybe it happens there

 
Error:
Since January we sometimes receive the error message below (it's a mix between german and english). I guess the core statement is this:"Application_DialogException","message":"You cannot insert further lines an this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line." Sidenote: Engomo is the name of our App. I am pretty sure, it has to do something with the order in which we write the positions back, but I can't fully reproduce the issue. We have a testing-environment but there the issue doesn't happen to 100%.. I rebuilt many of the orders, which cause this issue, but as I said, I can't force the error. 
 
13286 ms: Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 28 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines an this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: 7422a0d1-11c2-4ecf-aca5-0242469e45d."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines on this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re­
Calculate.Otherwise, you can insert after the last line. Correlationld: 6bf6d9b2-09e7-4c2a-b031-217c67f836d0."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error": 
{"code":"Application_DialogException", "message":"You cannot insert further lines on this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: 49c5b6fb­c5aa-49d9-ac00-22a9b72c1212."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error du ring communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines an this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: f868bb95-9670-427d-8c69-4e0acd0d444e."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error du ring communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines an this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: 8e06D4d4-dcbf-49a0-8cbd-368adb2a4705."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: d1 e3421e-2959-4597-9a3d-ed187f5e3a4e."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error du ring communication: 400 Bad Request {"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: 45c2c4c4-acfd-4665-a9fa-f6fd24305c2c."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"BadRequest", "message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: 33db33f8-23a6-4faf­bb3c-8f7316717336."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: 4d6d28a5-086f-4aee-9cd4-c635526053b4."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request 
{"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: d469ffb2-f974-4996-86c0-14faf5f72df4."}} . Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 2 konnte im Business Central nicht eindeutig identifiziert werden. Auftragsposition 28 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines an this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: 7422a0d1-11c2-4ecf-aca5-0242469e45d."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines on this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re­
Calculate.Otherwise, you can insert after the last line. Correlationld: 6bf6d9b2-09e7-4c2a-b031-217c67f836d0."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error": 
{"code":"Application_DialogException", "message":"You cannot insert further lines on this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: 49c5b6fb­c5aa-49d9-ac00-22a9b72c1212."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error du ring communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines an this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: f868bb95-9670-427d-8c69-4e0acd0d444e."}} Auftragsposition 28 konnte nicht synchronisiert werden. Error du ring communication: 400 Bad Request {"error":{"code":"Application_DialogException","message":"You cannot insert further lines an this position. lf the Order has no entries yet, you can reorganize the lines with Function, Re-Calculate.Otherwise, you can insert after the last line. Correlationld: 8e0604d4-dcbf-49a0-8cbd-368adb2a4705."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: d1 e3421e-2959-4597-9a3d-ed187f5e3a4e."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error du ring communication: 400 Bad Request {"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: 45c2c4c4-acfd-4665-a9fa-f6fd24305c2c."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"BadRequest", "message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: 33db33f8-23a6-4faf­bb3c-8f7316717336."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request {"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: 4d6d28a5-086f-4aee-9cd4-c635526053b4."}} Auftragsposition 29 konnte nicht synchronisiert werden. Error during communication: 400 Bad Request 
{"error":{"code":"BadRequest","message":"lnvalid JSON. An unexpected comma was found in scope 'Property'. A comma is only valid between properties of an object or between elements of an array. Correlationld: d469ffb2-f974-4996-86c0-14faf5f72df4."}} [line 39:13 - 39:34] ... throw error.toString{) [EngomoActionExecuteException, JavascriptException, PolyglotException] 

Thank you very much for your time and help!
I have the same question (0)
  • Suggested answer
    Assisted by AI
    OussamaSabbouh Profile Picture
    16,989 Super User 2026 Season 1 on at
    Hello,
    This looks more like an integration update/insert problem than a warehouse or item-line problem: the key message says BC is trying to insert a line at a position where no more lines can be inserted, while your log also says some positions “could not be uniquely identified” and later shows an invalid JSON comma error . I would not rely on the visual/position number from the external app; always read the BC sales order lines first and update the exact existing line using the BC line id / system identifier with PATCH, not by re-sending lines in a position order that may cause BC to insert/resequence lines. Also serialize the 4 temperature-zone updates per order, because parallel writes can change line state between read and update. The invalid JSON error is separate and must be fixed first, because BC will reject that request before any business logic is reached.
    Regards,
    Oussama Sabbouh

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,273 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,669 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,402

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans