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
12-01-2023
10:38
17 Kudos
Hej, Jag vill härmed lägga fram ett önskemål om en inställning till v.net som kan ha stor positiv påverkan för systemets användare. Önskemålet avser, som flera andra system redan kan, att man ska genom att kunna välja ett segmentvärde i koddelsträngen att systemet automatiskt skriver ut hela förutbestämda koddelsträngen. Jag ska förklara vidare genom ett exempel: Kund använder v.net med en koddelsträng som innehåller följande segment: Projekt längd 7, kostnadsställe längd 4 samt Arbetschef längd 3. Genom att välja ett specifikt projekt så ska alltså systemet skriva ut kostnadsställe och arbetschef. Detta baserat på att ett projekt alltid tillhör ett och samma kostnadsställe och ett och samma arbetschef. Säg projekt 1234567 tillhör kostnadsställe 1234 och arbetsledaren 12. Då önskar vi att inte fylla i alla tre utan genom att välja projekt 1234567 så ska kostnadsställe 1234 och arbetsledaren 12 skrivas ut automatiskt. Önskemålet innebär inte att exempelvis om man väljer kostnadsställe att projekt och arbetschef ska skrivas ut då kostnadsstället kan innehålla flera projekt. Utan just utifrån val av ett specifikt segment (projekt i detta fallet.) Denna önskan kommer från ett projektintensivt företag inom bygg. Antal projekt som rullar ca 2 500 st varav ca 800 som går över bokslut. Vänligen återkoppla till mig när ni läst och vad som händer i ärendet.
... View more
20-12-2022
16:07
Hi, We have a customer that would like to be able to fetch, create and update supplier classes in their different companies. Today it is only possible to fetch a smal amount of information under the Supplier endpoint, but we would like to fetch, create and update the supplier classes with more information.
... View more
19-12-2022
14:29
Hi, Is there any way to create supplier classes via the API? The only thing close to that of what I can see is fetching some information about a supplier class via the Supplier endpoint. But I would like to fetch more information and also to be able to create supplier classes in visma, is that possible?
... View more
13-12-2022
08:37
Hi, I have encountered the same issue. I have tried the workaround without success. I still get the same issue when sending a PUT request updating the salesperson field. This is the payload I am sending when this issue occurs: { "lines": [ { "salesPerson": { "value": "03" }, "operation": "Update", "lineNbr": { "value": 3 }, } ], "orderType": { "value": "EK" } } The update goes through and the sales person is set to 03 but the dimension values that originally is set to "3-090-03110" is updated to "0-090-00000"
... View more
07-12-2022
08:24
Hi, I'm inputting dimensions as per each invoice line, but would like to also add it to the customer invoice/credit note itself. See below for the requested field. I couldn't immediately find it on the [POST]/controller/api/v2/customerinvoice example model. Is this possible, and if so, which endpoint/property on the object? Thanks!
... View more
12-10-2022
10:37
Hi! I am currently looking into fetching currency rates from /controller/api/v2/currencyrate. I noticed that the only parameters available which narrows the output of currency rates are "toDate" and "fromDate". I could simply fetch currency rates on a daily basis and only fetch the rates which are new for the day given that I use toDate and fromDate in tandem with the the date of the fetch. How am I supposed to be able to update previous days currency rates without fetching all available rates from all available dates and compare to a previous fetch to distinguish which rates are updated? What I really am wondering is, is there any way to have a parameter with "last modified date" or similar to fetch all rates which have been updated since I previously fetched data?
... View more
22-09-2022
16:15
1 Kudo
The issue we have is that when we fetch a list of supplier invoices I will get all the supplier invoices that exists, but when we fetch some invoices separatly I get an error that says that the invoice doesn't exist. The only difference that we can see on the invoices is that the ones we can't fetch separatly is credit invoices. Why is it that we can fetch all invoices at once but not when we fetch them separatly?
... View more
01-09-2022
16:17
Okay, then it was as I suspected. Thank you!
... View more
31-08-2022
14:51
And we aren't sending any other requests other than the update request with this type of content.
... View more
31-08-2022
14:37
Hi, This is an example of how the request can look lite that we send to visma: { "name":{"value":"TEST"}, "status":{"value":"Active"}, "supplierClassId":{"value":"10"}, "creditTermsId":{"value":"30"}, "currencyId":{"value":"SEK"}, "paymentMethodId":{"value":"01"}, "cashAccount":{"value":"1930"}, "vatRegistrationId":{}, "corporateId":{}, "vatZoneId":{"value":"01"}, "accountUsedForPayment":{"value":"BANKGIRO"}, "mainAddress":{ "value":{ "addressLine1":{}, "addressLine2":{}, "addressLine3":{}, "postalCode":{}, "city":{}, "countryId":{"value":"SE"} } }, "supplierPaymentMethodDetails": [ { "paymentMethodDetailDescription":"Bankgironummer", "paymentMethodDetailValue":{"value":"1234-1234"} }, { "paymentMethodDetailDescription":"Plusgironummer", "paymentMethodDetailValue":{} } ], "attributeLines": [ { "attributeId":{"value":"MOMSKAT"}, "attributeValue":{"value":"40"} } ] } We don't have any issues with creating or updating suppliers otherwise. We only have issues when we try to change the payment method.
... View more
31-08-2022
08:42
Hi, We have an issue with updating the PaymentMethodId, AccountUsedForPayment and the SupplierPaymentMethodDetails. As an example we have a supplier that already has PaymentMethodId = 01, AccountUsedForPayment = Bank transfer (Bankgiro in swedish) and a giro number in the payment method details. If we then try to update this supplier with a new PaymentMethodId, lets say 04, and AccountUsedForPayment to IBAN and set new SupplierPaymentMethodDetails, we get an error saying that the giro number doesn't exist. Why do we get this error and shouldn't it be possible to change all this information at once?
... View more
30-08-2022
12:06
Hi, From Upsales: New information is added, changed or disappears. It does not have to be information needed to sync to Visma.NET. As soon as we feel that something is happening on the customer card, we sync everything to Visma.NET to be on the safe side that there is always correct information in both systems. Exempel: See Custumer 441025 in Visma.net.
... View more
23-08-2022
15:54
Många kunder som använder ankomstregistrering har behov av att få med data på radnivå vid slutbokning. Vid attest så kan datan behöva ändras eller så delas rader och då behöver vi ha möjlighet att uppdatera befintliga rader samt att lägga in datan på nya rader (väldigt vanligt case vid integration med Medius). Beskrivningsfältet går inte att ändra på ankomstregistrerade fakturor (detta är också ett förslag att ändra). Ett annat alternativ är att ändra radanteckningen. Radanteckningen kan ändras i Visma.net på ankomstregistrerade fakturor i portalen men inte via APIet. Om vi hade tillgång till anteckning på raden så kunde det fungera i vissa fall (önskar dock även att beskrivningsfältet blev redigerbart).
... View more
23-05-2022
16:23
Hi Magnus, any news today? Br Linnea
... View more
13-05-2022
16:41
Är det möjligt att använda olika OCR-nummer på Skatteverket för olika företagsgrenar?
... View more
10-05-2022
16:11
Hi Magnus, any news? Br Linnea
... View more
27-04-2022
07:54
Hi Magnus Do you have any status update? Br Linnea
... View more
20-04-2022
17:38
Hi Magnus, do you have any status from the developers? Br Linnea
... View more
19-04-2022
09:56
Löst! Problemet var att kunden inte hade Sverige som land.
... View more
19-04-2022
09:19
Hej, När jag försöker skapa en kundfaktura ger kunden ett felmeddelande: "Det uppstod ett fel under behandling av fältet Postnummer med värdet 61380 Fel: Ogiltigt postnummer." Tar jag bort postnumret på kunden får jag inte längre några fel. Jag förstår inte varför det blir fel med detta postnumret då det är ett giltigt postnummer. Bild nedan:
... View more
08-04-2022
10:39
Hi Magnus Have you had a chance to look at this? Tell me if you want us to inform you more about the case by phone. Best regards Linnea
... View more
07-04-2022
15:45
Thanks. Customer case-number is 00146406. Do you reach it?
... View more
07-04-2022
14:35
Thanks. Yes we have noticed another problem with the deductible services but we are not sure they are API related. We have reported this to the support, can I send you the ticket-nbr?
... View more
07-04-2022
12:32
Hi Normally the value is 30% of the work, but in these cases it is not. Labor cost concerning heat pump installations are not always 30%, and until january we have been able to override the logic in Visma.net trough the API. Now we can not do that.
... View more
06-04-2022
08:10
Hi Magnus, what is the status on this?
... View more
04-04-2022
08:51
Hi We are expecting Total Deductible Amount to be the same as the Amount in RUT and ROT Distribution, as seen in pictures below. This invoice is created with the same integration. Sine middle of january, we get this instead: When creating in the UI, I get the same problem. See picture below.
... View more
31-03-2022
14:31
We have a customer that uses the rut/rot functionality through the API on the CustomerInvoiceV2 endpoint. We have noticed that since middle of january we get wrong amount summed up on the RotRut-total. When using this Json today we get the wrong amount. When we used the same in the beginning of january we got the right amount. Our conclusion is that the check box "distributedAutomatically" does not work in the same way. { "customerNumber": { "value": "61938" }, "creditTermsId": { "value": "30" }, "documentDate": { "value": "2022-03-31T00:00:00.000Z" }, "invoiceText": { "value": "98158 Samma som faktura 106523 Helsingborg" }, "note": { "value": "Ordernummer: 98158\r\nProjektnummer: 2000102\r\nArbetsbeskrivning:\r\nSamma som faktura 106523 Helsingborg" }, "salesperson": { "value": "102" }, "externalReference": { "value": "Test Husarbete" }, "locationId": { "value": "HR5RWLIAVVEUFACN4FC65OSQ54" }, "domesticServicesDeductibleDocument": { "value": true }, "rotRutDetails": { "type": { "value": "Rot" }, "distributedAutomaticaly": { "value": false }, "organizationNbr": { "value": "" }, "estate": { "value": "Berget 12:1" }, "appartment": { "value": "" }, "distribution": [ { "operation": "Insert", "lineNbr": { "value": 0 }, "personalId": { "value": "198601015608" }, "amount": { "value": 14542 }, "extra": { "value": false } } ] }, "invoiceLines": [ { "operation": "Insert", "lineNumber": { "value": 1 }, "domesticServicesDeductible": { "value": false }, "description": { "value": "V\u00E5rt ordernummer: 98158" }, "quantity": { "value": 0 }, "accountNumber": { "value": "9999" } }, { "operation": "Insert", "lineNumber": { "value": 6 }, "domesticServicesDeductible": { "value": true }, "itemType": { "value": "Service" }, "typeOfWork": { "value": "Plumbing" }, "description": { "value": "Fast pris" }, "uom": { "value": "st" }, "quantity": { "value": 17.5 }, "manualAmountInCurrency": { "value": 110800 }, "accountNumber": { "value": "3031" }, "vatCodeId": { "value": "01" }, "subaccount": [ { "segmentId": 1, "segmentValue": "12" }, { "segmentId": 2, "segmentValue": "12" }, { "segmentId": 3, "segmentValue": "2000102" }, { "segmentId": 4, "segmentValue": "98158" }, { "segmentId": 5, "segmentValue": "0" } ] } ] }
... View more
01-03-2022
16:34
Thanks!
... View more
28-02-2022
16:31
For Monde Verde (company id: 2301700) we can not get past an error in the production environment when creating a sales order. The same setting works in their test company (2183985). We have compared the settings on SOs and Inventory and it seems to be the same. What is casting the error in the production company? The error is: requestUri: controller/api/v2/salesorder / method: post / headers: Content: application/json Authorization: Bearer 09f153ee-35e0-4eda-9b98-80803ce4ade5 ipp-application-type: Visma.net Financials ipp-company-id: 2301700 / response content: {"message":"VismaId: 189900ef-1a30-4529-8f87-90f3cd89192c. Error creating salesOrder. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> PX.Data.PXSetPropertyException: Inventory error: Item cannot be sold\r\n at PX.Data.PXRestrictorAttribute.Verify(PXCache sender, PXFieldVerifyingEventArgs e, Boolean IsErrorValueRequired)\r\n... The request body is for prod is: (for the test environment we change to customer 49999 and any product number in the catalog) { "OrderType": { "Value": "SO" }, "CustomerRefNo": { "Value": "test" }, "CustomerOrder": { "Value": "test" }, "OrigOrderNbr": { "Value": "test" }, "Hold": { "Value": false }, "Description": { "Value": "Sofie test" }, "Customer": { "Value": "40009" }, "SoShippingAddress": { "Value": { "AddressLine1": { "Value": "Smedsbacksgatan 20" }, "PostalCode": { "Value": "11539" }, "City": { "Value": "Stockholm" }, "Country": { "Value": "Sverige" } } }, "SoBillingAddress": { "Value": { "AddressLine1": { "Value": "Smedsbacksgatan 20" }, "PostalCode": { "Value": "11539" }, "City": { "Value": "Stockholm" }, "Country": { "Value": "Sverige" } } }, "Lines": [ { "Operation": "Insert", "InventoryNumber": { "Value": "111214" }, "LineDescription": { "Value": "ALASTAR C M OPAL, pendlad" }, "Quantity": { "Value": 1 }, "UnitPrice": { "Value": 1869.4872 }, "UnitCost": { "Value": 0 }, "DiscountAmount": { "Value": 0 }, "AlternateId": {}, "MarkForPO": { "Value": true }, "PoSource": { "Value": "DropShipToOrder" } }, { "Operation": "Insert", "InventoryNumber": { "Value": "111821" }, "LineDescription": { "Value": "L1:Opus 200 h\u00F6jd 131 mm gr\u00E5 IP44 rak 12W flickerfri LED 1300lm 3000K Ra\u003E90" }, "Quantity": { "Value": 1 }, "UnitPrice": { "Value": 2131.8 }, "UnitCost": { "Value": 2131.8 }, "DiscountAmount": { "Value": 0 }, "AlternateId": {}, "MarkForPO": { "Value": true }, "PoSource": { "Value": "DropShipToOrder" } } ], "OrderNumber": { "Value": "" }, "SoShippingContact": { "Value": { "overrideContact": { "Value": true }, "name": { "Value": "" }, "attention": { "Value": "" }, "phone1": { "Value": "" } } } }
... View more
24-09-2021
13:26
1 Kudo
När man trycker på direktlänkarna för ”Antal förfallna poster” i vy Förbered påminnelser AR521000 är det önskvärt att man får upp ett fönster med just dessa poster. När man trycker på länken i dagsläget, hamnar man i fönstret Kunduppgifter där samtliga av den valda kundens öppna fakturor visas. Även ej förfallna fakturor visas där vilket gör det svårt att få en överblick av de förfallna fakturor i respektive påminnelsenivå man egentligen hade velat se. En work around är att bocka i ”Dela upp efter verifikationsnummer”, göra urval på kunden och sedan urval på påminnelsenivå i kolumnen påminnelsenivå. Det vore dock smidigare att direkt kunna trycka på länken till postantalet för att se aktuella fakturor.
... View more
- Find more ideas tagged with:
- påminnelser
See more ideas labeled with:
- « Previous
- Next »
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