Par ErikW

Oskar Jansson · ‎11-11-2024

Has this problem been resolved, or do your customers still experience IPPExceptions?

Marten Voort · ‎30-09-2024

In the next release (version 10.20) this problem is solved. Let us know if the situation still occurs.

Sandra Anté · ‎06-02-2024

Hi Erik! Can you please specify the workflow that you've used so far so that we can replicate it in our environment? Please also include JSON for the transfer order if possible. Otherwise include screenshots from sales order (ScreenID=SO301000). Thank you! Kind regards Sandra

Yıldırım · ‎17-01-2024

Hi Erik, I can confirm the issue. This has been escalated as a bug and will be reviewed. 1) Create a KIT Item with multiple Warehouse (Warehouse Details: 1-Default, 2 Optional) 2) POST KIT Assembly with that KIT Item specifying the non-default warehouse in the payload. { "type": "P", "hold": { "value": false }, "date": { "value": "2024-01-17" }, "itemId": { "value": "KIT01" }, "revision": { "value": "1" }, "description": { "value": "string" }, "warehouse": { "value": "2" }, "location": { "value": "1" }, "quantity": { "value": 1 } } Output: 3) Check "Inventory Transaction History", it'll show the movement based on warehouse "1" even though we've specified Warehouse"2" 4) Create KIT Assembly manually in the ERP UI with Warehouse "2" 5) Check "Inventory Transaction History" again. Now, it shows the movement correctly, Warehouse "2"

ErikW · ‎16-01-2024

This would highly benefit us and our customers as well. In particular we have one larger customer that is more or less dependent on this functionality going forwards. Would appreciate some form of feedback if this is at all feasible and if so what sort of time frame would this entail?

adrianm · ‎12-10-2023

No, it is not possible. There is a request for it that has been open for 2 years. It was possible (sort of) up until February this year. You could create TR order but not set the destination warehouse. We used different customers instead and had a job updating the warehouse, but Visma pulled the plug on that workaround.

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

Hello, we're unable to reproduce the issue. Regardless of the pageNumber, the whole data should be filtered based on the query param. Could you please send us your company-ID & API Client details with DB restore approval ? <developersupport@visma.com>

Magnus Johnsen · ‎15-09-2023

That would help, please send it to DeveloperSupport@visma.com. Thank you.

ErikW · ‎14-08-2023

Hi I have a customer that would like to be able to set the field "kundreferens" (Customer Reference) via the API when we create a customer invoice. Please see the included picture for the field I am referring to. Is this possible? The field seems to be a free text input field in the UI as far as I can tell. Regards, Erik

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

Hello Erik, unfortunately this connection described in the UI is not available via the API. I'd recommend you creating an Idea by describing the process steps and corresponding module to be reviewed for implementation to the API.

ErikW · ‎21-02-2023

Hi, Just wondering if you could give me an indication as to when this might be resolved?

Magnus Johnsen · ‎11-08-2022

For get specific project, the attribute field is always returned if it has any attributes set. For the get all endpoint it is documented:

Magnus Johnsen · ‎17-05-2022

Hi, There are occasionally some issue related to the cache not being updated, however there is no documentation regarding this and it is not always a problem.

Re: Recurring 5520 errors when getting supplier in...

Re: Error "tstamp cannot be empty" when doing a PU...

Svar: Transfer orders purchase receipt 400 error

Re: Kitassembly does not respect chosen Warehouse

Svar: Landed Cost functionality for POST SupplierI...

Re: Creating Transfer orders

Re: Setting financialPeriod for CustomerInvoice Ge...

Re: Error when trying to retrieve customerCreditNo...

Set/overwrite customer reference on customer invoi...

Re: Associate deferred revenue transactions with i...

Re: /controller/api/v1/GeneralLedgerTransactions s...

Re: Including Attributes when getting multiple Pro...

Re: JournalTransaction V2 problem with new company

Noderīgas saites

Mūsu risinājumi

Seko mums