Om RRTT

Marko Koivuniemi · ‎10-04-2025

Hienoa että jaoit tämän tänne. Saattaa olla että tulevaisuudessa jonkun muutama hius jää harmaantumatta tai irti repimättä päästä tai molemmat.

Sandra Anté · ‎14-06-2024

Hi again, The fix is turned on for this customer now. We will write and update in the case when it is active in prodcution. Kind regards Sandra

Jukka Taivassalo · ‎19-04-2024

Hei, Tämä on raportoitu virheenä.

Marten Voort · ‎08-04-2024

Thanks for the information! I have tested this with the same settings and your supplied script. I was not able to reproduce this behaviour, in my test both api and UI provide the same costprice based on the components. Further investigation is needed. I advice you to contact country specific support, because this seems to be specific for your situation. For more information see https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710

RRTT · ‎24-10-2023

Hei! Kyselylistoille (kuten Myyntitilaukset) on muokattavissa ns. hakukenttiä, joihin on mahdollista yhdistää useammasta kentästä haettavaa tietoa. Tällöin siis yhden haun voi siis kohdistaa ns. useampaan kenttään yhdellä kertaa. Autamme tässä tarvittaessa. Uudet hakuominaisuudet myös paranivat alkuperäisestä. Enää prosenttimerkkejä ei (juurikaan) tarvitse. Versiosaatteesta: When you use the column search line in a list window, you can now search for multiple partial or complete words in random order, by separating the words with a space. You will then get all results containing these words in any order. If you want to search for partial or complete words in a specific order, use "%" as a separator between the words. "%" also functions as a wildcard when you search on a specific order of words. Example: There are two customer names, "Big data customer" and "Customer Big Data". When you search on: - "big data cust" or "Big data customer", you will get both customer names in your result, - "big%cust", data%cust or "Big%customer", you will only get customer name "Big data customer" in your result, - "cust%big", "cust%data" or "customer%data", you will only get customer name "Customer Big Data" in your result

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

Hello, just an update, following is the status of the V3 Sales Order Endpoint on Inventory (Supplier Details). It is set up right now that the supplier data is set to the line if/when the "purchase order source" is specified in the payload, as the supplier is used when creating PO for the order line. So, In order POST SalesOrder V3 to be able to fetch the Supplier data of the selected item, "purchaseOrderSource": "string" should be specified in the payload. https://salesorder.visma.net/swagger/index.html Example: { "type": "SO", "date": "2023-08-18", "description": "Test Sales Order", "customer": { "id": "10022" }, "orderLines": [ { "inventoryId": "1", "description": "Test Sales OrderLine 1", "quantity": 5, "unitPrice": 10, "taxCategoryId": "3", "unitOfMeasure": "STK", "purchaseOrderSource": "purchaseToOrder", "subaccount": { "1": "00", "2": "01", "3": "03", "4": "04" } } ] }

RRTT · ‎12-04-2023

Hei! Vain Ei-varastotuotteita sisältävän laskun voi kopioida Myyntilaskut -ikkunan toimintopalkin leikepöytätoiminnolla uudeksi laskuksi. Varastotuotteita sisältävät laskut täytyy aina tehdä myyntitilausten kautta. Myyntitilaukset voi kopioida uudeksi tilaukseksi.

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

Hello, we confirm the issue. This has been reported to the development team. We will provide further updates as more information is available.

RRTT · ‎28-12-2022

PicklistPrinted and ShipConfirmationPrinted are needed for WMS purposeses on GET Shipment endpoint. Whit those information it would be possible to more accurately identify correct shipments to be picked by mobile devices.

RRTT · ‎13-10-2022

Hi! For WMS purposes we need to GET PickPriority from Warehouse endpoint. PickPriority POST and PUT warehouse/{warehouseID}/location seems already to be possible.

Katja Salminen · ‎09-09-2022

Tämä on täysin sallittua. Systeemi ei tarkista onko ideaa ehdotettu aikaisemmin.

Yıldırım · ‎04-02-2022

Hello, the case related to the performance improvement - Inventory Endpoint released in Visma.Net API 8.82.0 - 01.02.2022 has caused some inconsistencies, therefore it has now been rolled back so that endpoint should be operating normal as used to. Please check this out, and please let us know if you still face any issues. Thanks.

RRTT · ‎14-01-2022

Replenishment information to GET InventoryItem endpoint is most needed.

RRTT · ‎29-12-2021

soPrepared (qty) is missing from the endpoint. Please expose it as it is also needed to our WMS -system.

RRTT · ‎24-11-2021

For EDI purposes we need Alternate ID and Alternate description exposed to GET PurchaseOrder endpoint - lines segment. These fields are in the GUI. Especially 'Alternate description' is needed, as it is in subject of change from line to line despite of Alternate ID. We have an active EDI project where this is needed and now we are going with a work around that is not so good.

RRTT · ‎13-10-2021

Necessary fields are ARTran.margin, ARTran.cost, ARTran.TranCost and ARtran.UnitCost. Relevant thing here is to GET margin and cost information to external reporting systems. OneStopReporting for example is useless for invoice reporting without these and invoice reporting is the key for most reporting. These fields are not visible in the UI. There is an other Idea to get them visible in the UI too. Anyway these fields are in the database and they can be used with generic inquiries and report designer for example.

Magnus Johnsen · ‎13-10-2021

Hi, As mentioned in the reply below, if this is not currently exposed, please post it in the Ideas part of the forum. Please also include screenshots of where this information is displayed in the UI.