When trying to create a customer with a customer class where ‘Send invoices by Email’ is default true, we are experiencing problems with creating the customer. It’s a few customers that don’t have email, but we are unable to override the customer class default by setting ‘Send invoices by Email’ to false in the request for such cases.   We thought we might be able to handle it with ‘OverrideWithClassValues’ to false by default for our requests but doesn’t seem to resolve the issue.   As a secondary inquiry we are also having issues with setting the ‘CustomerLedgerSubaccount’ segments on creation.   Resonse: {"message":"VismaId: 6fed418a-a0b3-47fd-887c-3769c51c1376. Error inserting the customer. Error: Inserting 'Customer' record raised at least one error. Please review the errors.\r\nThe email address must be specified if 'Send invoices by email' is activated.\r\n"}   Request: {     "Number": {         "Value": "123456789"     },     "Name": {         "Value": "Test A/S"     },     "Status": {         "Value": "Active"     },     "OverrideWithClassValues": false,     "CustomerClassId": {         "Value": "7"     },     "CreditTermsId": {         "Value": "14"     },     "PrintInvoices": null,     "AcceptAutoInvoices": null,     "SendInvoicesByEmail": {         "Value": false     },     "PrintStatements": null,     "SendStatementsByEmail": null,     "PrintMultiCurrencyStatements": null,         "MainContact": {         "Value": {             "Name": null,             "Attention": {                 "Value": null             },             "Email": {                 "Value": null             },             "Web": null,             "Phone1": {                 "Value": "12345678"             },             "Phone2": {                 "Value": null             },             "Fax": null         }     },     "InvoiceContact": {         "Value": {             "Name": {                 "Value": "Test A/S"             },             "Attention": {                 "Value": null             },             "Email": {                 "Value": null             },             "Web": null,             "Phone1": {                 "Value": "12345678"             },             "Phone2": {                 "Value": null             },             "Fax": {                 "Value": null             }         }     },     "GlAccounts": {         "Value": {             "CustomerLedgerAccount": null,             "CustomerLedgerSubaccount": [                 {                     "SegmentId": 1,                     "SegmentValue": "99"                 },                                 {                     "SegmentId": 2,                     "SegmentValue": "000"                 },                 {                     "SegmentId": 3,                     "SegmentValue": "000"                 },                 {                     "SegmentId": 4,                     "SegmentValue": "00000000"                 },                 {                     "SegmentId": 5,                     "SegmentValue": "0000"                 }             ],             "SalesAccount": {                 "Value": "1010"             }         }     },     "AttributeLines": [         {             "AttributeId": {                 "Value": "AFDELING"             },             "AttributeValue": {                 "Value": "99"             }         }     ] } ... View more

When you do a GET call on InventoryReceipt you get the Lot/Serial Number and the expiration date, but when you do the same call as a POST you dont get the option to enter allocation values. This seems to be a mistake and are crucial for customers with lot and serial numbers.    ... View more

If found a missing functionality in the API. When you wanna create a customer, it might be that the new customer already is registered as a supplier. That makes the need to use the function 'Exstend to customer'. This is a cool functionality in Visma.net, but a functionality we are missing in the API.  ... View more

We can't get past that some data needs to be validated in Visma. For this proces we would like to make a small program that does this automaticly, but need some endpoints exposed in the API. I have listet the windows belove:   Validete Inventory ScreenId=IN505000 Validate Deferred Balance ScreenId=DR509900 Validate Customer Balances ScreenId=AR509900 Validate Vendor Payment Details ScreenId=AP50950S Validate Vendor Balances ScreenId=AP509900 Validate Account Balances ScreenId=CA503000 Validate Account History ScreenId=GL509900   It's basicly the same things we need exposed in all of them, which is 'Validate All', 'Validate', the "selector" so we can select which lines to run (or run all), and lastly (the reason Vismas own automation schedule doesn't work) we need the endpoint for the pop-up message that appears after you have pressed Validate All or Validate. We also need the endpoint for Warehouse, periodes and what else they are called in the different validation windows, exposed.          ... View more

Today we have the possibility to create a Purcase Receipt through the API, but meanwhile there is no possibility to create a Transfere Receipt. Still more of our costumers are using TR orders to transfer products between their warehouses and stores, and don't want to log in to visma in the stores and register the transfer receipt but want to be able to register a transfer receipt just like they are able to register a purchase receipt through the API. My request is therefor to create the necessary API possibility to handle these Transfer Receipts.    The transfer receipt is handled in the same window as purchase receipts PO302000, the difference is the document type. Where the purches reciept is handled as PoReceipt, the transfer receipt is TransferReceipt.         ... View more