No worries, it is a lot to read at first. 🙂 ... Visa mer

Thank you for checking. I'll create a new thread with a different issue when adding lines "manually".  ... Visa mer

Thank you, regarding the confirmation it's also confirmed it happened in the GUI and it will be reported accordingly.   ... Visa mer

I think it is time to discuss when to deploy, and even more, when not to deploy. So, to deploy or not to deploy, that is the question. The answer is dependent on a risk evaluation. And the risk evaluation is dependent on probalility and impact. If expected impact is high; even low probability should suggest no deployment.   To understand impact, Visma need to understand the pratical consequenses at the ISV's and at the end customers. Visma need to understand our pain.   In our house, we have a very tough system administrator. He rules. And he often say NO. Honestly, some times it is frustrating for some of us. But all the time it is safe, for all of us. We do not deploy on Fridays - we dont want to bring potential problems into the weekend, neither for us nor for our customers. We do not deploy on Mondays - some times things happens during weekends, and it need to be handled, we need to deal with this first before we deploy. Clean the desk and be prepared. We do deploy on Tuesdays, Wednesdays and Thursdays.   If to discuss any exceptions from this, expected impact need to be low.   We stop deploying a few days before holidays and bigger events. Because we need to be at work and ready for action if not everything after deployment went as expected. And we do not want to introduce new risks just before hight traffic events. These events are already busy enough.   Of course this careful approach to deployment can be frustrating for both impatient customers and marketing departments. But in the long run it gives a more stable environment. It pays off.   The need of being prepared for handling situations after deployment is also valid in a world with continous delivery. Also the need of someone being at work, someone to handle situations and communication.   Like Forrest Gump says; **bleep** happens. And when it happens "someone" need to be "the chosen" - with a plan - to clean up and communicate. ... Visa mer

Thank you for confirming it works, please let us know if you have any other issues. ... Visa mer

As far as we can see, nothing out of the ordinary occured this morning. We can see some 502's in the logs, but more then usual. How many 502's were you getting? Was this under a longer period or just around 7.30? ... Visa mer

Hi, This request of a larger set of improvements aimed at the salesOrder endpoint, that will be under development this year. As of today, we can't say when this will be implemented, we urge you to keep updated about the changes to salesOrder endpoint via our release notes in the news section of the forum.   Thank you.  ... Visa mer

Thank you, I have sent an e-mail! ... Visa mer

These are the differences between 8.26 and 8.29 public class VismaNetApi.CashSaleEndpoint + public Task<bool> PutBydocumentNumberAsync(String documentNumber, CashSaleUpdateDto cashSaleUpdateDto, TimeSpan? timeout) - public Task<bool> PutBydocumentnumberAsync(String documentnumber, CashSaleUpdateDto cashSaleUpdateDto, TimeSpan? timeout) public class VismaNetApi.CashTransactionEndpoint + public Task<CashTransactionDto> GetByreferenceNbrAsync(String referenceNbr, TimeSpan? timeout) - public Task<CashTransactionDto> GetByreferenceNumberAsync(String referenceNumber, TimeSpan? timeout) public class VismaNetApi.CustomerContractEndpoint + public Task<bool> PutBycontractIdAsync(String contractId, CustomerContractUpdateDto customerContract, TimeSpan? timeout) - public Task<bool> PutBycustomerContractIdAsync(String customerContractId, CustomerContractUpdateDto customerContract, TimeSpan? timeout) public class VismaNetApi.CustomerPaymentMethodEndpoint + public Task<bool> UpdateCustomerPaymentMethodBycustomerIdcustomerPaymentMethodIdAsync(String customerId, String customerPaymentMethodId, CustomerPaymentMethodUpdateDto paymentMethod, TimeSpan? timeout) - public Task<bool> UpdateCustomerPaymentMethodBycustomerIdpaymentMethodIdAsync(String customerId, String paymentMethodId, CustomerPaymentMethodUpdateDto paymentMethod, TimeSpan? timeout) public class VismaNetApi.InventoryAdjustmentEndpoint + public Task<bool> PutByinventoryAdjustmentNumberAsync(String inventoryAdjustmentNumber, InventoryAdjustmentUpdateDto adjustment, TimeSpan? timeout) - public Task<bool> PutByadjRefNumberAsync(String adjRefNumber, InventoryAdjustmentUpdateDto adjustment, TimeSpan? timeout) public class VismaNetApi.InventoryIssueEndpoint + public Task<bool> PutByinventoryIssueNumberAsync(String inventoryIssueNumber, InventoryIssueUpdateDto issue, TimeSpan? timeout) - public Task<bool> PutByissueRefNumberAsync(String issueRefNumber, InventoryIssueUpdateDto issue, TimeSpan? timeout) public class VismaNetApi.InventoryReceiptEndpoint + public Task<bool> PutByinventoryReceiptNumberAsync(String inventoryReceiptNumber, InventoryReceiptUpdateDto receipt, TimeSpan? timeout) - public Task<bool> PutByreceiptRefNumberAsync(String receiptRefNumber, InventoryReceiptUpdateDto receipt, TimeSpan? timeout) public class VismaNetApi.InventoryTransferEndpoint + public Task<Uri> PutByinventoryTransferNumberAsync(String inventoryTransferNumber, InventoryTransferUpdateDto transfer, TimeSpan? timeout) - public Task<Uri> PutBytransferRefNumberAsync(String transferRefNumber, InventoryTransferUpdateDto transfer, TimeSpan? timeout) public class VismaNetApi.SalesOrderEndpoint + public Task<bool> PutByorderNbrAsync(String orderNbr, SalesOrderUpdateDto saleOrderUpdateDto, TimeSpan? timeout) - public Task<bool> PutBysalesOrderNumberAsync(String salesOrderNumber, SalesOrderUpdateDto saleOrderUpdateDto, TimeSpan? timeout) public class VismaNetApi.SalesOrderBasicEndpoint + public Task<bool> PutByorderNbrAsync(String orderNbr, SalesOrderBasicUpdateDto saleOrderUpdateDto, TimeSpan? timeout) - public Task<bool> PutBysalesOrderNumberAsync(String salesOrderNumber, SalesOrderBasicUpdateDto saleOrderUpdateDto, TimeSpan? timeout) public class VismaNetApi.ShipmentEndpoint + public Task<bool> PutByshipmentNbrAsync(String shipmentNbr, ShipmentUpdateDto shipmentUpdateDto, TimeSpan? timeout) - public Task<bool> PutByshipmentNumberAsync(String shipmentNumber, ShipmentUpdateDto shipmentUpdateDto, TimeSpan? timeout) ... Visa mer

Hi,   This is also causing big problems for us, we have an external live reporting of the different orders in different stages for external use, however deleted orders have no notification. We have to do a query where we check all orders if they excists, which is not a very clean way to do as the amount of orders grows.           ... Visa mer

Thank you. Then we hope that this issue will be solved very soon, since we need this to make the integration in this matter complete.   ... Visa mer

Hello, currently, the reason we get an immediate response as "InProgress" is due to the release action is asynchronous in all release action exposed endpoints; the process is started in the back end and response is sent back before the process is finished therefore we don't receive status on whether the document is released.   This has already been conveyed to the development team and registered as a wish for improvement. We've updated the case as this request has been repeated. We’ll update you once we hear back.         ... Visa mer

Thank you,  great! ... Visa mer

Hi, The case is currently pending.  We have asked the team for an update, but until they have set an version for this we can't provide an ETA. We will share details as soon as we have more information from the development team.  If you have concerns or thoughts regarding the time frame, please get in contact with your partner service: Contacting the Visma.Net ERP Support / Partner Service ... Visa mer