Thanks for writing and for the provided feedback.
The idea behind the SynchronizationFilter
is to limit the items being part of the synchronization context that works on a given Everlive table. Setting a SynchronizationFilter
will limit the synchronized items to those who pass this filter - only the filtered items will be stored locally and synchronized with the cloud. With the current state of implementation, if you want to add a new item to the context it should pass the condition that the SynchronizationFilter
So is it your scenario related to browsing through records that exist, yet are not part of the current SynchronizationContext
with a potential possibility to add them to the context?
Currently you could use the Everlive
SDK to search for items, update the properties of those you want to have in the SynchronizationContext
and call SynchronizeAsync
to make sure they are downloaded.
Have a suggestion or face a problem - you can use the Ideas & Feedback portal
to submit ideas, feedback and vote for them.