Should be fixed in 10.21.0 planed for today ... View more

Jag har också flera kunder som efterfrågar denna funktion! ... View more

Hello, I think this is having the same root cause as https://community.visma.com/t5/Forum-in-Developers-Visma-net/Error-creating-customer-with-restrictions-active/m-p/623816#M4432    We've conveyed this problem to development team as well. We'll keep you informed.  ... View more

Hello, this has now been escalated to the Development team for investigation. We'll keep you informed on any progress.  ... View more

Hi, Please send us an email at developersupport@visma.com with an example of a JSON that fails, the companyID and name. We'll forward this to the development team. For now the only known workaround has been retrying the operation at a later point.  ... View more

I've sent a few examples to developersupport now ... View more

Hi Actually it seams to have been solved now. Its working.   /Anders ... View more

Update: Development team checked the database of this customer and: Restriction groups are inactive now. Restriction by GLaccount shows that accounts 3911 and 3230 are restricted A inverse in 2 groups ("Kb ej noll invert", "Kst ej noll invert"), Restriction by subaccount show that subaccounts 937-999000-00-0000 and 931-999000-00-0000 do not have restrictions. Restriction by subsegment shows that: segmentID 1 with segment value 000 is restricted to group "Kst ej noll invert" and segment value 937 and 931 are not restricted segmentID 2 with segment value 000000 is restricted to group "Kb ej noll invert"and segment value 999000 is not restricted segmentID 3 with segment value 00 is restricted to group "Bolagskod ej noll invert" segmentID 4 with segment value 0000 is not restricted Because Restriction groups are inactive now, when testing the API json POST customer invoice, it works and the system creates the invoice. When activating the groups "Kb ej noll inverta" and "Kst ej noll invert" the Restriction by GL account for accounts 3911 and 3230 get activated and the Restriction by subsegment segmentID 1 with segment value 000 and segmentID 2 with segment value 000000 get activated. When testing the API json POST customer invoice, we get an error "message": "VismaId: 14a2619c-9e1d-47a0-b8e8-8660659e6e99. Error creating document. Error: Kostnadsställe of SubID do not exist." even if the subaccounts 937-999000-00-0000 and 931-999000-00-0000 are not restricted.  This is reproducible on the company database.      ... View more

Hello, you can find additional information about the fix and the background of the case below.    1) https://community.visma.com/t5/Forum-in-Developers-Visma-net/Sales-orders-V3-created-by-id/m-p/584084#M3699 2) POST Sales Order Service API - "createdById" and "lastModifiedById" set with API_Client_ID [Release Notes] - Sales Order Service API 1.0.14.648 ... View more

Based on operation context, timeout can happen, therefore we'd recommend implementing a retry mechanism. If timeouts frequency is increased for the same operation type and data size, please send us the transaction details. (URL - DateTime & ClientID & IppCompanyID)   Thanks. ... View more

Hi, The only payment method that is returned using the supplier endpoint is the one set under the suppliers "payment settings". The supplierLocation endpoint does not return this information either. If this is functionality that you need, we would recommend that you create a post in the "Ideas" part of the forum.  Setting the correct paymentMethod on each location should allow you to not have to specify what payment method you want to use. ... View more

Hello, sorry for the late reply, you can try the configuration explained in https://community.visma.com/t5/Forum-in-Developers-Visma-net/API-returns-400-Postcode-is-invalid/m-p/331215/highlight/true#M632 ... View more

Hi,could you please share your payload with us ? (developersupport@visma.com)  Thanks. ... View more

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

Fantastic - you are right. Switching the App-Serviceplans fixed the problem. Thank you for helping! ... View more

Hi, currently "LandedCost" tab is not exposed via Supplier Invoice Endpoint. If you'd like to get this DTO extended, please create this in the Ideas sction by specifying the request details (what operation, request flow etc) so that this will be reviewed by the development team.  Thanks. ... View more

After this action, you'll get a response like this indicating that the process has started: " {     "actionId": "584e8112-6d12-406c-9b6e-ee442809e1aa",     "actionResult": "InProcess" }" After this, what are you doing? Please send us some more details regarding what is done after the creation of the invoice, up until the release action is called and what steps you take after that together with the companyID to developersupport@visma.com and we'll lift it with the development team.  ... View more

Hi, Have you noticed any changes in the frequency of these messages the last couple of days?   ... View more

The problem is back since about 15 minutes ago... Can you look into it as soon as possible?   ... View more

I cannot, they have already been reverted by the customer. This is no new error, this error was quite common serveral years ago when visma net was less stable. ... View more

Hello,    please create an "idea" for exposing those fields, including a print screen from the module highlighting the fields/operations in detail. Thanks. ... View more

Hej,    Vad händer om en leverantören råkar skicka en pappaerfaktura till gamla adressen efter de 60 dagarna ni vidaresänder fakturorna?   ... View more