> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/changelog/april-2025/2025-04-24.md).

# 2025-04-24

## Systems

### :screwdriver: New

<table><thead><tr><th width="339">System</th><th>Functionality</th></tr></thead><tbody><tr><td>Visma eAccounting</td><td><ul><li><p>GET /financialdimensions</p><ul><li>Added support for retrieving financial dimensions from Visma eAccounting.</li></ul></li></ul></td></tr></tbody></table>

### :wrench: Improved

<table><thead><tr><th width="339">System</th><th>Functionality</th></tr></thead><tbody><tr><td>Visma eAccounting</td><td><ul><li><p>map customer label</p><ul><li>Mapped <code>CustomerLabel</code> from Visma eAccounting to <code>PartyIdentification</code>.</li></ul></li><li><p>improved validation for attachments</p><ul><li>Improved validation response handling for <code>POST /salesinvoices/:id/attachments</code>.</li></ul></li><li><p>token refresh fix</p><ul><li>Fixed 500 error caused by token refresh issues during GET /financialdimensions.</li></ul></li></ul></td></tr><tr><td>Visma Netvisor</td><td><ul><li><p>map customer type</p><ul><li>Mapped customer type to <code>AccountingCustomerParty</code></li></ul></li></ul></td></tr><tr><td>Fortnox</td><td><ul><li><p>Fortnox: token refresh fix for GET /financialdimensions</p><ul><li>Resolved a bug where token refresh failures caused 500 errors when accessing financial dimensions.</li></ul></li></ul></td></tr></tbody></table>

## Platform

### General

<table><thead><tr><th width="341.3333740234375">System</th><th>Functionality</th></tr></thead><tbody><tr><td>General platform improvements</td><td><ul><li>Security updates</li><li><p>Validation error handling fix</p><ul><li>Fixed issue where duplicate keys in <code>validationErrors</code> could throw an exception.</li></ul></li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zwapgrid.com/changelog/april-2025/2025-04-24.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.