About Magnus Johnsen

Magnus Johnsen · ‎11-05-2021

Hi, We are looking in to this and will get back to you. I can't see any issues with your JSON straight away.

Magnus Johnsen · ‎11-05-2021

Alright, could you please send us the timestamp of the call, the company id and your API Client ID? Thank you.

Magnus Johnsen · ‎10-05-2021

Hi, Could you please try this in the UI as well? It sounds like this is due to the time it takes for the ERP to do this, and would be as time consuming in the UI. Is this a normal size for you to add?

Magnus Johnsen · ‎06-05-2021

Indeed, good to hear that it works!

Magnus Johnsen · ‎06-05-2021

Hi, we are looking in to this. So far, in the UI the best way to find this would be to: 1. Check what warehouses the item is stocked in(only needed to check for several if the inventory item gets delivered to multiple locations, if it is always delivered to one, the default warehouse should be enough). 2. Go to Inventory Allocations details(IN402000) to see what purchaseOrders are not yet purchaseReciepts: 3. Check the expected delivery date on the order. As of right now, this screen does not seem to be exposed. We are checking with the ERP team what the best way to do this would be and will get back to you as soon as we have more information.

Magnus Johnsen · ‎06-05-2021

Hi Florian, The issue is that the periodId's under periods should be defined as YYYYMM. Here is the updated version that I used in my local company: { "ledger": { "value": "TEST" }, "financialYear": { "value": "2021" }, "account": { "value": "1910" }, "subaccount": [ { "segmentId": 1, "segmentValue": "01" }, { "segmentId": 2, "segmentValue": "001" }, { "segmentId": 3, "segmentValue": "1" } ], "description": { "value": "Budsjett 2021" }, "amount": { "value": -958333.26 }, "branchNumber": { "value": "TEST" }, "periods": [ { "operation": "Insert", "periodId": { "value": "202101" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202102" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202103" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202104" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202105" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202106" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202107" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202108" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202109" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202110" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202111" }, "amount": { "value": -95833.33 } }, { "operation": "Insert", "periodId": { "value": "202112" }, "amount": { "value": -95833.33 } } ] }

Magnus Johnsen · ‎06-05-2021

Hi Steinar, We'll have a look at it and get back to you. Thank you!

Magnus Johnsen · ‎30-04-2021

Hi, Could you please doublecheck your sub account segment key setup(ScreenId=CS202000&DimensionID=SUBACCOUNT): It sounds like there is a value sent that is longer or shorter than the length specified for the value.

Magnus Johnsen · ‎21-04-2021

Hi Steinar, We have relayed this information to the team investigating the issue. Thank you.

Magnus Johnsen · ‎20-04-2021

Hi, If it's the format you are asking for it's "yyyy-MM-ddTHH:mm:ss.FFF" and the Timezone is CET/ GMT + 1. It follows local time in Norway and accounts for summer/winter time.

Magnus Johnsen · ‎19-04-2021

Currently, the "Attributes" parameter is exposed on the following endpoints. Endpoint Customer CustomerContract Inventory Project Supplier Setting the attributes for other assets works in the same way as for e.g. customer. To set Attributes on Customers and Inventory Items you first need to Create the attributes in the UI. Assign the attributes to the Customer/Inventory etc. Classes respectively. Assign the class to the Customer/Inventory Item you want to use them on. Set the values of the attributes. 1. Creating the attributes: You can do this in the Attributes screen(ScreenId=CS205000): 2. Assigning the attributes to the class: Customer You can either reach the customer classes by Going to screen ScreenId=AR2010PL Clicking on the pen next to the class in the customer card: Here you then add attributes based on the attributes you have created in the attributes screen. Inventory You can either find the Item classes by: Going to the Item class screen(ScreenId=IN201000) Or clicking in the pen next to the Item class in the Inventory screen: Same as for customer, you can add attributes here based on the attributes you have created in the Attributes screen. 3/4. Setting the attributes and their values When this has been done, you can under the Attributes tab add the attributes from the classes the Customer/Inventory belongs to and set their values: Using the attribute parameter via the API To use these attributes, below is the syntax to use in your query: Filtering on several attributes. {{base}}/inventory?attributes={"AttributeID1":"ValueID1","AttributeID2":"ValueID2"} Filtering on date time {{base}}/inventory?attributes={"DATETIME":"2019-04-19"} Filtering on text. It will not match partial strings. only exact string. {{base}}/inventory?attributes={"TEXT":"long text to filter upon"} Filtering on True/False {{base}}/inventory?attributes={"ACTIVE":"1"} With special case for Multiple selection combo: {{base}}/inventory?attributes={"AttributeID":"ValueID1,ValueID2"} When encoding your query, the "equal sign" should not be encoded, below is an example for the customer endpoint and accepted forms of encoding it: Customer Endpoint: GET {baseUrl}customer?attributes={"DATETEST":"2019-01-01","TEST":"testvalue"} Encoded: (both encoding examples below are accepted) customer?attributes=%7B"DATETEST":"2019-01-01","TEST":"testvalue"%7D customer?attributes=%7B%22DATETEST%22%3A%222019-01-01%22%2C%22TEST%22%3A%22testvalue%22%7D Inventory Endpoint Inventory?attributes={"TEST":"testvalue"} Encoded: (both encoding examples below are accepted) inventory?attributes=%7B"TEST":"testvalue"%7D inventory?attributes=%7B%22TEST%22%3A%22testvalue%22%7D

Magnus Johnsen · ‎14-04-2021

Hi, We can confirm this is happening, as a workaround you can use the parameter FT=1 when updating the released supplierInvoice. This will allow the operation to be performed. We currently have a case in the backlog regarding updating fields for released supplierInvoices via the API, that are not allowed, as opposed to the UI where they can be altered. Thank you.

Magnus Johnsen · ‎14-04-2021

Hi, Ok, we are not able to see any issues with the JSON's you have sent us and are not able to reproduce this in our local enviroments. As far as we know, there should not be a difference in the validation made in the UI when using the action "addPurchaseOrderLine" and when doing it via the API. Has this happened to any other purchaseOrderLines? What type is the inventoryItem? Non-stock or stock? As we are not able to reproduce this at this moment with the information provided, could you please let us know if it happens again so that we can try to replicate the issue on our end? Thank you.

Magnus Johnsen · ‎12-04-2021

Hi, It does not look like there is an issue based on what you have sent. Could you please try to add this line manually in the UI to see if you can find it in the list or get any warnings/errors when adding it? If you are still having issues in the UI as well, could you please check what type of inventoryItem it is and describe the steps you have taken so far so we can try to reproduce this in our local enviroment? Also, if you get errors, please send us a screenshot from the UI. Thank you.

Magnus Johnsen · ‎12-04-2021

Hi, Could you please send us the JSON request you are sending now as well as the result of GET purchaseOrder/101830? Thank you.

Magnus Johnsen · ‎01-04-2021

Hi, We'll move this post to the Ideas section of the forum. Thank you for your suggestion.

Magnus Johnsen · ‎24-03-2021

This case is still in the backlog and we have asked the team for an update regarding the ETA. Update: The issue is in the current sprint, due to other priority cases we have not been able to start work on it yet. It will also be included in the upcomming sprint, and hopefully we will have a fix within the next 2 weeks.

Magnus Johnsen · ‎23-03-2021

Are you getting these issues on certain entryTypes or on all types? With Disembursement we were able to send a JSON without a VAT code: { "tranDate": { "value": "2021-03-23T10:29:13.896Z" }, "finanacialPeriod": { "value": "202103" }, "description": { "value": "empty vat" }, "cashAccount": { "value": "1900" }, "entryType": { "value": "10" }, "taxCalculationMode": { "value": "TaxSetting" }, "cashTransactionDetails": [ { "operation": "Insert", "quantity": { "value": 1 }, "uom": { "value": "STK" }, "price": { "value": 5 }, "amount": { "value": 5 }, "offsetAccount": { "value": "3000" }, "offsetSubaccount": [ { "segmentId": 1, "segmentValue": "01" }, { "segmentId": 2, "segmentValue": "001" }, { "segmentId": 3, "segmentValue": "0" } ], "project": { "value": "x" } } ], "cashTransactionTaxDetails": [] } UI:

Magnus Johnsen · ‎23-03-2021

Hi, We're looking in to this and will report it to the development team. Could you send us an example JSON of how you are expecting it to work? Thank you.

Magnus Johnsen · ‎22-03-2021

Hi, You can set up your currency rates in different ways in Visma.Net FInancials, please have a look at how to do it in the ERP here: Manage currency rates - overview This can be managed in ScreenId=CM301000: Via the API you call the endpoint currency to get the same data. PUT/POST toCurrency in the URL in the example USDEUR would be EUR: The body should contain USD's rate to the euro.

Magnus Johnsen · ‎19-03-2021

Hi, To be able to not use the automatic number series when posting via the API you need to include the field: "overrideNumberSeries": { "value": true }, This allow you to post the invoice with the number you specify in the referenceNumber field.

Magnus Johnsen · ‎19-03-2021

We have sent you an email, please have a look at it and let us know.

Magnus Johnsen · ‎15-03-2021

This is planned to be included in version 8.41 planned to be released on 16/03/2021: Visma.net Financials API updates for version 8.41.0 (March 2021)

Magnus Johnsen · ‎12-03-2021

Hi, The case is currently planned be worked on in the sprint for version 8.42. This is not a guarantee and can be changed. As soon as we have any information to share regarding this we will. Thank you.

Magnus Johnsen · ‎04-03-2021

Hi, Are these salesOrders with a high amount of lines? Also, what is your current timeout set to? Is there anything else in the error than your initial post? Could you please send us your API client ID, ip-addresses as well as a couple of timestamps to developersupport@visma.com? The time seems like it might coincide with when an Apache proxy was added on our side.

Magnus Johnsen · ‎04-03-2021

Hi, I've had a look at this, and to just start with lets review example 1. If the purchaseReceipt just has been created, normally if you have a look at it in the UI, it will not have any allocation lines. However when getting the receipt, the API will tell you that there is an allocation, this is an "internal" kind of preallocation of the required allocations. So in this example, where 1 line has 2 items that you want to split to two different locations you should update line 1(this is the only real line, the second line "dissapears" as you change the allocation for line 1). This is the JSON what you would use: { "lines": [{ "allocations": [{ "operation": "insert", "lineNbr": { "value": 2 }, "quantity": { "value": 1 }, "lotSerialNumber": { "value": "AllocationLine1" }, "location": { "value": 1 } }, { "operation": "insert", "lineNbr": { "value": 3 }, "quantity": { "value": 1 }, "lotSerialNumber": { "value": "AllocationLine2" }, "location": { "value": 2 } } ], "operation": "Update", "lineNbr": { "value": 1 } } ] } You would in the case of the lines being inserted not specify the line number, this is done automatically. It's only when changing the, updating or deleting you need to specify them. This is the result in the UI: When you have several lines, it helps knowing where the receiptlines are so that you can update them and then insert the lines you need for your allocation. Please try this, and if it still doesn't help, please let us know!

Magnus Johnsen · ‎03-03-2021

Hi, There is currently no support to search for multiple parameter values for "paymentType" in the same query.

Magnus Johnsen · ‎02-03-2021

Hi, Do you happen to have a time for when this started to happen and how often this happens? Are you seeing it happen on certain endpoints or generally?

Magnus Johnsen · ‎02-03-2021

Hi, We are checking this internally, in the case where the operations are failing, we can confirm that this seems to be happening, no content-length is provided, and transfer-encoding is provided. When the operation succeds the opposite is true.

Magnus Johnsen · ‎26-02-2021

Hi, We currently have a case in the backlog for this issue. Follow the "Release" news in the News section for updates regarding when this is implemented. This is being worked on.

Re: Problem adding PaymentLinesUpdateDto to Custom...

Svar: Adding large purchase order (900 rows) to re...

Re: Adding large purchase order (900 rows) to rece...

Re: Strange error posting Budget

Re: Best practice for finding next deliverydate fo...

Re: Strange error posting Budget

Re: County number problem Customer

Re: Strange error posting Budget

Re: Updated inventory lastmodifydate

Re: Interpreting the lastModifiedDateTime and crea...

Using the Attribute Parameter

Re: paySelected cannot be modified when SupplierIn...

Re: Issue: AddPurchaseOrderLines

Re: Issue: AddPurchaseOrderLines

Re: Issue: AddPurchaseOrderLines

Re: Default subaccounts on POST

Re: Location response header 404 error for credit ...

Re: Empty VATCode on CashtransactionLine

Re: Empty VATCode on CashtransactionLine

Re: Which exchange rate is leading

Re: manual invoice numbering through API and autom...

Re: API: Problems with updating allocations on pur...

Re: inventory returning blanks in json after one w...

Re: Location response header 404 error for credit ...

Svar: Periodically: Unable to connect to the remot...

Re: API: Problems with updating allocations on pur...

Re: Combining Payment types into one query possibl...

Re: Periodically: Unable to connect to the remote ...

Sv: no content returned anymore when POSTING to sa...

Re: Location response header 404 error for credit ...

Useful pages

About Visma

Contact us

Follow us