4 weeks ago
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.
Yes, I'm referring to the offline initialization.
Is there a way to increase the timeout?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
70 | |
9 | |
8 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.