Hi all,    Right now the ETag header is only returned for GET requests, but (the latest) is required for PATCH and POST. When I need to update an order that leads to the following flow:  GET /api/v3/SalesOrders/${OrderType}/${OrderId}  // get whole order just for etag header  PATCH /api/v3/SalesOrders/${OrderType}/${OrderId}  // use etag to update Order GET /api/v3/SalesOrders/${OrderType}/${OrderId}  // get etag header again DELETE /api/v3/SalesOrders/${OrderType}/${OrderId} /lines?lineIds=1,2,3,4,5  // use etag to delete lines  GET /api/v3/SalesOrders/${OrderType}/${OrderId}  // get etag header again POST /api/v3/SalesOrders/${OrderType}/${OrderId} /lines  // use etag to insert lines    Doing a full get is a bit wasteful and introduces added calls/latency. Could you guys include the ETag header in the reply for POST, PATCH and DELETE? Ideally also include a HEAD to get it without getting the full Order.    That could shorten the flow above to: HEAD /api/v3/SalesOrders/${OrderType}/${OrderId}  // get etag header, no data PATCH /api/v3/SalesOrders/${OrderType}/${OrderId}  // use etag from above and capture eTAG from reply DELETE /api/v3/SalesOrders/${OrderType}/${OrderId} /lines?lineIds=1,2,3,4,5  // use from above and  capture eTAG from reply POST /api/v3/SalesOrders/${OrderType}/${OrderId} /lines // use etag from above    That 6 calls would be 4 and smaller ones too, saving round trips and bandwith.        ... View more

Hi,    I'm trying to write (POST, PUT) projects with their attributes, but I don't see attributes in the ProjectUpdateDto.. Just wanted to double check if missed something and writing attributes to projects might be possible after all?    Regards Gert-Jan ... View more

Hi,    I'm moving KitSpecifications from and older system to Visma.Net through the API.    I was able to add a lot of them, however when reviewing the result I noticed something wrong so I deleted them all through the normal web client (as the is no KitSpecifications  delete).    If I GET /v1/KitSpecifications it returns 0 records    Now I want to post them again but that gives me this error:  {"message":"VismaId: 6d80fb70-42e7-49b9-b0b1-4130f903294e. Error creating INKitSpecHdr. Object reference not set to an instance of an object."}   I also tried PUT KitSpecifications /id/revision but indeed those are not found.    Could you help me out here?      ... View more

Hi,   The authentication against https://connect.visma.com with Authorization Code flow returns an error: Error redeeming code: invalid_tenant / no description   It worked fine just an hour ago, don;t think we changed anything.    Below is the return URI with the code, it seems to happen in exchanging the code for the token.  Not sure what the tenant would be? Tried another Visma organization and got the same error.      http://localhost:8888/callback/?code=33xxxD6&scope=email%20profile%20openid%20offline_access&state=awvXn0D8gIy6_xfjoCCh0Q&session_state=DsEL0qVdhqD9H3_AW94rCWdCSoHDfC3HSdgZm81g-84.F095CAC6F1B4C97200856615C1949C28&iss=https%3A%2F%2Fconnect.visma.com   ... View more

Hi,    When I POST a new journal to JournalTransactionV2 the api replies with "" and I can see the newly created journal in screen GL3010PL but it's not yet posted.    There is a second method /action/release but that requires a JournalNumber. How do I get the the Number of the newly created journal from the api, so I can release it? Normally you would expect the api to return the newly created journal or at least the autogenerated Number..      ... View more

I have a user where the login process does not complete.    I send them to the OAuth start uri, but that process does not complete. When he's logged in, it shows the 'blurry background' with no content on it and stalls there, no pending redirects or anything.    If he's logged out he does get the login prompt, but after that it again stops at the same point.   Not sure what could cause this, we'll monitor if it resolves itself just wanted to report it.    GJ ... View more

Hi,    I get a 400 with message "error": "invalid_grant" when trying to use the refresh token I got with the previous login.    Here is my request : POST https://connect.visma.com/connect/token HTTP/1.1 Accept: application/json Content-Type: application/x-www-form-urlencoded Host: connect.visma.com Content-Length: 127 Expect: 100-continue   grant_type=refresh_token&refresh_token=6474**F1A6&client_id=isv_xlconnect   That form content seem to align with the docs except for the secret, but this app is PKCE..  Any idea what might be causing this? Can you see more details in the log?    Regards Gert-Jan   ... View more