Hi, please send your payloads used in the mentioned operations and share the followed API transaction flow step by step via developersupport@visma.com  ... View more

This integration is running with the old authentication. The company ID is 4300704.   But we have got the same error on another integration, running the new authentication. Sorry to say, I have no any saved data to share with you. /Stefan ... View more

Thanks for you kind help Yildirim   The Parters service could not answer but referred to you. I also know that it is possible to use Visma.Net to synchronise employees and code sections. But this customer is using Expense with no connection to any ERP system. That's why I wrote that it is standalone. But then I guess there is no way besides those that Visma uses themselves to synchronise their business systems with Expense. You can close the case. ... View more

Hi Stefan, Ok, thank you! ... View more

Hi, These fields are currently not available in any of the salesOrder endpoints. If this is functionality you need, please create a post in the "Ideas" part of the forum. Thank you.  ... View more

Apologies for the test. My privileges on the forums seem to be flip flopping, leading to disappearing posts/replies. I have created a separate topic on the problems with Swagger, since this one has been marked already as solved. ... View more

Hi Stefan,    this case has already been conveyed to the development team and currently in the process of prioritization so that we'll be able to share more information once it's finalized.  ... View more

This does not look like a companyID, could you please doublecheck? ... View more

Hi, You don't need to delete the whole discount, only the line that you wanted to update originally. Do this with the line operator "delete" via a put call. The numbering when inserting is omitted, as with other endpoints as well, it is only taken into account when you are using "Update" or "Delete" operators.  The series value gets set according to your settings in the discount code window, if it's set to autonumbering and the conditions of the discount is different from the other series it will be autogenerated: ... View more

Hi Allan   The only solution we found was to wait for the shipping, there you can find both the IN och UT warehouses.   /Stefan   ... View more

In shipment, action menu, and Update inventory.   ... View more

We can confirm even sending the minimum fields result in the same error: {     "landedCost": [         {             "operation": "Insert",             "landedCostCode": {                 "value": "TESTCODE"             },             "supplierID": {                 "value": "50000"             },             "purchaseInvoiceNbr": {                 "value": "SupRef"             },             "locationId": {                 "value": "Main"             },             "description": {                 "value": "Test"             }         }     ] }   It has been reported to the development team. Thank you.  ... View more

1) Expose "Attributes" Tab via Employee Endpoint (Read&Write) 2)Expose "Attributes" as a filtering parameter via GET Employee Endpoint  e.g. Inventory & Supplier & Customer Endpoints.  Syntax: {{base}}/inventory?attributes={"MULTIPLE":"Summer,Winter","ACTIVE":"1"} - Filtering on several attributes. {{base}}/inventory?attributes={"DATETIME":"2019-04-19"} - Filtering on date time {{base}}/inventory?attributes={"TEXT":"long text to filter upon"} - Filtering on text. It will not match partial strings. only exact string. {{base}}/inventory?attributes={"ACTIVE":"1"} - Filtering on True/False In general: {{base}}/inventory?attributes={"AttributeID":"ValueID","AttributeID":"ValueID"} With special case for Multiple selection combo: {{base}}/inventory?attributes={"AttributeID":"ValueID1,ValueID2"} In case of multiple value usage "OR" Logical Parameter is not supported, The operands works based on AND logical operator. Meaning, if there are 3 multiple attribute value holder items exist such as   # ITEM ID Attribute Value 1 Item 1 MULTIPLE "a1,b1,c1" 2 Item 2 MULTIPLE "a1,b1" 3 Item 3 MULTIPLE "a1"   Filter: attributes={"MULTIPLE":"a1,b1,c1"}   Returns only #1st Record MULTIPLE "a1,b1,c1"   ... View more

Thanks, Stefan ! After checking our backlog, we've seen that there is a case for extending the GET (Read) EmployeeDto with Employee - Attributes tab.   Regarding exposing Attribute values as a filtering parameter, this will also be conveyed to the development team. However, implementation process will be assessed based on couple of factors therefore we're unable to share any specific date about when this can be included at the moment.  ... View more