This we already we followed but how we can create service app for Visma Nxt. ... View more

As of now we have issue of refresh token getting expired after 180 or 365days. Due to this users need to re-setup everything into the system. This make too much issue for users to remember the days. So we have created a service app to avoid refresh token issue.   We have added "Business NXT GraphQL Service API" in the service app. But while authorizing the service app it never asked for Nxt permissions also we are not able to access NXT APIs after authenticating. So by looking at refresh token issue we have planned to shift all visma application from "Web" type of application to "Service" type application. As of now we have Visma e-Accounting, Visma NET, Visma NXT, Dinero (in progress), Visma E-conomic(in progress). Can you please help guide me to have proper solution? ... View more

We have created a service app to resolve the refresh token issue. We are not able to access Visma Nxt services using service app. Which other application supported in service app Dinero, E-conomic, E-accounting etc ... View more

You are correct but I am not able to add customer without tennatID as per service App flow. I need tennatId first for authenticate and generate token. Ref: https://docs.connect.visma.com/docs/service-applications ... View more

Can you please provide me a menu steps? I tried but could not found. ... View more

I cannot find tennatId. For service application I need to know tennatId in advance for generating access token. ... View more

This solution also not works as expected. Upto 24 hours API giving new refresh token on every call. After 24hours it again got invalid. This means every users need to re authenticate them self again every year.   ... View more

This we already following every time but no new refresh token received. ... View more

Need to check at visma side, I have called connect/token API every 5 minutes  before it getting expire of 1 hour. No new refresh token get, this found on development and live app both. This create serious issue of all users who already connected and now they need to re-authorize (consent flow) manually.   ... View more

We already following this. We are sending POST request on https://connect.visma.com/connect/token with headers Content-Type: application/x-www-form-urlencoded Accept: application/json Authorization: Basic base64_encode(client_id:client_secret) With data grant_type=refresh_token refresh_token=current saved refresh token client_id=app client id client_secret=app client secret Every time getting same refresh token. When we get new refresh token after expiration or near to expiration? ... View more

Getting  "invalid_grant" because refresh_token expired. As per above app setting refresh token expire after 30 days. How we can handle this case without involving users? ... View more

Any update on this? ... View more

The above solution does not work properly. As mentioned earlier, availabilityLastModifiedDateTime is applied at the item-warehouse level. While fetching records, we use the lastModifiedDateTime field from within warehouseDetails to maintain the last sync datetime on our end. This allows us to determine up to which date records have been synced with our system. However, the values of this field are not being returned in the correct sort order. For example, we are receiving values like "2024-11-04 20:40:13", "2024-05-30 11:11:57", or "2024-01-15 20:40:13". As a result, the same records keep appearing in the API results, leading to the processing of a large amount of redundant data on our side.     "warehouseDetails": [ { "isDefault": true, "warehouse": "1", "quantityOnHand": 0, "available": 0, "availableForShipment": 0, "lastModifiedDateTime": "2024-11-14T01:19:20.283" } ]     ... View more

Getting same issue on many clients. How can we resolve it? ... View more

How can we put both lastModifiedDateTime and availabilityLastModifiedDateTime  together in "OR" condition? ... View more

How we can keep product stocks and price upto date whenever its changed in visma? We need some way to make product stock/price to be same in Visma and Our system. ... View more

Any API available which call every X interval with filter of lastModifiedTime so we can get only updated products? ... View more

No its not working. Expected to work whenever product stock or any type of price getting changed via any operations? ... View more

In above reply, what I am getting in API response and used in the another API. I am not aware what system assigned number are you talking. Can you please advice me which field or number are you targeting?   ... View more

I have customer invoice   [ { "creditTerms": { "id": "14", "description": "14 dager netto" }, "documentDueDate": "2024-09-12T00:00:00", "cashDiscountDate": "2024-08-29T00:00:00", "exchangeRate": 1.00000000, "attachments": [], "taxDetails": [ { "taxId": "3", "vatRate": 25.000000, "taxableAmount": 1440.0000, "vatAmount": 360.0000 } ], "invoiceLines": [ { "lineType": "GN", "lineNumber": 1, "inventoryNumber": "0014spicychicken", "description": "Spicy Chicken", "quantity": 10.000000, "unitPrice": 64.000000, "unitPriceInCurrency": 64.000000, "manualAmount": 640.000000, "manualAmountInCurrency": 640.000000, "amount": 640.0000, "cost": 0.0000, "amountInCurrency": 640.0000, "account": { "type": "Income", "number": "3000", "description": "Salgsinntekter, avg.pliktig høy sats" }, "vatCode": { "id": "3", "description": "Utgående mva, høy sats" }, "uom": "STK", "discountPercent": 0.000000, "discountAmount": 0.0000, "discountAmountInCurrency": 0.0000, "manualDiscount": false, "subaccount": { "subaccountNumber": "00A1000", "subaccountId": 1, "description": "None", "lastModifiedDateTime": "2020-01-29T13:02:18.967", "active": true, "segments": [ { "segmentId": 1, "segmentDescription": "Avdeling", "segmentValue": "0", "segmentValueDescription": "(Default)" }, { "segmentId": 2, "segmentDescription": "Project", "segmentValue": "0", "segmentValueDescription": "p1" }, { "segmentId": 3, "segmentDescription": "Dynamic", "segmentValue": "A1000", "segmentValueDescription": "A1" } ] }, "deferralSchedule": 0, "branchNumber": { "number": "1", "name": "Panteon AS" } }, { "lineType": "GN", "lineNumber": 2, "inventoryNumber": "005deluxeveggie", "description": "Deluxe Veggie", "quantity": 10.000000, "unitPrice": 80.000000, "unitPriceInCurrency": 80.000000, "manualAmount": 800.000000, "manualAmountInCurrency": 800.000000, "amount": 800.0000, "cost": 0.0000, "amountInCurrency": 800.0000, "account": { "type": "Income", "number": "3000", "description": "Salgsinntekter, avg.pliktig høy sats" }, "vatCode": { "id": "3", "description": "Utgående mva, høy sats" }, "uom": "STK", "discountPercent": 0.000000, "discountAmount": 0.0000, "discountAmountInCurrency": 0.0000, "manualDiscount": false, "subaccount": { "subaccountNumber": "00A1000", "subaccountId": 1, "description": "None", "lastModifiedDateTime": "2020-01-29T13:02:18.967", "active": true, "segments": [ { "segmentId": 1, "segmentDescription": "Avdeling", "segmentValue": "0", "segmentValueDescription": "(Default)" }, { "segmentId": 2, "segmentDescription": "Project", "segmentValue": "0", "segmentValueDescription": "p1" }, { "segmentId": 3, "segmentDescription": "Dynamic", "segmentValue": "A1000", "segmentValueDescription": "A1" } ] }, "deferralSchedule": 0, "branchNumber": { "number": "1", "name": "Panteon AS" } } ], "sendToAutoInvoice": false, "roundingDiff": 0.0000, "customerVatZone": { "id": "01", "description": "Salg innenlands, avgiftspliktig" }, "childRecord": {}, "directDebitMandate": {}, "hold": false, "discountTotal": 0.0000, "discountTotalInCurrency": 0.0000, "detailTotal": 1440.0000, "detailTotalInCurrency": 1440.0000, "vatTaxableTotal": 1440.0000, "vatTaxableTotalInCurrency": 1440.0000, "vatExemptTotal": 0.0000, "vatExemptTotalInCurrency": 0.0000, "paymentReference": "100140000348", "invoiceAddress": { "addressId": 10, "addressLine1": "Langmyrveien 197", "postalCode": "0874", "city": "OSLO", "country": { "id": "NO", "name": "NORGE" }, "county": { "id": "0301", "name": "OSLO" }, "overrideAddress": false }, "invoiceContact": { "contactId": 10, "businessName": "kashyap", "email": "kashyap@gmail.com", "phone1": "99999999", "overrideContact": false }, "applications": [], "dontPrint": false, "dontEmail": true, "revoked": false, "customer": { "number": "10014", "name": "kashyap" }, "documentType": "Invoice", "referenceNumber": "000034", "postPeriod": "082024", "financialPeriod": "202408", "documentDate": "2024-08-29T00:00:00", "origInvoiceDate": "2024-08-29T00:00:00", "status": "Balanced", "currencyId": "NOK", "amount": 1800.0000, "amountInCurrency": 1800.0000, "balance": 1800.0000, "balanceInCurrency": 1800.0000, "cashDiscount": 0.0000, "cashDiscountInCurrency": 0.0000, "paymentMethod": { "id": "1", "description": "Innlandsbetalinger" }, "lastModifiedDateTime": "2024-08-29T08:50:00.313", "createdDateTime": "2024-08-29T08:50:00.313", "note": "", "vatTotal": 360.0000, "vatTotalInCurrency": 360.0000, "location": { "countryId": "NO", "id": "Main", "name": "Primary location" }, "branchNumber": { "number": "1", "name": "Panteon AS" }, "cashAccount": "1910", "project": { "id": "X", "description": "Non-Project Code." }, "account": { "type": "Asset", "number": "1500", "description": "Kundefordringer" }, "subaccount": { "subaccountNumber": "00A1000", "subaccountId": 1, "description": "None", "lastModifiedDateTime": "2020-01-29T13:02:18.967", "active": true, "segments": [ { "segmentId": 1, "segmentDescription": "Avdeling", "segmentValue": "0", "segmentValueDescription": "(Default)" }, { "segmentId": 2, "segmentDescription": "Project", "segmentValue": "0", "segmentValueDescription": "p1" }, { "segmentId": 3, "segmentDescription": "Dynamic", "segmentValue": "A1000", "segmentValueDescription": "A1" } ] }, "metadata": { "totalCount": 1, "maxPageSize": 1000 } } ]   Now I am registering payment for this invoice as per your suggestion   { "referenceNumber": { "value": "000034" }, "type": { "value": "Payment" }, "hold": { "value": false }, "applicationDate": { "value": "2024-08-29T00:00:00" }, "paymentRef": { "value": "Payment ref comment" }, "customer": { "value": "10014" }, "location": { "value": "Main" }, "paymentMethod": { "value": "1" }, "cashAccount": { "value": "1910" }, "currency": { "value": "NOK" }, "paymentAmount": { "value": "1800.00" }, "invoiceText": { "value": "invoice text comment" }, "paymentLines": [ { "operation":"Insert", "documentType": { "value": "Invoice" }, "refNbr": { "value": "000034" }, "amountPaid": { "value": "1800.00" } } ] }   This shows me error, VismaId: 957a08d1-f072-4e6b-b5cb-72ed52247568. Error creating payment. Error: AdjdRefNbr '000034' cannot be found in the system. ... View more

Regarding invoices, How can I register the payment for invoice? Is there any API like voucher or register payment? Any fields available to check invoice paid or partial paid or not paid? ... View more

We need to know below things to start working How we can know order(sales or invoice) is open? How we can complete or change the status of order (sales or invoice)? So it will not come again in list of remaining payment orders. How we can know order(sales or invoice) have not received any payment? So we can know its partial paid or full paid. ... View more

Getting below error while generating order. VismaId: 3bb11d46-2c47-46e1-a3e6-5acca64e70b8. Error creating salesOrder. Error: Dynamic of SalesSubID do not exist. {"orderType":{"value":"IN"},"customer":{"value":"10335"},"orderNumber":{"value":"1153"},"customerRefNo":{"value":"ddd"},"description":{"value":"sa"},"note":{"value":"191141-2-1153-1060-100389"},"date":{"value":"2024-08-27T16:01:26"},"hold":{"value":false},"branchNumber":{"value":"1 "},"soBillingAddress":{"value":{"addressLine1":{"value":"tors gate 811"},"postalCode":{"value":"4632"},"city":{"value":"KRISTIANSAND S"},"overrideAddress":{"value":true}}},"lines":[{"operation":"Insert","inventoryNumber":{"value":"20191108000133"},"description":{"value":"08 product not exist and create"},"quantity":{"value":10},"unitPrice":{"value":"80.00"},"accountNumber":{"value":"3000"},"vatCodeId":{"value":"3"},"warehouse":{"value":"30"},"subaccount":[{"segmentId":1,"segmentValue":"2"},{"segmentId":2,"segmentValue":"0"},{"segmentId":3,"segmentValue":""}]},{"operation":"Insert","inventoryNumber":{"value":"202303240001"},"description":{"value":"24SO Price Test"},"salesOrderOperation":{"value":"Receipt"},"quantity":{"value":5},"unitPrice":{"value":"80.00"},"accountNumber":{"value":"3000"},"vatCodeId":{"value":"3"},"warehouse":{"value":"30"},"subaccount":[{"segmentId":1,"segmentValue":"0"},{"segmentId":2,"segmentValue":"0"},{"segmentId":3,"segmentValue":"A1000"}]}]}   ... View more

So then there is a issue. We are getting "invalid_grant" when we try to run process for multiple companies at same time.  FYI: Out of 18 companies 10 companies use the same branch of visma and other 5 & 3 uses different branch of visma. ... View more