Not sure where we're going wrong here. First off the app:     oidc-redirect works as expected, scopes included is 'profile email openid roles tenants'. Retrieving a token returns the data: { "id_token": "<token value>", "access_token": "<token value>", "expires_in": 3600, "token_type": "Bearer", "scope": "profile email openid roles tenants" } Looks fine. But then retrieving https://connect.visma.com/connect/userinfo returns: { "sub": "<guid>", "email": "<my e-mail>", "email_verified": true, "locale": "nb-NO", "name": "<my name>", "given_name": "<my name>", "family_name": "<my name>", "created_at": 1623067455, "updated_at": 1725350746, "picture": "<url>", "roles": [], "tenants": [] }   Feels like i've tried every combination of scope and settings in dev-portal, but nothing. I read in another thread: API access If your app only uses openid, email and profile the access token cannot be used for calling ERP API. When using the tenants scope together with the scopes of the API your app can obtain tenant information from the /connect/userinfo endpoint. The response will contain an array of tenants where the user has access to.   So I tried adding scopes like vismanet_erp_interactive_api:read, but the only difference seems to be that we get tenant selected: { "sub": "<guid>", "email": "<my e-mail>", "email_verified": true, "locale": "nb-NO", "name": "<my name>", "given_name": "<my name>", "family_name": "<my name>", "created_at": 1623067455, "updated_at": 1725350746, "picture": "<url>", "roles": [], "built_in_roles": [], "tenant_id": "<selected tenant>", "tenant_external_id": "<vni id>", "tenant_owner_client_id": "odp", "tenants": [], "features": [] }   There's not many posts talking about this so obviously I'm doing something wrong. But what? Any ideas? ... View more

  Endpoint `controller/api/v1/customerCreditNoteWriteOff` indicates this is available, but is not returned. In Financials UI this Address exists for all types under "Invoices and Memos", but the API does not return it for specifically Credit WOs.     ... View more

Haven't seen any big posters announcing EOL, last official thing (not a forum post) i saw was the statement the 18th.   We're still getting these intermittent 400s with Branch-stuff, like others have already reported: {"message":"Error: An error in processing of field Branch value 1 Error: Branch '1 ' cannot be found in the system."} Most of our stuff is pretty inactive during the holidays, but we have some real-time stuff which is constantly showing "reds". Switching them back to VNI removes all of these errors   So what I'm wondering is what's gonna happen tomorrow? Is it still so that everything VNI will break? I'm kind of nervous about everything coming online ... View more

  When using the scope vismanet_erp_service_api:create and posting to integration.visma.net the "UserID" is picked up correctly and displays apiclient_isv_etcetc, but not using scope visma.net.erp.salesorder:write to salesorder.visma.net   Is there anything we can do to link the two together? ... View more

Hi all   I'm wondering how to post SBWOs to the API. Tried with various payloads, but haven't gotten it to work.   Intended result: SBWO with Code 15 against an CustomerInvoice   payload: { "type": { "value": "SmallBalanceWo" }, "applicationDate": { "value": "2022-10-24T11:49:39.5783663+00:00" }, "customer": { "value": "08809204" }, "paymentAmount": { "value": 3000 }, "invoiceText": { "value": "SBWO Test" }, "paymentLines": [ { "balanceWriteOff": {"value": 3000 }, "writeOffReasonCode": {"value": "15" }, "operation": "Insert", "documentType": {"value": "Invoice" }, "refNbr": {"value": "000156920" }, "amountPaid": {"value": 3000 } } ] }  There's a bunch of fields here that may not be necessary. I've tried removing some, but I'm currently stuck on this error:   Error creating payment Value cannot be null.\r\nParameter name: format There's no mention of "format" in Swagger. I've tried including it in various places, but no success.   Does anyone have a sample payload that works? ... View more

There is currently no way of obtaining the PaymentDate-field from a CustomerPayment-object via the API.   When we look at the list of CustomerPayments (AR3020PL) we see: When working with Financial, many users consider this field when the Payment has "happened", from VNs point of view. The field is the DocDate that we can also see in the Financial Details-tab (AR302000) for a CustomerPayment: props:   This seems to me to be a fairly important field. For example when reporting Payment-data to a different system we need to know which date the Payment is from, since it affects CustomerBalance. And we cannot rely on/enforce Financials-users to always set the same ApplicationDate, because they will not. ... View more

https://community.visma.com/t5/Forum-in-Developers-Visma-net/Obtaining-DunningLevelInformation/m-p/422696   tldr linked post: The ERP UI displays different information for seemingly the same fields on an CustomerInvoice. Via API we're currently unable to differentiate between Invoices with dunning letter drafts and released ones.   Vismanet swagger doc even says:     The Financial details tab > The dunning info section > Dunning level > The dunning level of the document       We have no strong preference on the specific solution. Possibly an easy one is that API should filter the dunning information like ERP does. ... View more

This here is Invoice A as shown in Invoices and Memos -> Financial Details (AR301000)   And this is Invoice B found in the same place   The same can be seen in Dunning Letter History in ERP where, as expected, we find Invoice B and not Invoice A.   But querying CustomerInvoice for Invoice A via API gives me "dunningLetterDate": "2021-01-26T00:00:00", "dunningLetterLevel": 1, and for Invoice B "dunningLetterDate": "2021-11-04T00:00:00", "dunningLetterLevel": 1,   I don't really understand this result. I've been unable to differentiate between these two via API. Am I missing something obvious? ... View more