Skip to main content
Question

JSON parsing fails after upgrading to REST API provider version 12.1.0.0

  • May 21, 2026
  • 3 replies
  • 31 views

After upgrading to Ingest 7313.1 I updated my REST API provider version to 12.1.0.0.

 

Now some of my REST endpoints have started failing.

Running “Import metadata” works fine, but when it tries to extract values from the JSON, it fails with errors like: 

Failed to execute callback for endpoint 'Get Charge Points':
Column 'data_id' does not belong to table charge-points.

System.ArgumentException: Column 'data_id' does not belong to table charge-points.

 

But it should be able to parse it.

The structure of the JSON is like this (just showing top of file):

{
  "data": [
    {
      "id": 1096237,
      "teamId": 449574,

 

Any tips?

 

3 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • June 2, 2026

Hi ​@JanTerje

How is the endpoint set up in the provider?

Is charge-points the name of the Table Flattening?


  • Author
  • Starter
  • June 3, 2026

Hi ​@JanTerje

How is the endpoint set up in the provider?

Is charge-points the name of the Table Flattening?

Hi, Thomas.

I’m actually getting this behavior in more than one endpoint, also on endpoints that don’t use table flattening.

My workaround has been to use the CData REST connector for the REST endpoints where we experience this issue, so it’s not a critical issue for now.

When I have some time, I can recreate a simple data source connection that reproduces the error.


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • June 11, 2026

Hi Jan

I assume it is due to the data_id merged field that it somehow can’t locate. Actually using Table flattening may actually resolve it.