Hi   we still have no good solution for that. Therefore we have to go back to sending one by one record for update. We also have to send one by one for insert there we need the return values for each record since we can't find a proper way to reference the answers to the requests. For inserts where we don't need the suggested values from BNxt we will keep sending the requests collected.   Florian ... View more

Yes! That seems to work now, thank you!   ... View more

Sorry it's not 100% confirmed here that the GraphQL has not changed since yesterday. Not sure that it is related to the upgrade.  But following more simple example does not work either:   mutation {   useCompany(no: 3542724) {   associate_create(values: [{associateNo: null, name: "tommy1"}])   {     affectedRows     items {       associateNo, name, shortName     }    }   } }     Is something wrong with our GraphQL here? "errors": [         {             "message": "A record with the same primary key already exists.",             "path": [                 "useCompany",                 "associate_create",                 "values/0"             ],             "extensions": {                 "data": {                     "status": 3                 }             }         }     ], Florian ... View more

I tested this now and it still runs into a timeout       ... View more

Thank you, that was exactly what we wanted. I see, we used the wrong joining path - sorry ... View more

Hi Marius,   yes, but do you know what the meanings of the codes are? Which can we except and what does the codes say us?   Florian ... View more

Thank you for the info. I can talk with the developer that this will be available on Friday and he can start to implement that. ... View more

Any idea about a timeline? if this takes some time to be resolved, we have to change our implementation in the meanwhile ... View more

Is there any progress, or any new information?   ... View more

Yes, of course, that's also possible. Thank you. But if this could be fixed maybe others won't spent time on finding solutions around the problem 🙂 ... View more

And: no stress, I get solved this by checking the number of rows in the result instead, but the hasNextPage is useless ... View more

Fantastic - you are right. Switching the App-Serviceplans fixed the problem. Thank you for helping! ... View more

Hi, thanks for this fantastic description. I restarted the app-services first, but that did not help much. The error situation is a bit weird - now our UI is showing the right data but this curl failed:      I will try to update the app-serviceplan.   Florian   ... View more

We still have a lot of errors here. I tried to restart the app but that did not help much. Now I often get the error:   Unable to connect to the remote server ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 91.123.56.208:443     ... View more

Is this related to Azure? I don't get these messages in debug and we have also other integrations which are running as services which don't seem to have the same problem....     ... View more

The same here, I have a lot of this SocketException errors here. ... View more

Here another problem with the Insert:   The documentation says that the affectedRows property gives the number of rows which are succesfully inserted.  It's also documented that the items returns all successfully imported rows:   When we try to import 20 customers we get the following answer: { "errors": [ { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/0" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/0" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/1" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/1" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/2" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/2" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/3" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/3" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/4" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/4" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/5" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/5" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/6" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/6" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/7" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/7" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/8" ], "extensions": { "data": { "status": 0 } } }, { "message": "Error: The value is already in use.", "path": [ "useCompany", "associate_create", "values/8" ], "extensions": { "data": { "status": 0 } } } ], "data": { "useCompany": { "associate_create": { "affectedRows": 20, "items": [ { "externalId": "", "customerNo": 0, "name": "Arne Bergfjord" }, { "externalId": "", "customerNo": 0, "name": "Milaim Imeri" }, { "externalId": "", "customerNo": 0, "name": "Leif E. Tømmervåg" }, { "externalId": "", "customerNo": 0, "name": "Supaluck Antarit" }, { "externalId": "", "customerNo": 0, "name": "Jan Anders Hansen-Zahl" }, { "externalId": "", "customerNo": 0, "name": "Knut Kristen Kuløy Kjenstad" }, { "externalId": "", "customerNo": 0, "name": "Alf Rune Totland" }, { "externalId": "", "customerNo": 0, "name": "Nils Harald Østevold" }, { "externalId": "", "customerNo": 0, "name": "Kjell Arne Tokheim" }, { "externalId": "1235", "customerNo": 7001235, "name": "Svein-Ivar Holm" }, { "externalId": "1243", "customerNo": 7001243, "name": "Asbjørn Lochert" }, { "externalId": "2995", "customerNo": 7002995, "name": "Geir Skarstein" }, { "externalId": "740328", "customerNo": 7740328, "name": "Evelyn Olafsen" }, { "externalId": "1289", "customerNo": 7001289, "name": "Sverre Jørgensen" }, { "externalId": "650024", "customerNo": 7650024, "name": "Bjørn Mo" }, { "externalId": "", "customerNo": 0, "name": "HR Danmark" }, { "externalId": "460011", "customerNo": 7460011, "name": "Ola Sukka" }, { "externalId": "460021", "customerNo": 7460021, "name": "Kristian Reitan" }, { "externalId": "", "customerNo": 0, "name": "HR Sogn" }, { "externalId": "", "customerNo": 0, "name": "HR Vestfold" } ] } } }, "extensions": { "vbnxt-trace-id": "0000000000000000a38b590571dc5a3a" } }    20 affected Rows and 20 Items but a bunch of error-messages (because the customers already exists).   Would we always get all rows back (also the failed ones) or is this just on the associate table or is this a bug?   Florian   ... View more

Hi Ole,   okay - one thing is that this is not working, but why do you think the errorhandling would work better than in my solution? What would the result be?   Florian ... View more

Thank you for your info. I think this can get a bit trouble especially when one customer behavior affects the other customer because they are running on the same client-ID. And I guess that was not the meaning from Visma to create client-IDs per customer?   ... View more

ok, since there is no better suggestion we are going to fetch all openCustomerTransactions with restamount<>0 and summarize it on our side. Just not sure how many transactions we will have on each run. ... View more

That was obviously not so easy? We could start with looping first, but hope that we don't hit any quota limits therefore.  ... View more

From chatGPT: CSV (Comma-Separated Values): CSV is a simple and widely supported file format that stores tabular data. It is human-readable and can be easily imported into various applications like spreadsheets and databases. However, CSV files can be large and may not be the most efficient option for very large datasets. JSON (JavaScript Object Notation): JSON is a lightweight and flexible format for representing structured data. It is commonly used for web APIs and data interchange. JSON files are human-readable, widely supported, and can handle complex nested data structures. However, they can also be large and may not be the most space-efficient format. Parquet: Parquet is a columnar storage file format designed for big data processing frameworks like Apache Hadoop and Apache Spark. It offers efficient compression and encoding, which can significantly reduce the file size and improve query performance, especially for analytics workloads. Parquet files are optimized for column-wise data access and are suitable for large datasets. Avro: Avro is a compact, efficient, and self-describing binary file format developed by Apache. It supports schema evolution, allowing you to add, remove, or modify fields without breaking compatibility with existing data. Avro files are suitable for large datasets and are commonly used in big data processing pipelines. HDF5 (Hierarchical Data Format): HDF5 is a versatile file format designed for storing and organizing large and complex datasets. It supports hierarchical data structures, compression, and efficient chunking for accessing subsets of data. HDF5 files are commonly used in scientific and numerical applications. Apache Arrow: Apache Arrow is an in-memory data format and columnar storage system that aims to provide a common data representation for different programming languages and systems. It is designed for high-performance analytics and can facilitate efficient data exchange between different frameworks and tools.   I'm not sure what the best would be here - but Json I think is both more stable (feks CRLF, CR, special characters and so on) and easier to handle (by JsonConverters) as CSV?   But I'm not sure about this bigdata-problem actually? Did you get many threads here about timeouts when handling many pages? Or is this a question about quota limitation?   Florian      ... View more