Hi, Our customer  (ID: 4228921) receives the following error message in Medius AP A from the API when supplier invoices are to be sent over; Felmeddelande från ERP: 'requestUri: controller/api/v1/supplierinvoice / method: post / headers: Content: application/json Authorization: <******> ipp-application-type: Visma.net  Financials ipp-company-id: ****** / response content: {"message":"VismaId: 71451f44-0405-4e30-b8a5-ec08cdc2ef8c. Error creating supplierInvoice. Error: Inserting 'Supplier transactions' record raised at least one error. Please review the errors.\r\nAn error in processing of field Subaccount: Error: Projekt + AO/ÄTA of Subaccount do not exist."} / json response {"Version": We have tried creating the invoice manually in Visma, but get no error. We see no error in the subaccount or the segment value.  ... View more

Hi,  When creating sales order the ‘Invoice separately’ is unchecked on order type, Visma still create invoices separately. See ticket 00150654.  Visma creates invoices basted on Adress ID, in our case the address never chanced in Visma but it’s still creating invoices separately.  Visma is connected to Upsales. When we generate new invoices, we want the lates information from the customers, way use the Adress ID when the sales order was created? And witch settings can we use to makes sure the sale order will be invoices at once?   ... View more

Hej, Jag har fått frågan om att koppla 6 Upsales konton till samma visma.net bolag. Finns det någon begränsning från Vismas sida ? ... View more

POST/controller/api/v1/supplierInvoice   When creating supplierInvoice we get an error "the documen   t is out of balance".  See attachment.  We tested different scenarios,  and it seems that we get the error when we send three decimals. This is something we have been able to do prior. - has there been a change in the API?       ... View more

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-03-01T05:00:00&lastModifiedDateTimeCondition=%3E%3D"   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-03-01T05:00:00&lastModifiedDateTimeCondition=%3E%3D>, @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-2022/ba-p/479925   ... View more