User Profile
Magnus Johnsen
1050
Posts
112
Kudos
172
Solutions
10-08-2021
12:40
Release Notes
Documentation
Deprecated PUT, POST and GET v1/currency/ExchangeRates methods
The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on November 16th 2021. Start using the new methods under v2/currencyRate.
New Parameters/Flags to improve the performance of the General Ledger Transactions Endpoint
Parameters to avoid additional data for Account, Branch and beginning and ending balance in the query has been added to improve the performance for this API ExpandAccountInfo: By default, if no value is provided, True and each transaction returned will include extended information about the account. If False, the account information will include only Number, Description, Type and GlConsolAccountCD. ExpandBranchInfo: By default, if no value is provided, True and each transaction returned will include extended information about Branch (number and name). If False, the branch information will include only the branch number. IncludeTransactionBalance By default, if no value is provided, True and each transaction returned will include its balance. If False, the transactions returned will not include their balances (fields BegBalance, EndingBalance, CurrBegBalance, CurrEndingBalance)
Pagination and filtering issues introduced with performance improvement of GET salesorderbasic endpoint in 8.59
In 8.59 we introduced a performance optimization for GET salesorderbasic endpoint which resulted in some issues with pagination and filtering. This has now been fixed, and we have reactivated the optimization again.
GET SalesOrder endpoint returns an internal project ID in project
Earlier, the GET SalesOrder endpoint returned and internal ID in project. This has now been fixed by adding property ProjectCD containing the visible ID for the project. Enabling integrations to utilize this value.
A new easier method to use the Currency endpoint
The currency endpoints have been changed and a new version 2 added for Exchange rate and Rate type.
GET api/v1/currency and GET /api/v1/currency/{curyId} has been extended with new columns "symbol": "string", "isBaseCurrency": true, - is only returned on the currency that is the base currency. "decimalPrecision": 0, "isUsedForAccounting": true New version 2 of Currency rates GET /api/v2/currencyrate with parameter fromDate toDate fromCurrency toCurrency rateType Returning "id": 0, "fromCurrencyId": "string", "toCurrencyId": "string", "rateType": "string", "rate": 0, "effectiveDate": "2021-08-04T00:00:00", "multDiv": "string", "rateReciprocal": 0 For POST, the CurrencyRateID is removed as parameter and From and To Currency is part of the request. POST /api/v2/currencyrate "fromCurrencyId": "string" "toCurrencyId": "string" "rateType": "string" "effectiveDate": "2021-08-04" "rate": 0 "multDiv": "Multiply" For PUT, the request only contain Rate and MultiDiv to avoid updating an existing Rate for a other currency/ratetype by mistake. PUT /api/v2/currencyrate with parameter currencyRateId "rate": 0 "multDiv": "Multiply" New API's for Currency rate type: GET /api/v2/currencyratetype "id": "string", "description": "string", "daysEffective": 0 POST /api/v2/currencyratetype "id": "string" "description": "string" "daysEffective": 0
... View more
Categories:
09-08-2021
15:51
Thank you for confirming that the issue has been resolved.
... View more
09-08-2021
15:14
1 Kudo
Hi,
We can confirm that the "projectTask" field object is omitted and have reported this to the development team for both purchaseOrder and purchaseReceipt.
Thank you!
... View more
06-08-2021
12:39
Hello, according to information we've received,
" As this "Print" only working in the VismaXML format which will be replaced soon with PEPPOL BIS 3 and this function no longer will be supported in the PEPPOL when PEPPOL BIS 3 is implemented, therefore, case has not been taken into development plan. "
... View more
27-07-2021
15:56
Postmortem: https://status.visma.com/incidents/vghs93jnrqvd
... View more
19-07-2021
14:56
Thank you Magnus for the answer.
... View more
09-07-2021
10:52
Hi,
We'll have a look at this and get back to you.
... View more
23-06-2021
21:34
I need all the information I can get 🙂 As I understand it "/controller/api/v2/journaltransaction" does somewhat the same thing as @WaBnd and @WaVo. I'm in the process of mapping all the fields between the file I have and the journaltransaction endpoint, but it seems like there are a lot more fields in the file than available in the endpoint. I also suspect that this is not the Visma.net way of doing things, so I'm a little bit lost if it's even doable or the work process needs to change.
... View more
17-06-2021
11:39
1 Kudo
Hi,
Currently there is no parameter exposed to filter by status via the SupplierInvoice endpoint.
There is a case for this in the backlog, you can vote for it here:
Expose Supplier Invoice Document "Status" as a filtering parameter via "SupplierInvoice" Endpoint
... View more
17-06-2021
08:20
Hi,
The case is currently in the backlog.
As of right now there is no ETA we can share for when this will be implemented.
If it's a functionality you need changed, we would recommend that you vote for the Idea and contact your partner service.
Thank you.
... View more
17-06-2021
08:17
Easy oversight, I did not notice that you had written the field that way either.
Glad that it works.
... View more
16-06-2021
10:18
This field is currently not exposed to via the API.
If you need this functionality, please post it in the "Ideas" part of the forum.
This allows other users to vote for your suggestion and in turn influences the assessment/implementation process from the development team.
Thank you.
... View more
11-06-2021
11:28
Hi,
As of now, it is not possible to change the sort order, it is returning the dataset in ascending order.
I suppose what you could do is to
Get the transactions that have been modified since your last request with a page size of 1
Check the totalCount in the metaData returned
If the count is one, this is the only document that has changed and nothing else would be needed
If it is higher than one, request the last page and use that date
Then again, if the only need that you have is to check if they have had any new transactions since the last time you checked, you could always just check the endpoint everyday and update the datetime parameter, if the returned set is not empty they have posted to the journal.
... View more
10-06-2021
15:48
Hi,
The invoice printed should be printed as per the settings on the customer(ScreenId=AR303000):
We were not able to reproduce this with the standard dutch template, neither via the API or the UI, in both cases the date was printed as d/m/yyyy:
Could you please have a look at this setting and send us screenshots of the invoice printed in the UI and via the API?
If you do not want to post it here, you can send it in an email to developersupport@visma.com.
Thank you.
... View more
10-06-2021
14:26
We can confirm even sending the minimum fields result in the same error:
{
"landedCost": [
{
"operation": "Insert",
"landedCostCode": {
"value": "TESTCODE"
},
"supplierID": {
"value": "50000"
},
"purchaseInvoiceNbr": {
"value": "SupRef"
},
"locationId": {
"value": "Main"
},
"description": {
"value": "Test"
}
}
]
}
It has been reported to the development team.
Thank you.
... View more
09-06-2021
15:11
Please also have a look at the following article, might be helpful for configuration of the webhooks. Visma.net ERP API Webhooks Setup API & ERP UI (Event - Subscription - Notification)
... View more
09-06-2021
11:38
Hi,
We have asked the development team for another update on this case.
We recommend that you lift this with your partner service as well.
... View more
27-05-2021
15:34
Thanks for all answers. The invoices i want is the ones that are been clicked "Released" in the topmenu of the supplierinvoice detail view. Preferably so you can go by date to get it to.
... View more
21-05-2021
09:06
Hi,
There are cases for this in the current backlog:
Create/Update CustomerSalesPrice
API, Vendor Sales Price endpoint
If you need this functionality, we recommend that you go to those Ideas and vote for them.
Thank you.
... View more
20-05-2021
18:10
Thanks for the confirmation 🙂
... View more
18-05-2021
14:55
That sounds like a good idea, if this is an improvement you'd like to see. Please post it in the "Ideas" part of the forum.
... View more
12-05-2021
13:58
Hi Marius,
As this is an improvement and there are currently high priority cases ahead of it in the backlog, there is no current date planned for this.
Here is the Idea's post for the case: Expose "paymentDetails" from Supplier -> Locations
To help with prioritising the case, you can vote for the Idea.
Further progress will be posted in the Idea post.
Thank you.
... View more
12-05-2021
13:55
This is currently in the backlog.
... View more
11-05-2021
13:50
Could you please send us your api client ID and the company ID to developersupport@visma.com
... View more
07-05-2021
13:56
[Release Notes] - Visma.Net API 8.26 - 09.11.2020
... View more
07-05-2021
13:19
This issue has been planned to be fixed in 8.48 version. Visma.net Financials API updates for version 8.48.0 (May 2021)
... View more
06-05-2021
14:36
Indeed, good to hear that it works!
... View more
27-04-2021
11:35
Visma.net Financials API updates for version 8.46.0 (April 2021)
... View more
Activity Feed for Magnus Johnsen
- Posted Version 10.29 - Scheduled downtime maintenance window has been postponed: 10th December on News in Developers Visma.net. 27-11-2024 14:17
- Posted Version 10.28 - Breaking change due to mandatory changes in the SAF-T report: 6th December 2024 on News in Developers Visma.net. 18-11-2024 14:22
- Got a Kudo for Re: Including Attributes when getting multiple Projects. 17-05-2024 09:03
- Tagged [Release Notes] - Visma.Net API 9.80.0 - 06.02.2024 on News in Developers Visma.net. 09-02-2024 08:57
- Posted Re: TaxID '01' cannot be found in the system. on Forum in Developers Visma.net. 18-01-2024 15:18
- Posted Re: HIGH priority Subaccount missing, Error creating journal transaction. Error: TaxID '01' cannot on Forum in Developers Visma.net. 18-01-2024 15:00
- Posted Re: Budget API is not retrieving inactive subaccounts on Forum in Developers Visma.net. 18-01-2024 13:39
- Posted Re: Bad Gateway messages when making calls to the Visma.Net ERP API on Forum in Developers Visma.net. 17-01-2024 09:56
- Posted Sv: Getting customer / supplier invoice document (PDF) on Forum in Developers Visma.net. 15-01-2024 10:25
- Posted Sv: Getting customer / supplier invoice document (PDF) on Forum in Developers Visma.net. 10-01-2024 13:37
- Posted Re: Insert supplier on Forum in Developers Visma.net. 09-01-2024 09:51
- Posted Svar: Insert supplier on Forum in Developers Visma.net. 09-01-2024 09:47
- Posted Re: Insert supplier on Forum in Developers Visma.net. 09-01-2024 09:03
- Posted Re: Bad Gateway 502, in all API calls, AGAIN (!) on Forum in Developers Visma.net. 05-01-2024 12:10
- Posted Re: Bad Gateway messages when making calls to the Visma.Net ERP API on Forum in Developers Visma.net. 04-01-2024 11:16
- Posted Re: Change from test to production on Forum in Developers Visma.net. 03-01-2024 12:23
- Posted Re: VNI-VC January 1st on Forum in Developers Visma.net. 02-01-2024 11:13
- Posted Re: Salesorder API v3 creating orderLines without subaccount on Forum in Developers Visma.net. 29-12-2023 14:25
- Posted Svar: IPPexception 5520 on every call for select customers migrated to new auth flow on Forum in Developers Visma.net. 29-12-2023 14:21
- Posted Re: Service app status pending on Forum in Developers Visma.net. 29-12-2023 10:24