Purge locally document and avoid pull replication

[priya.rajagopal]

@spruzzi23

So the question is still there, how can i set a field, replicate that change, and then delete the document(for delete i mean that the user of the smartphone won’t see the document anymore, could be a purge, of a filter in the query),

I believe I answered this part of the question earlier about how to set a field, replicate and then delete .

@priya.rajagopal

You update the document via the app. The Sync function processes the updated document. The sync function should be implemented such that if document has this particular property set, you put it in a “history” channel

Basically, once the document change is replicated and pushed to a different channel as discussed above , you can purge it locally if you’d like. You don’t have to do that though - in the next replication cycle, since document is removed from the channel that the client has subscribed to , you will see it come down with a special _removed flag that you can use as an indication that this document is not to be used by your client.

As for this part of your question
even if there is no connection?

Well- if you are offline, you cannot replicate the change . So you can’t purge the document locally since the the changed document isn’t up on the server.

I would think that you should implement app-layer logic to handle the case- basically disallow usage of the document locally if the flag is set.