Search
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Sign In
My Products
Help
Sign in or create account
to get a personalized navigation.
Sign in or create account
to get a personalized navigation.
User Profile
gerrit_deglee
12
Posts
1
Kudos
0
Solutions
17-11-2021
14:58
Now you are confusing me. The LastModifiedDateTime is in the swagger specification for this endpoint. Just not the condition.
... View more
17-11-2021
14:42
Thanks Yildrim, that seems to have helped! I don't see the LastModifiedDateTimeCondition parameter in Swagger for this endpoint?
... View more
17-11-2021
13:33
Hi Yildrim, If I look at the version number in Swagger, this is now implemented right? We do not see an improvement yet. Thanks, Gerrit
... View more
12-11-2021
14:21
1 Kudo
Hi Bogdan, to be honest we stopped using this particular endpoint, so I have no work around. The issue with the journaltransaction endpoint is only at a particular customer. We do not see this at other customers. Gerrit
... View more
11-11-2021
16:28
Any news on this?
... View more
10-11-2021
19:43
Page 30 does fail in Postman as well (after a very long wait). The first few pages are fast, but they seem to be getting slower and slower, until they time out. I don't think it is always page 30, but as I said, if I try just that page in Postman, it does fail. Thanks
... View more
10-11-2021
14:09
We're having problems with the initial load of journaltransaction for a new customer of ours. We're trying to load period 202101 and it fails on pagenumber 30 https://integration.visma.net/API/controller/api/v2/journaltransaction?pageNumber=30&periodId=202101&lastModifiedDateTime=1900-01-01&releasedBatch=true&pageSize=1000 The error is http 500 internal server error. We try this three times and then give up. We did see timeouts in pages 17, 23, 25 and 27, but retrying resolved those. This is for ippcompany id 3001421. Thanks, Gerrit
... View more
21-09-2021
15:21
I've restarted and see a timeout on page 5 at 14:51:52, but that loads succesfully on second attempt. Page 6 times out at 15:02:22, 15:08:27 and 15:14:37. Our procedure gives up after three failed attempts. Normally we only load modified records since last load, but because we had a mismatch in number of records between the DWH and the reported totalcount we wanted to refresh our DWH. That is when we started seeing the timeouts.
... View more
21-09-2021
12:57
This is for company 1939930. The client_id is cpm4care_auth_prod_a2ost70wv1 The error occurred just now at: 12:22:36.257 and retried at 12:28:41.301 and 12:34:51.337 I don't have a statuscode. I assume it times out on our end after 6 minutes.
... View more
21-09-2021
12:18
We had a difference in number of records in our DWH and those reported in the totalCount of the supplierInvoice endpoint, so we tried a full load. We are experiencing frequent time-out errors on the supplierInvoice endpoint when doing this. The request is in the form: https://integration.visma.net/API/controller/api/v1/supplierInvoice?pageNumber=3&pageSize=1000&LastModifiedDateTime=2021-03-31&LastModifiedDateTimeCondition=> Usually the timeout occurs on page 6 or 7 Is there a problem with the endpoint? Anything we can do to speed this up? I've tried reducing the pageSize to 100, but that does not help a lot. Thanks, Gerrit
... View more
10-02-2021
08:34
HI, we noticed the metadata.totalcount is missing in the customer endpoint since tonight. We use it to verify we have all records.
Thanks,
Gerrit
... View more
Categories:
- Categories:
-
API:Customer
10-11-2020
12:13
Hi, we use the following request to verify we have all expected records in our DWH. Since this morning the JournalTransactionV2 endpoint returns metadata.totalcount of 1 instead of the expected number, causing our validation to fail. https://integration.visma.net/API/controller/api/v2/journaltransaction?pageNumber=1&pageSize=1&periodid=202001&releasedBatch=true If I change the pagesize to 2, I get a totalcount of 2. If I change it to 3, I get two records, one with a totalcount of 113230, the other with totalcount of 1. One query should return the same totalcount in all cases I assume. The 113230 is the number I would expect. Thanks
... View more
Activity Feed for gerrit_deglee
- Posted Re: http 500 error when using journaltransaction endpoint on Forum in Developers Visma.net. 17-11-2021 14:58
- Posted Re: http 500 error when using journaltransaction endpoint on Forum in Developers Visma.net. 17-11-2021 14:42
- Posted Re: http 500 error when using journaltransaction endpoint on Forum in Developers Visma.net. 17-11-2021 13:33
- Got a Kudo for Re: Time-out in supplierInvoice endpoint. 12-11-2021 14:24
- Posted Re: Time-out in supplierInvoice endpoint on Forum in Developers Visma.net. 12-11-2021 14:21
- Posted Re: http 500 error when using journaltransaction endpoint on Forum in Developers Visma.net. 11-11-2021 16:28
- Posted Re: http 500 error when using journaltransaction endpoint on Forum in Developers Visma.net. 10-11-2021 19:43
- Posted http 500 error when using journaltransaction endpoint on Forum in Developers Visma.net. 10-11-2021 14:09
- Posted Re: Time-out in supplierInvoice endpoint on Forum in Developers Visma.net. 21-09-2021 15:21
- Posted Re: Time-out in supplierInvoice endpoint on Forum in Developers Visma.net. 21-09-2021 12:57
- Posted Time-out in supplierInvoice endpoint on Forum in Developers Visma.net. 21-09-2021 12:18
- Posted metadata totalcount missing in Customer endpoint on Forum in Developers Visma.net. 10-02-2021 08:34
- Posted Incorrect metadata totalcount in JournalTransactionV2 since this morning on Forum in Developers Visma.net. 10-11-2020 12:13
Useful pages
Contact us
Copyright © 2022 Visma.com. All rights reserved.
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America