08-28-2019, 08:58 PM
Hi sltfn,
You can use sync to download a table to your device and make it available locally. This will allow you to perform all the same APIs on the data without having to make cloud calls. Then at the end of the session you can sync the table back up to the cloud and any changes (new records, records deleted, records updated, etc) will be made to the cloud.
cdb_sync(pRecordIDL, pTable, pSource, pAllowDeletes, pDetectCollisions)
You mentioned you would prefer a subset of the table instead of the entire table. To do this, pRecordIDL will be a line delimited list of recordIDs corresponding to the subset of the table you are interested in. Once the table is local, you just need to pass "local" instead of "cloud" to the APIs and no more cloud calls.
Hope this helps. Let me know if you have any questions.
You can use sync to download a table to your device and make it available locally. This will allow you to perform all the same APIs on the data without having to make cloud calls. Then at the end of the session you can sync the table back up to the cloud and any changes (new records, records deleted, records updated, etc) will be made to the cloud.
cdb_sync(pRecordIDL, pTable, pSource, pAllowDeletes, pDetectCollisions)
You mentioned you would prefer a subset of the table instead of the entire table. To do this, pRecordIDL will be a line delimited list of recordIDs corresponding to the subset of the table you are interested in. Once the table is local, you just need to pass "local" instead of "cloud" to the APIs and no more cloud calls.
Hope this helps. Let me know if you have any questions.