on 2024 Oct 08 4:00 PM
Hello experts!
I'm facing a problem while the app is trying to retrieve the data and creating the offline data store. This is happening because I have one entity which has 19k registers. To get a better understand, I forced the service to provide a TOP=1000 registers and it worked very well. That's why I'm pretty confident the problem is timeout, not the odata service.
Now I have to solve the sync problem with all of those 19k registers. First, I thought SAP MDK had a timeout sync but I coudn't find it inside the services, bundle or actions.
Second, I thought SAP MDK does pagination while retrieving the data. So I traced the OData query SAP MDK did, but I didn't see any query options or params like $filter, $top, $skip. So I'm assuming is always a fullsync in this scenario.
Someone can help me to understand if I'm right in these analysis and what can I do to increase the timeout sync in SAP MDK?
I have a delta sync logic, but in this case is the first sync, a full sync to create the offline data store.
When MDK is binding to entity sets it will use data paging by default. The default is 50 records at a time. However, if you are referring to offline initialization then the MDK paging does not apply. For offline initialization, the request will be based on the defining request data and typically the odata server will handles the paging of the result set back via server side paging.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
62 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.