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? ... Meer weergeven

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. ... Meer weergeven

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. ... Meer weergeven