Microsoft Dynamics 365 BC Troubleshooting

Symptom

When using a Cloud Connect Microsoft Dynamics 365 BC integration, you encounter the following error:

AutosplitKey function cannot calculate a new line number || Last known Path data %1

Here, %1 is replaced by the actual path where the error occurs.

Cause

This error typically happens when the details in the same array of creates/updates do not share the same header record key. Microsoft Dynamics 365 BC relies on consistent relationships between header key of the line records for autosplit key calculation. If the header key is inconsistent across related lines, the system cannot determine the next line number.

Examples

• Correct Structure

  • BOM with ID 12345
    BOM Line with BOMHeaderId = 12345
    BOM Line with BOMHeaderId = 12345

• Incorrect Structure

  "Item-PriceListLine":[
  {
  "_metadata": { "entity": "7001", "action": "create", "id": "BC - Price List Line", "noseries": [ { "2": "detail" } ] },
  "1": "BASI",
  "destination": [ { "ProductNo": "Component1" } ]
  },
  {
  "_metadata": { "entity": "7001", "action": "create", "id": "BC - Price List Line", "noseries": [ { "2": "detail" } ] },
  "1": "DIA",
  "destination": [ { "ProductNo": "Component2" } ]
  }
  ]

  Lines reference different header key value within the same array, breaking the relationship. Here, the process document had a custom relation between entity 27 and 7001. The correct structure should be:

  27 → 7000 (Sales Price List Header) → 7001 (Sales Price List Line)

Solution

Ensure that:

• All entities in the same array of creates/updates reference the same header record key.

• If you have custom relations, verify that the process document reflects the correct relationship structure before saving, and that the entities follow the correct relation with the proper header record key.