Search
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Sign In
My Products
Help
Sign in or create account
to get a personalized navigation.
Sign in or create account
to get a personalized navigation.
User Profile
KonsultVn
116
Posts
109
Kudos
1
Solution
22-03-2024
15:34
Jag har också flera kunder som efterfrågar denna funktion!
... View more
19-12-2023
10:08
Hi, We have an issue when trying to create a supplier with restrictions active on account level. If we have an expense account with restrictions we get the following message: {
"message": "Error inserting the supplier. Error: Kostnadsställe of VExpenseSubID do not exist."
} And here's the body: POST /controller/api/v1/supplier {
"name": {
"value": "Test"
},
"supplierClassId": {
"value": "40"
},
"overrideWithClassValues": true,
"mainContact": {
"value": {
"name": {
"value": "Test"
}
}
},
"mainAddress": {
"value": {
"addressLine1": {
"value": "Testgatan 1"
},
"postalCode": {
"value": "11111"
},
"city": {
"value": "Testort1"
}
}
},
"glAccounts": {
"value": {
"expenseSubaccount": {
"value": "46-000-000000-0-00000"
}
}
}
} We have tried with "overrideWithClassValues" set and vice versa. We also have an issue when restrictions on the supplier account. Since the supplier ledger sub isn't available via the API we always get an error. Here's the call: POST /controller/api/v1/supplier {
"name": {
"value": "Test"
},
"supplierClassId": {
"value": "40"
},
"overrideWithClassValues": true,
"mainContact": {
"value": {
"name": {
"value": "Test"
}
}
},
"mainAddress": {
"value": {
"addressLine1": {
"value": "Testgatan 1"
},
"postalCode": {
"value": "11111"
},
"city": {
"value": "Testort1"
}
}
}
} ipp-company-id: 4933212 Thanks
... View more
14-12-2023
10:27
Hi again, Any news on this? It's becoming critical because we need to go live soon and we haven't been able to test the integration.
... View more
12-12-2023
09:23
One more thing to add is that we can generate a token with the credentials we are using.
... View more
11-12-2023
14:30
Hi, No additional information in the response body, but it does say "Status: 500 Internal Server Error". Client ID is isv_exsitec_transport and its a new application created via the portal.
... View more
08-12-2023
13:38
Hi, Unfortunately we still get the same error.
... View more
07-12-2023
15:13
Hi, We are receiving this error: {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_e0179a36-7872-4c08-9c3a-2e9711b2441e","ExceptionDetails":""} for every API call we do for only one of our customers. Company ID 4936497. We have tried at different times over the past 4 days and we are still receiving this error. We are using identical integration that the rest of our almost 70 customers are using for Medius<-> Visma.net, and when we receive this error it's usually temporary but this seems to be permanent. I have tried endpoints: controller/api/v1/account controller/api/v1/dimension/ controller/api/v1/supplierinvoice To name a few. Any ideas what can be causing this issue?
... View more
04-12-2023
11:59
Hi, We have an issue when trying to create a customer with restriction for subaccounts enabled. We're trying to create a customer with a customer class that has a specificed sales account with restrictions enabled. Segment 1 is not allowed to be 0 for the account, but the customer class has a default value set in that segment. In the UI this works as expected. We get the response: "Error inserting the customer. Error: Inserting 'Location with address' record raised at least one error. Please review the errors.\r\nError: Kostnadsställe of Sales sub. do not exist." If we disable the restriction group everything works as expected. Here's the request we're trying to make: POST /controller/api/v1/customer Json: {
"corporateId": {
"value": "189001019802"
},
"name": {
"value": "Anna Andersson"
},
"customerClassId": {
"value": "50"
},
"mainContact": {
"value": {
"name": {
"value": "Anna Andersson"
}
}
},
"mainAddress": {
"value": {
"addressLine1": {
"value": "Testgatan 1"
},
"postalCode": {
"value": "11111"
},
"city": {
"value": "Testort1"
}
}
}
} ipp-company-id: 4933212 Thanks
... View more
30-11-2023
09:13
Jag har läst följande ärenden ''Error message when posting Journal Transaction'' där lösningen var att skicka in filerna senare men det är ju inte en rimlig lösning för denna kund tyvärr
... View more
30-11-2023
09:12
Hej, vi fick följande mail från kund: Vi får fel ibland när vi laddar upp verifikat via API och då skapas inte verifikatet alls i Visma. Felet vi får från ert API är: Error: Another process has added 'CADailySummary'. Your changes will be lost." Med samma data så kan det fungera igen efter ett tag eller med ett annat datum, vi ser inget mönster. Exempelvis fick jag fick fel 2st av 8st försök med några minuters mellanrum. Vi har testat att vänta flera timmar i mellan och kan fortfarande få felmeddelande. Filen: Innehåller många transaktioner. Kunden har väldigt många transaktioner dagligen och de kommer behöva skicka ca 30 liknande filer varje dag. Filen innehåller återupprepade rader av likvidkonton. Hur går vi bäst vidare Vi behöver ta i beaktning att detta är en kund som har många transaktioner. och behöver hämta ut filen manuellt flera gånger per dag. Därför fungerar det inte att den ibland inte kan läsas in då det förstör deras planering av arbete för dagen. Tack på förhand, Mvh Nina Christensen
... View more
25-10-2023
15:33
Hi! We are still encountering issues communicating with the API after the migration.. We are consistently receiving numerous 5520-errors as well as a new type of error as shown below. {"message":"VismaId: 5202f96b-979d-43bc-88cc-f452e53654bf. Timeout performing EVAL (5000ms), inst: 76, qu: 0, qs: 0, aw: False, rs: ReadAsync, ws: Idle, in: 0, serverEndpoint: 10.10.6.4:15003, mc: 1/1/0, mgr: 10 of 10 available, clientName: erp09670100003Q, PerfCounterHelperkeyHashSlot: 10848, IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=46,Free=32721,Min=8,Max=32767), v: 2.1.58.34321 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)"}. . We have noticed that the API's status is currently marked as operational on https://status.visma.com, but we wanted to bring to your attention that the issues persist and are causing problems even today. We would greatly appreciate it if you could investigate this matter further.
... View more
23-10-2023
08:39
We have identified the same problem as above this morning along with a 502-gateway error. Is this something Visma are aware of? These seem to mainly occur when handling supplier invoices. Examples of the errors below: {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_f468c19a-16fa-4251-ac21-928d180061dd","ExceptionDetails":""}. {"message":"VismaId: f22461e8-9168-43b8-baf6-a387b230acb0. A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.)"}. . Error response: <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> </body> </html>
... View more
02-10-2023
18:12
Hi, Anders, are you still experiencing Branch '1'-Error? We get the same error on both customer invoice and supplier invoice, but if we wait a few hours after the first failed request, then it seems to work.
... View more
21-08-2023
15:33
We have as of today started experiencing timeout issues with the Visma.Net-API. The problem seems to occur in most of our integrations. It doesn't seem to happen often, maybe 1 out of 200-500 requests. The request was canceled due to the configured HttpClient.Timeout of 120 seconds elapsing. The operation was canceled. The operation was canceled. Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request.. The I/O operation has been aborted because of either a thread exit or an application request.
... View more
16-08-2023
11:16
Hi, Any updates regarding this? 🙂
... View more
16-08-2023
08:55
Hi, We are also having trouble extracting journaltransactions from visma.net API on several customers and we are getting the same error message "An existing connection was forcibly closed by the remote host". We haven't changed anything on our side. Have there been an update to the API that can affect the extract of journaltransactions?
... View more
10-08-2023
11:49
Hi, Any updates regarding this issue?
... View more
07-07-2023
10:53
Hello, How do we obtain the payment information for a supplier that has multiple locations and determine which of the payment details belongs to which location? We have tried this for three different suppliers and retrieve different results. In the first case, we have supplier A where there are two locations where one of them is inactive; the output is that we get results for both locations. We got the same results again for this supplier even if both locations were active. In the second case, we tried retrieving information from supplier B that has two locations, both of them are active. The result is that we only get the information for what is set to be the "primary location". In the third case, we tried retrieving information from supplier C that has three locations where two are active, and one is inactive. The result is that we only get the information for what is set to be the "primary location". In all of these cases the information that is set as 'Primary' is the same information that we see under 'General information'.
... View more
06-07-2023
16:49
Hi, What is the latest news on this? We just did a test today where we converted an integration in test to use Visma Connect authentication (Service API), instead of VNI. Mostly it went fine, but when we tried to post a SupplierInvoice, we got "Error creating supplierInvoice. No access to a branch." We repeated the process, and got the same error from Postman. However, roughly 1h later, we tried again from both postman and the integration, and it worked. Any idea why it did not work at first? And why it works now? We are planning on moving several hundred Service-integrations to Visma Connect during the fall, starting august. But we also need to be able to trust the new authentication system, before we reliably can start any migrations.
... View more
05-07-2023
17:51
Thanks. Here's the requested screenshot:
... View more
04-07-2023
14:11
1. POST controller/api/v2/customerinvoice 2. {
"Note": {
"Value": "2371"
},
"DocumentDate": {
"Value": "2023-06-12T10:46:17.667+02:00"
},
"CurrencyId": {
"Value": "SEK"
},
"CustomerRefNumber": {
"Value": "Matilda Holletrz"
},
"InvoiceText": {
"Value": "2023-06-09 - Mathilda Hollertz - SLF Styrelsem\u00F6te"
},
"CustomerNumber": {
"Value": "10318"
},
"SalesPerson": {
"Value": "94"
},
"InvoiceLines": [
{
"Description": {
"Value": "Atmosf\u00E4ren"
},
"Quantity": {
"Value": 1
},
"UnitPriceInCurrency": {
"Value": 0
},
"Subaccount": [
{
"SegmentId": 1,
"SegmentValue": "937"
},
{
"SegmentId": 2,
"SegmentValue": "999000"
},
{
"SegmentId": 3,
"SegmentValue": "00"
},
{
"SegmentId": 4,
"SegmentValue": "0000"
}
],
"VatCodeId": {
"Value": "04"
},
"AccountNumber": {
"Value": "3911"
},
"Operation": "Insert"
},
{
"Description": {
"Value": "Bredd sm\u00F6rg\u00E5s med ost och skinka"
},
"Quantity": {
"Value": 8
},
"UnitPriceInCurrency": {
"Value": 31
},
"Subaccount": [
{
"SegmentId": 1,
"SegmentValue": "931"
},
{
"SegmentId": 2,
"SegmentValue": "999000"
},
{
"SegmentId": 3,
"SegmentValue": "00"
},
{
"SegmentId": 4,
"SegmentValue": "0000"
}
],
"VatCodeId": {
"Value": "04"
},
"AccountNumber": {
"Value": "3230"
},
"Operation": "Insert"
},
{
"Description": {
"Value": "Bricklunch - serveras mellan 11.00 - 13.00"
},
"Quantity": {
"Value": 6
},
"UnitPriceInCurrency": {
"Value": 107
},
"Subaccount": [
{
"SegmentId": 1,
"SegmentValue": "931"
},
{
"SegmentId": 2,
"SegmentValue": "999000"
},
{
"SegmentId": 3,
"SegmentValue": "00"
},
{
"SegmentId": 4,
"SegmentValue": "0000"
}
],
"VatCodeId": {
"Value": "04"
},
"AccountNumber": {
"Value": "3230"
},
"Operation": "Insert"
}
]
} 3. 4468219 4. Segment 1 and 2 are not allowed to be 0 for specific accounts. This is the same issue which we have experienced regarding supplier invoice and journal transactions for this company. Thanks
... View more
29-06-2023
09:32
Hi, I am recently having issues with overriding Contact and Address information for a location I'm creating. This has worked previously but now the information is inherited from the main address and contact on the customer in spite of using override flags. The fields that don't work are DisplayName on the Contact (with ContactIsSameAsMain = false) and CountryId/Country (with AddressIsSameAsMain = false). I have tried various combination of Country and CountryId and this latest call is with populating both. It makes no difference if I only populate one of them. This is not working for POST nor PUT. We have verified that there are no interfering settings in the Visma.Net company configuration. Here's the call and payload: {Method: PUT, RequestUri: 'https://integration.visma.net/API/controller/api/v1/location/10069/0010900000GDuMx', Version: 1.1, Content: System.Net.Http.StringContent, Headers: { Authorization: Bearer xxxxxx ipp-application-type: Visma.net Financials ipp-company-id: xxxxxxx Content-Type: application/json; charset=utf-8 Content-Length: 577 }} "{\"LocationName\":{\"Value\":\"AstraZeneca AB, M\\u00F6lndal\"},\"Active\":{\"Value\":true},\"AddressIsSameAsMain\":{\"Value\":false},\"Address\":{\"Value\":{\"AddressLine1\":{\"Value\":\"Pepparedsleden 3\"},\"AddressLine2\":{\"Value\":\"Godsmottagningen MA1\"},\"AddressLine3\":{\"Value\":\"Attn: Karin Wiinikka LE110\"},\"PostalCode\":{\"Value\":\"43183\"},\"City\":{\"Value\":\"M\\u00F6lndal\"},\"CountryId\":{\"Value\":\"SE\"},\"Country\":{\"Value\":\"SE\"}}},\"ContactIsSameAsMain\":{\"Value\":false},\"Contact\":{\"Value\":{\"DisplayName\":{\"Value\":\"AstraZeneca AB\"}}},\"VatRegistrationId\":{\"Value\":\"SE559131717601\"},\"CorporateId\":{\"Value\":\"\"}}" It works to change this manually directly in the user interface. However, when I try to send another call to update the existing location (with the manually corrected country) it instead gives me a postcode invalid error as if it's trying to input the postcode from the main address still: Reason: {"message":"Error: Updating 'SelectedLocation' record raised at least one error. Please review the errors.\r\nAn error in processing of field Postcode value WA3 6UT Error: The postcode is invalid.\r\n"} Location in question: Customer: Thank you!
... View more
27-06-2023
08:09
Hi, Perfect! It was set at the same time.
... View more
22-06-2023
19:39
Hi, We have an issue when trying to create a customer invoice with restriction for subaccounts enabled. It's similar to earlier issues we've had when creating supplier invoices and also journal transactions. We get the response: "Error creating customer invoice. Error: Kostnadsställe, Kostnadsbärare of SubID do not exist" "Kostnadsställe" and "Kostnadsbärare" is segment 1 and segment 2. The invoice we're trying to create has a valid set of segments and can be created in the GUI.
... View more
22-06-2023
16:54
Hi! One of our customer have imported stock items via the API. It works fine but for some reason the majority of the items has a value in the columns "last edited by"/"Created by" that says 000000-00000-000-00 instead of the id of the API-user. Anyone who have seen this before? Is it something we should be concerned about?
... View more
15-06-2023
15:05
Hi i'm experiencing a similair issue with "Another process XXXXX" when using this endpoint. It cant be related to simulatenous requests since if tried manual stepping and adding in task.delay(20000). There shouldnt be anything wrong with the data or the environment configuration since it succedes sometimes and fails sometimes with the exact same input data. Overall the success rate is low which stops the customer from going live with the integration. '{"message":"VismaId: fc051b52-eb0c-4c6e-a64f-19ffcd2c5410. Error creating journal transaction. Error: Another process has added 'CADailySummary'. Your changes will be lost."}'
... View more
07-06-2023
13:34
Thanks! I tried linking the customer to a new invoice directly in the UI and received a more detailed error regarding an invalid zip code. It would be greatly appreciated if in the future you could get this error message out rather than the current "Object reference not set to an instance of an object.". It would have made it a lot easier for us in troubleshooting.
... View more
07-06-2023
08:36
Hi, I tried this but we still get the same problem "message": "VismaId: cf5e5143-a594-47a5-8562-9a9b163ed234. Object reference not set to an instance of an object." We need to import this invoice into Visma as quickly as possible. Can you try import the invoice and see what the problem is? Modified json below { "ReferenceNumber": { "Value": "1923" }, "Note": { "Value": "[Fakturanummer: XXXX;KF23]" }, "DocumentDate": { "Value": "2023-06-01T00:00:00" }, "CurrencyId": { "Value": "EUR" }, "CreditTermsId": { "Value": "60" }, "OverrideNumberSeries": { "Value": true }, "ExternalReference": { "Value": "XXX" }, "InvoiceText": { "Value": "Avtal XX-XX XXX" }, "CustomerNumber": { "Value": "10034" }, "PaymentReference": { "Value": "XXXX" }, "FinancialPeriod": { "Value": "202306" }, "InvoiceLines": [ { "Description": { "Value": "Avtalsnr: XX-XX, Avtalsperiod: 2023-06-01 - 2024-05-31" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "-" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "Facility:\r\n XXX" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "-" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "Portar" }, "Quantity": { "Value": 12.0 }, "UnitPriceInCurrency": { "Value": 42.12 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "1001022" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "16" }, { "SegmentId": 4, "SegmentValue": "01" }, { "SegmentId": 5, "SegmentValue": "40" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "19 Doors á 25 SEK" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "-" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "-" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "\"Reverse charge\"" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "0000000" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "00" }, { "SegmentId": 4, "SegmentValue": "00" }, { "SegmentId": 5, "SegmentValue": "00" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "-" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "1001022" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "16" }, { "SegmentId": 4, "SegmentValue": "01" }, { "SegmentId": 5, "SegmentValue": "40" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "Ert momsregistreringsnummer XXXX" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "1001022" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "16" }, { "SegmentId": 4, "SegmentValue": "01" }, { "SegmentId": 5, "SegmentValue": "40" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" }, { "Description": { "Value": "Omvänd betalningsskyldighet gäller för denna faktura" }, "Quantity": { "Value": 1.0 }, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "1001022" }, { "SegmentId": 2, "SegmentValue": "800839" }, { "SegmentId": 3, "SegmentValue": "16" }, { "SegmentId": 4, "SegmentValue": "01" }, { "SegmentId": 5, "SegmentValue": "40" }, { "SegmentId": 6, "SegmentValue": "00" } ], "VatCodeId": { "Value": "04" }, "AccountNumber": { "Value": "3046" }, "Operation": "Insert" } ] }
... View more
Activity Feed for KonsultVn
- Kudoed LÖST: Känt fel med automatmatchningen i Behandla Kontoutdrag CA306000 for Derek Josefsson. 15-07-2024 14:27
- Kudoed Länk till Approval när attestant får mail om att det är dags att attestera en faktura i Approval for 2110. 16-05-2024 13:25
- Posted Svar: Kontosaldo i separat kolumn per rad vid verifikationsregistring on Förbättringsförslag för Visma Net. 22-03-2024 15:34
- Kudoed Kontosaldo i separat kolumn per rad vid verifikationsregistring for GEBEE2019. 22-03-2024 15:33
- Got a Kudo for Automatisk Koddelsträng. 18-01-2024 09:26
- Kudoed KN-kod som fält i PEPPOL-formatet for sandrajornklev. 18-01-2024 08:52
- Posted Error creating suppliers with restrictions on account on Forum in Developers Visma.net. 19-12-2023 10:08
- Posted Svar: Error 5520 on every call on Forum in Developers Visma.net. 14-12-2023 15:36
- Posted Svar: Error 5520 on every call on Forum in Developers Visma.net. 14-12-2023 10:27
- Posted Re: Error 5520 on every call on Forum in Developers Visma.net. 12-12-2023 09:23
- Posted Re: Error 5520 on every call on Forum in Developers Visma.net. 11-12-2023 14:30
- Posted Re: Error creating customer with restrictions active on Forum in Developers Visma.net. 08-12-2023 13:38
- Posted Error 5520 on every call on Forum in Developers Visma.net. 07-12-2023 15:13
- Posted Error creating customer with restrictions active on Forum in Developers Visma.net. 04-12-2023 11:59
- Posted Svar: Felmeddelande med inläsning av filer via API on Forum in Developers Visma.net. 30-11-2023 09:13
- Posted Felmeddelande med inläsning av filer via API on Forum in Developers Visma.net. 30-11-2023 09:12
- Posted Svar: 5520 on Forum in Developers Visma.net. 25-10-2023 15:33
- Posted Svar: 5520 on Forum in Developers Visma.net. 23-10-2023 08:39
- Kudoed 5520 for andreasaulin. 23-10-2023 08:31
- Posted Re: POST CustomerInvoice. Error: 'RevisionID' cannot be empty. on Forum in Developers Visma.net. 02-10-2023 18:12
Useful pages
Contact us
Copyright © 2022 Visma.com. All rights reserved.
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America