About Yıldırım

Yıldırım · ‎09-02-2023

Hello, are you looking for Sales & Purchase Orders ? SalesOrder<ScreenId=SO3010PL> PurchaseOrder<ScreenId=PO3010PL> You can find endpoints available for SalesOrder and PurchaseOrder modules by searching in the swagger.

Yıldırım · ‎09-02-2023

Hello Erik, currently approval process is manually checked by the related team on the portal and approval time may vary, this will soon be automated based on Partner Service <Country> However, could you please send your Application details to developersupport@visma.com so that we can inform the team ? Thanks.

Yıldırım · ‎09-02-2023

Hi, every company can have different configurations, therefore you might receive an error in one when the other is working fine with the same request. Could you check your "customer ledger preferences" (ScreenId=AR101000) on the company that you receive the error and send us a print screen ?

Yıldırım · ‎08-02-2023

Registered.

Yıldırım · ‎08-02-2023

Can you provide the POST JSON used in the 1303428-DEMO Mer Sweden AB

Yıldırım · ‎08-02-2023

@SitterIT & @Anders_Traventus Could you please provide Financials ERP Company IDs where you're using POST - SalesOrder Service API ?

Yıldırım · ‎08-02-2023

If you're having the same issue for the other companies, please follow the troubleshooting steps that has been provided earlier. If it doesn't help, then again send us the segment key - values setup in the format of the ones shared earlier, for each company. Thanks.

Yıldırım · ‎08-02-2023

Hello, could you share your POST request, including headers and body ? Additionally please also send your API ClientID & Company ID to developersupport@visma.com Thanks.

Yıldırım · ‎25-01-2023

In addition to what Magnus shared, you can also check this through developer portal. My applications > Select Application > Integrations

Yıldırım · ‎20-01-2023

This has been registered as a bug and conveyed to the development team. 1) Create Sales Order (Single line) 2) Create Shipment for that salesOrder (Single Shipment line) 3) Shipment status: Open 4) Salesorder status: Shipping 5) PUT - Delete Shipment Line > OK 6) SalesOrder status, still Shipping. If we remove the Shipment Line via Financials ERP UI 7) Sales order status become : Open

Yıldırım · ‎20-01-2023

I've noticed that SegmentID=2 (Projekt+AO) has length 9 with validation, but in the payload you're sending 8 zeros so please add one more zero and try again. "Operation": "Insert", "Subaccount": [{ "SegmentId": 1, "SegmentValue": "00000" }, { "SegmentId": 2, "SegmentValue": "00000000" }, { "SegmentId": 3, "SegmentValue": "000" }, { "SegmentId": 4, "SegmentValue": "00" } ] } ],

Yıldırım · ‎20-01-2023

Hello, thank you for reporting this. We'll check it out.

Yıldırım · ‎20-01-2023

Can you please make sure that subaccount combination sent in the payload exist in the following module ? <ScreenId=GL203000>

Yıldırım · ‎20-01-2023

Hello, could you please send your API Client ID & Company ID that webhook subscription made with ? <developersupport@visma.com>

Yıldırım · ‎19-01-2023

Hello, Please don't send key-value in the payload with empty or null, you can find the edited version of your JSON below. { "SupplierNumber": { "Value": "50048 " }, "SupplierReference": { "Value": "100006.1" }, "Note": { "Value": ";Administrationstjänster//;Omkostnader//" }, "CurrencyId": { "Value": "SEK" }, "DueDate": { "Value": "2023-02-16T01:00:00+01:00" }, "Date": { "Value": "2023-01-17T01:00:00+01:00" }, "SupplierTaxZone": { "Value": "01" }, "PaymentRefNo": { "Value": "100006" }, "CashDiscountDate": { "Value": "2023-02-16T01:00:00+01:00" }, "InvoiceLines": [{ "LineNumber": { "Value": 1 }, "CostInCurrency": { "Value": 34246.58 }, "AccountNumber": { "Value": "4990" }, "VatCodeId": { "Value": "01" }, "Operation": "Insert", "Subaccount": [{ "SegmentId": 1, "SegmentValue": "30098" }, { "SegmentId": 2, "SegmentValue": "30098A001" }, { "SegmentId": 3, "SegmentValue": "000" }, { "SegmentId": 4, "SegmentValue": "00" } ] }, { "LineNumber": { "Value": 3 }, "CostInCurrency": { "Value": -0.23 }, "AccountNumber": { "Value": "3740" }, "VatCodeId": { "Value": "12A" }, "Operation": "Insert", "Subaccount": [{ "SegmentId": 1, "SegmentValue": "00000" }, { "SegmentId": 2, "SegmentValue": "00000000" }, { "SegmentId": 3, "SegmentValue": "000" }, { "SegmentId": 4, "SegmentValue": "00" } ] } ], "DocumentType": { "Value": "Invoice" } } Additionally, please send us a print screen showing your subaccount > Segment & Values from the Financials ERP UI. Segment Keys <ScreenId=CS202000&DimensionID=SUBACCOUNT> then by clicking "segment ID" you can check available Segment Values for the Subaccount

Yıldırım · ‎19-01-2023

Hi, this should be fixed in [Release Notes] - Sales Order Service API 1.0.14.338

Yıldırım · ‎18-01-2023

Hello, this issue has been fixed in [Release Notes] - Visma.Net API 9.30.0 - 17.01.2023

Yıldırım · ‎18-01-2023

Hello, can you send your payload ? Also, is there any Branch or user restriction for the Subaccount Segments in the Financials ERP company ?

Yıldırım · ‎16-01-2023

Hello, to be able to add PaymentMethod & Cash account combinations, those assets should be registered in the Company > Branch you're working with. For example, checking the availability of the desired Payment Method and the Cash Account in the Sales Order > Payment settings tab. Please see the transactions below for POST Sales Order with PaymentMethod & Cash Account, then creating a payment via API for that Sales Order. 1) POST Sales Order <https://integration.visma.net/API/controller/api/v2/salesorder> { "lines": [ { "operation": "Insert", "inventoryNumber": { "value": "1" }, "quantity": { "value": 2.0 }, "unitPrice": { "value": 39.00 }, "lineDescription": { "value": "test" } } ], "orderType": { "value": "SO" }, "hold": { "value": false }, "date": { "value": "2023-01-16" }, "customer": { "value": "01235" }, "currency": { "value": "NOK" }, "description": { "value": "test" }, "paymentMethod": { "value": "4" }, "cashaccount": { "value": "1900" } } Financials ERP UI Output 2) POST Customer Payment for the recently created Sales Order { "type": { "value": "Payment" }, "hold": { "value": false }, "paymentRef": { "value": "123456" }, "customer": { "value": "01235" }, "paymentMethod": { "value": "4" }, "cashAccount": { "value": "1900" }, "currency": { "value": "NOK" }, "paymentAmount": { "value": 78 }, "ordersToApply": [ { "operation": "Insert", "orderType": { "value": "SO" }, "orderNumber": { "value": "000536" }, "appliedToOrder": { "value": 0 } } ] } Financials ERP UI Output

Yıldırım · ‎16-01-2023

Hi, Please correct the syntax in your payload by replacing "," with "." "paymentAmount": { "value": 122,76 }, "paymentAmount": { "value": 122.76 }, Then please also try the transaction without "paymentMethod": { "value": "Paytrail" }, "cashAccount": { "value": "1910" }, to see what default values system assigns.

Yıldırım · ‎13-01-2023

Hello, this has been reported as an error, and it is currently under review by the team.

Yıldırım · ‎12-01-2023

Hello, we've informed the development team once again that the request has been repeated. We'll share updates as soon as there is a change in the status.

Yıldırım · ‎11-01-2023

Release Notes Documentation More context fields in Webhook notifications Webhook notifications will now contain more context fields: ApiClientId (if notification was triggered by an API, identifies the API integration client) TenantId (identifies the tenant/company) ConnectId (identifies the user) IsScheduler (true if notification was triggered by a scheduled task, otherwise false) GET SupplierPayment endpoint not displaying all fields in paymentLines Missing fields “batchNumber”, “description” and “currency” are now included in the paymentLines for the GET SupplierPayment endpoint. Due dates for breaking changes Release Notes. Documentation Due Remove deprecated parameters in Financial Period endpoint The numberToRead and skipRecords parameters for the financial period endpoint are deprecated and will be removed. Feb 28, 2023 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎11-01-2023

Great news !

Yıldırım · ‎11-01-2023

Hello, this has been reported to the Sales Order Service API team so that it'll be reviewed to determine whether this is working as designed or a bug.

Yıldırım · ‎11-01-2023

Hi, the most convenient way to troubleshoot this operation is trying the same process in the Financials ERP UI so that you can review if the order is available for the payment in the look-up table. There are certain workflow logics in the Financials ERP, E.g Customer Payment > OrdersToApply can fetch the document before SO is invoiced.

Yıldırım · ‎11-01-2023

Hello, underscore (_) is used as whitespace identifier in the Financials ERP UI, therefore system doesn't allow assigning that. If you have items, please send us a print screen from the UI and GET Inventory response where we can see the returned Inventory Number. So that you can also try using Method for getting resources with reserved characters - B64URL Encoding

Yıldırım · ‎10-01-2023

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.

Yıldırım · ‎05-01-2023

Good to hear, please send your API Client ID & Financials ERP Company ID to developersupport@visma.com so that we can investigate in detail.

Yıldırım · ‎05-01-2023

You should be able to test the other endpoints with the current token that you're using. When it comes to the logs, we're unable to see further details of what might cause this. Since this is only happening on the specific client, this is most likely related to that user & the company. Please send your API Client ID & Financials ERP Company ID to developersupport@visma.com. Regarding the troubleshooting, please review the article API incidents - Troubleshooting and reporting We need information on these details to be able to help you. Every integration should have their own specific user to generate token with, so that please contact your client to login them via Swagger & Financials ERP UI to check access related parts. Thanks.

Re: Production orders

Re: App review time

Re: Error creating document. Error: TaxCategoryID ...

Re: Known issue: Visma.net ERP Sales order API v3 ...

Re: SalesOrder api subaccount issue mandatory

Re: SalesOrder api subaccount issue mandatory

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: POST /v2/customerinvoice creates multiple back...

Re: Visma Connect Authentication for Visma.net ERP...

Re: Deleting lines on shipment puts order in stran...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Deleting lines on shipment puts order in stran...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Is it possible to see the webhook response?

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: SalesOrder api subaccount issue mandatory

Re: Missing "Description" field on SupplierPayment...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Correct way to add a payment to an order

Re: Creating payment error: the specified combinat...

Re: Paging in SalesOrderApi

Re: Lot-/Serialtype is missing in endpoint

[Release Notes] - Visma.Net API 9.30.0 - 17.01.202...

Re: Visma.net ERP NeXtGen Sales Order Service v3: ...

Re: SalesOrder V3 - customerId filter bug

Re: Creating payment error: the specified combinat...

Re: Any limits in product codes?

Re: Webhook received multiple times when shipment ...

Vastaus: Getting 5520 for sending timeCard

Vastaus: Getting 5520 for sending timeCard

Useful pages

About Visma

Contact us

Follow us