Best practice to implement one way (client to server) syncing?

M Mark Bauer 2 years 11 months ago
1 1 0

I am looking for a way to use rhoconnect's sync engine to send data from the client to the server, but then never bring that data back down again in the model's query method.  I have tried using pass through, as well as hard coding a place holder record in the query method, and both of these processes leave orphaned data on the clients, with the object ID that the client generated, as seen in the attached screen shot.  Ideally the placeholder record would stay, and the other record would be removed from the client after syncing. 

Thanks in advance for any ideas,

MAB

Please register or login to post a reply

1 Replies

K Kutir Mobility

Hi Mark,

As you know rhoConnect is designed from our ground for two-way syncing. Wish there is a variable to set one way. :).

Do you think you can use RESTFul API for sending data from Client to Server and then flush it?

Visnupriya R
Kutir Mobility

CONTACT
Can’t find what you’re looking for?