Problem with Visma.net API - missing external codes in extract

[SteffenW]

Hi,

after lunch today we dont get the information for external codes via our API from visma.net. No error message, the fields are just empty. Doublechecked our visma.net and the values are still there but they dont get extracted.

[SteffenW]

It looks like that you now have both the old and the new solution in place:

What is the plan moving forward? Will you keep the old, the new or both solutions?

[Magnus Johnsen]

Hi,

The old fields will be deprecated, we recommend updating your solution to use the new fields, but for now it will still work with the old fields.

[SteffenW]

Ok, thank you! good to know. It would be appreciated if you could give us a timeline or a phase out date for the old solution so that we will not get suprised again. Thank you in advance!

[Magnus Johnsen · Accepted solution]

Hi,

The due date for the removal of the old fields can be found in the release notes:

[Release Notes] - Visma.Net API 9.70.0 - 14.11.2023

[SteffenW]

any update on this? It is quite frustrating for us if you change the code affecting the API without any notice

[Magnus Johnsen]

HI,

There are improvements in the GET Account API endpoints. Both, the 'Get a specific account' and the 'Get a range of accounts' endpoint will include values for:
- Control account module
- Allow manual entry
- Public code
- External code 1
- External code 2
- Analysis code
in their responses. In addition, it is possible to set filters on
- Public code
- External code 1
- External code 2
- Analysis code
in the 'Get a range of accounts' endpoint.

These fields now look like this:

    "externalCode1Info": {
      "number": "string",
      "description": "string"
    },
    "externalCode2Info": {
      "number": "string",
      "description": "string"
    }

[SteffenW]

Thank you for your answer! How do we need to adapt our SQL coding to retrieve the string from the externalCode1Info - number? in our example below we tried different alternatives but did not succeed

[Magnus Johnsen]

Hi,

The development team is currently looking into if this needs to be rolled back or fixed in another way. 

[SteffenW]

thanks for the update

[SteffenW]

one example of what we have tried but it does not work 

[SteffenW]

Our code that worked before lunch and for the last months looks like this: 

[SteffenW]

Edit:
Post has been removed due to including an API token in the print screen.

Please share the image again after obscuring the authentication part.

[Magnus Johnsen]

Hi,

What values from what endpoints are you having issues getting?