Hi,   are there any plans for a new version of the discount endpoint with the pagination info like in all the other endpoints?    now it returns:   { "pageNumber": 0, "pageSize": 0, "totalCount": 0, "records": [ { "discountCode": "string", "series": "string", ...   and I have to handle this in our standard-accessor in another way as all the other endpoints which have this information in the meta-data (?)   Same problem in the SalesPerson endpoint. Florian ... View more

Hi   what happened with the swagger?     Florian ... View more

Hi,   since the updating of subaccount in cashtransaction does not work automatically from the inventory-number (see other thread) I have to read this information from the inventory-endpoint. But is the formatting of the subaccounts there a bit strange?   "salesSubaccount": { "id": "102000" } The customer has 2 segments and in the cash transaction I have to post also 2 segments.  The Subaccount in the UI is at least 102-000 and not 102000 And in the post for the cash-transaction I have to deliver: [{ "id": "1", "value":"102"},{"id":"2","value":"000"}]    ?   Florian ... View more

Hi,   just to check. Is this URL correct?   https://integration.visma.net/API/controller/api/v1/inventory?expandWarehouseDetail=true&availabilityLastModifiedDateTime=2021-05-14%2011%3A23%3A02.000&PageNumber=1&PageSize=500&attributes=%7B%22Inrugs%22%3A%221%22%7D   I don't get the availabilityLastModifiedDateTime work in this combination but I'm not 100% sure about the datetime-filterformat.    Here both the paging and the attribute-filter is working. But I always get all inventories which are matching the attribute and pagefilters, even if there are no warehouse changes.   Florian ... View more

Hi,   We are trying to post a budget line for our customer and we get an HTTP/1.1 500 Internal Server Error. I have verified the JSON in a JSON verifier - that is ok. I get the same error when I use Swaggar. The error is {   "message": "VismaId: 0251b020-2d21-4a09-b4bf-dd766657a4b3. Error creating budget. Index and length must refer to a location within the string.\r\nParameter name: length" }   It works in user interface.     Json: {"ledger": {"value": "2"},"financialYear": {"value": "2021"},"account": {"value": "1110"},"subaccount":[{"segmentId": 1,"segmentValue": "100"},{"segmentId": 2,"segmentValue": "00"},{"segmentId": 3,"segmentValue": "80901"},{"segmentId": 4,"segmentValue": "00"} ],"description": {"value": "Budsjett 2021"},"amount": {"value": -958333.26},"branchNumber": {"value": "1"},"periods":[{"operation": "Insert","periodId": {"value": "1"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "2"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "3"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "4"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "5"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "6"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "7"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "8"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "9"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "10"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "11"},"amount": {"value": -95833.33}},{"operation": "Insert","periodId": {"value": "12"},"amount": {"value": -95833.33}} ]}     Reponse:  HTTP/1.1 500 Internal Server Error Date: Fri, 30 Apr 2021 06:15:50 GMT Server: Apache/2.4.25 (Debian) Strict-Transport-Security: max-age=31536000; includeSubDomains Content-Type: application/json; charset=utf-8 ipp-request-id: 53f689c4-ff13-4b0a-a789-8ad58c2f85e8 Feature-Policy: geolocation 'none'; vr 'none'; payment 'none'; midi 'none'; microphone 'none'; fullscreen 'none'; encrypted-media 'none'; camera 'none'; autoplay 'none'; Cache-Control: no-cache,no-cache X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Acumatica-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_NO_REAL_0027 Strict-Transport-Security: max-age=31536000; includeSubDomains Expires: -1 X-XSS-Protection: 1;mode=block Set-Cookie: LegacyUI=0; path=/; secure; HttpOnly,UserBranch=13; path=/; secure; HttpOnly,Locale=TimeZone=GMTE0000U&Culture=en-GB; path=/; secure; HttpOnly,LicenseRoles=; expires=Thu, 29-Apr-2021 06:15:49 GMT; path=/; secure; HttpOnly,UserDisplayName=; expires=Thu, 29-Apr-2021 06:15:49 GMT; path=/; secure; HttpOnly,ADRUM_BT1=R:0|i:309592; expires=Fri, 30-Apr-2021 06:16:19 GMT; path=/; secure; HttpOnly,ADRUM_BTa=R:0|g:ec02fe20-992a-42f2-96d1-76ec88302a3e|n:visma_33a6117b-0ef0-4014-a5c1-a5af28a665ec; expires=Fri, 30-Apr-2021 06:16:19 GMT; path=/; secure; HttpOnly Set-Cookie: ADRUM_BT1=R:0|i:107258|e:898|d:1053; Expires=Fri, 30-Apr-2021 06:18:10 GMT; Path=/ Connection: close   Content: {"message":"VismaId: 337521c0-18b3-4573-acea-ead68b9dcc40. Error creating budget. Index and length must refer to a location within the string.\r\nParameter name: length"}   Regards,   Florian ... View more

Hei,   I have also another issue: In the UI its fully possible to set a blank Vat-Code on the Cashtransaction Lines. But thats not possible in the API. When sending "" i get the message that the Vat-Code is not found and when I send a null-value or don't send the field at all I get the standard vat-code from the account. Our workaround so far is to use a vat-code which don't have vat calculation, but that seems to be a bug in the API.   Florian     ... View more