Hi   We've noticed that createdDateTime filter does not seem to work on CustomerInvoice and CustomerCreditNote endpoints.   For example, when run a GET query with parameters lastModifiedDateTime: 2021-02-19 (tomorrow's date) lastModifiedDateTimeCondition: > we get no results as expected. https://integration.visma.net/API/controller/api/v1/customerinvoice?status=Balanced&lastModifiedDateTime=2021-02-19&lastModifiedDateTimeCondition=%3E&pageNumber=1&pageSize=1   But if we run the GET query with createdDateTime filter instead createdDateTime: 2021-02-19 (tomorrow's date) createdDateTimeCondition: > we get all the invoices like there is no filter at all   https://integration.visma.net/API/controller/api/v1/customerinvoice?status=Balanced&createdDateTime=2021-02-19&createdDateTimeCondition=%3E&pageNumber=1&pageSize=1       "metadata": { "totalCount": 999, "maxPageSize": 1000 }       The issue is reproducible in Swagger at least on the CustomerInvoice and CustomerCreditNote endpoints. We tested the same filter parameters on the Customer endpoint and there is worked as expected.       ... View more

Hi   We think it'd great if it was possible to find a Supplier Invoices by Supplier Number and SupplierReference.  Both fields are required in Visma.net and their combination is unique.    This would greatly improve that usability of this API endpoint, reduce the amount of calls one needs to make to extract this information and would allow for simpler integration architectures.   Thank you ... View more

Hi   The problem: Today it is possible to create Supplier Invoices with the connected Purchase Receipt lines via API. However, if the Purchase Receipt line was already attached to another invoice the API will return an error like  "The PO Receipt Line with order number 005092 and line number 136 doesn't exist in the look-up table".   This problem does not exist in the client because you add Purchase Receipt lines to the invoices via the look-up table view and only Purchase Receipt lines that are possible to use are shown there.   There is no way to make such look-up via API.   Proposal: Either to expose the look-up table in the API or perhaps to introduce a new field on the Purchase Receipt lines like "Non Invoice Quantity" or similar so it is possible to see that the Purchase Receipt line is already used anywhere else or not.   Like you have it in the look up table:   Thank you       ... View more

Hi   We are trying to create Customer Invoices by attaching Purchase Receipt lines to the invoices.  The problem is that when a Purchase Receipt line is already attached to another invoice we get errors like  "The PO Receipt Line with order number 005092 and line number 136 doesn't exist in the look-up table".   We you do the same in the client such Purchase Receipt lines just do not appear in the look-up table, and on those that do appear there you can see the original quantity as well as the quantity attached to other invoices.   We would like to do  a similar control via API but we are not sure is it is possible. The Purchase Receipt lines do not appear to have the Invoiced Quantity field and the look-up table seems not to be available in the API.   Do you maybe have any other suggestions on how we can se that it is not possible to attach the invoice receipt line to the customer invoice?   Thank you   ... View more

Hi   We periodically get IPPException as answers from API when making requests creating shipments and orders.  We do not see any pattern in why it happens and do not think it is data-related. Out of 20 requests 3-4 might fail which is a lot. We are using Azure functions to make the requests so most probably they are done simultaneously in parallel. Can this be the cause? Is there a limit of how many parallel calls is allowed to make? Is there anything else we can do to avoid it?   The exception message that we get: {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_c3ec5015-d452-47a1-b4ce-abd222b0fe24","ExceptionDetails":""} ... View more

Hi We have problem sending requests to VBS in VB 15. The requests come back with the error message before they reach VBS or Debug Host. Same programs work normally with earlier versions of Visma. We presume that something must be changed in the config but didn't manage to find what. Do you have any suggestions? The error message:   Severity: Error - Failed to communicate with Visma Business Services. Failed to communicate with server. The caller was not authenticated by the service. The request for security token could not be satisfied because authentication failed. at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target) at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState) The config file:   <system.serviceModel> <bindings> <basicHttpBinding> <binding name="BasicHttpBinding_IOrderService" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="65536" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true"> <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384"/> <security mode="None"> <transport clientCredentialType="None" proxyCredentialType="None" realm=""/> <message clientCredentialType="UserName" algorithmSuite="Default"/> </security> </binding> </basicHttpBinding> <wsHttpBinding> <binding name="vbsSecuredBinding" closeTimeout="23:59:59" openTimeout="23:59:59" receiveTimeout="23:59:59" sendTimeout="23:59:59" maxBufferPoolSize="524288" maxReceivedMessageSize="1073741824"> <readerQuotas maxDepth="1000000000" maxStringContentLength="1000000000" maxArrayLength="1000000000" maxBytesPerRead="1000000000" maxNameTableCharCount="1000000000"/> <security mode="Message"> <message clientCredentialType="UserName"/> </security> </binding> </wsHttpBinding> </bindings> <client> <endpoint address="http://localhost:2001/GenericService" behaviorConfiguration="nullX509Behavior" binding="wsHttpBinding" bindingConfiguration="vbsSecuredBinding" contract="Visma.BusinessServices.Generic.IGenericService"> <identity> <dns value="VBSTestCert"/> </identity> </endpoint> <endpoint address="http://localhost:2001/TestService" binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IOrderService" contract="OrderServiceRef.IOrderService" name="BasicHttpBinding_IOrderService"/> </client> <behaviors> <endpointBehaviors> <behavior name="nullX509Behavior"> <clientCredentials> <serviceCertificate> <authentication certificateValidationMode="Custom" customCertificateValidatorType="Visma.BusinessServices.Client.NullX509CertificateValidator, Visma.BusinessServices.Client"/> </serviceCertificate> </clientCredentials> <dataContractSerializer maxItemsInObjectGraph="1000000000"/> </behavior> </endpointBehaviors> </behaviors> </system.serviceModel>     ... View more