All imports from Visma.Net to Tracked stopped this morning.

[CharlotteJB1]

All imports from Visma.Net to Tracked stopped this morning. 

The endpoint /controller/api/v1/dimension/subaccount and parameter lastModifiedDateTime gives the correct answer if there is something changed since “lastModifiedDateTime” but if there is no change of data the endpoint answers with 404, see below.

 
url = "https://integration.visma.net/API/controller/api/v1/dimension/subaccount?lastModifiedDateTime=2022-0..."

HTTPClient::BadResponseError (unexpected response: #<HTTP::Message::Headers:0x0000563e7405bf00 @http_version="1.1", @body_size=0, @chunked=false, @request_method="GET", @request_uri=#<Addressable::URI:0x2b1f3a02a830 URI:https://integration.visma.net/API/controller/api/v1/dimension/subaccount?lastModifiedDateTime=2022-0...>, @request_query=nil, @request_absolute_uri=nil, @status_code=404, @reason_phrase="Not Found", @body_type=nil, @body_charset=nil, @body_date=nil, @body_encoding=#<Encoding:UTF-8>, @is_request=false, @header_item=[["Date", "Wed, 02 Mar 2022 06:18:25 GMT"], ["Server", "Nginx"], ["Strict-Transport-Security", "max-age=31536000; includeSubDomains"], ["Content-Type", "application/json; charset=utf-8"], ["ipp-request-id", "579fbcb9-664a-414a-90ff-bf1b03db9ddf"], ["X-Content-Type-Options", "application/json"], ["Pragma", "no-cache"], ["X-Handled-By", "Acumatica-PX.Export/AuthenticationManagerModule"], ["Referrer-Policy", "origin-when-cross-origin"], ["VnfInstanceId", "ERP_SE_REAL_0019"], ["Strict-Transport-Security", "max-age=31536000; includeSubDomains"], ["Cache-Control", "no-cache,no-cache"], ["Feature-Policy", "geolocation 'none'; vr 'none'; payment 'none'; midi 'none'; microphone 'none'; fullscreen 'none'; encrypted-media 'none'; camera 'none'; autoplay 'none';"], ["Expires", "-1"], ["X-XSS-Protection", "1;mode=block"], ["Set-Cookie", "UserDisplayName=; expires=Tue, 01-Mar-2022 06:18:25 GMT; path=/; secure; HttpOnly"], ["Transfer-Encoding", "chunked"]], @dumped=false>)

Previously, status = 200 was returned with empty data, as expected.

Nothing in the documentation https://integration.visma.net/API-index/ indicates otherwise.

The release note about performance improvement in this endpoint yesterday maybe cause this problem? 

https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Visma-Net-API-8-86-0-01-03...

[Magnus Johnsen]

Hi,

No update had been made in between those times.

[Magnus Johnsen]

Hi,

We're not able to reproduce this issue, could you please try the operation via for example Swagger?

When trying on our end we receive the subAccount object back, but with no segments that have been modified:

[CharlotteJB1]

Hi Magnus, 

Was there any changes or correction in the API before you had time to test?