Breaking changes

[adrianm]

Just to ensure you are aware that changing operationId in swagger is a breaking change for us using auto-generated clients.

It is fine to change things, even if I don't understand why e.g. "Nbr" is better than "Number", but please put it into the release notes.

[adrianm]

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)

[Magnus Johnsen]

Hi,

Did you see for what endpoint this happened?

If so, it would help us let the correct team know that they left it out and as a consequence you're having issues. 

Thank you.