About PPaavola

PPaavola · ‎22-02-2023

Thank you for your reply, In Developer portal, both application scope selections say "This API has no scopes left for a new integration." because everything is already activated. If the APIs use different tokens, that explains why I can't get the scopes to activate in the App Store. I couldn't find this information in the documentation. Any estimate of when the APIs use the same token?

PPaavola · ‎21-02-2023

Hello, I have problem to activate new scopes for our application. I made changes to our registered app in the developer portal. We had the SalerOrder API integration already added, I added the integration for the ERP Service API. After the new integration was approved, I tried to make changes to the app's scope in the App store. The App store only accepts the scopes of the SalesOrder API as active, if I try to activate the scopes of the ERP Service API, an error message appears. (ERROR_INVALID_SCOPE) What could be causing this?

PPaavola · ‎27-10-2021

Sopimuslaskututus toiminnosta puuttuu tietokentät aikajaksosta jota lasku koskee. Koska laskutamme palvelua kuukausi, tai kvartaali kerrallaan, pitäisi laskun perusteena oleva aikajakso ilmoittaa laskulla. Tällä hetkellä, tätä tietoa ei pysty lisäämään laskun tekstiin tai laskun riveille. Kyseiset tiedot jakson alku- ja loppupäivämääristä pitäisi saada joko tietokenttänä laskun otsikkoon/riveille tai parametreina.

PPaavola · ‎05-02-2021

What timezone is Visma DB using? I found that lastModifiedDateTime field in Customer and Inventory endpoints are using UTC+1 time. Is this correct and also is it static, no summertime etc?

Re: Problem with scopes in Visma App Store

Problem with scopes in Visma App Store

Sopimuslaskutukseen kentät aikajaksosta jota lasku...

Time zone and lastModifiedDateTime

Useful pages

About Visma

Contact us

Follow us