The actual content from the APIs for at least the following tables seem to no longer fit the metadata-specifications:
SubaccountSegmentsJournalTransactionLines
Most other tables still work fine and the problem might be related to the dynamic nature of Visma.net’s metadata (see Dynamic data models: how to deal with continuously new tables and columns for background).
The problem seems to have started on July 6 and from then on occurred every day.
This seems to correspond to the introduction of Visma.net API version 9.00.00. The following Visma.net API metadata definitions have been used:
| Version | Patch | Start Date |
|---|---|---|
| 8.97.00 | 1001 | 2022-05-19 |
| 8.98.00 | 1007 | 2022-05-25 |
| 8.99.00 | 1003 | 2022-06-01 |
| 9.00.00 | 1003 | 2022-06-08 |
| 9.00.00 | 1003 | 2022-06-09 |
| 9.01.00 | 1009 | 2022-06-15 |
| 9.02.00 | 1004 | 2022-06-22 |
| 9.03.00 | 1007 | 2022-06-29 |
| 9.04.00 | 1001 | 2022-07-06 |
| 9.05.00 | 1003 | 2022-07-13 |
| 9.06.00 | 1005 | 2022-07-20 |
Please note that the actual download date of a new metadata-definition can lag behind an API actually using it due to caching.
It seems the problem started happening on 9.04.00.
A developer is assigned to further analyze the issue. This can take a few working days.