Hi Community!
We’re just in the process of implementing real-time sync and with our implementation, I have got a few asks that I want to share to be evaluated by the product team.
- Decouple RTS and Scheduled filters
Realistically, we may want RTS to only apply to certain records that may not be the same exact logic as scheduled fields.
In my case, I want the scheduled sync to create contacts (those that don’t exist in GS / don’t have a GSID), but I do NOT want RTS to consider calls for all contacts (so I’d like to have a filter that prevents it from considering contacts that do not have a GSID in SFDC).
To prevent RTS from considering updates to all contacts, I have to revert to creating new contacts with a rule, and limiting the sync job to scheduled updates (RTS and scheduled) to implement the filters that I need, if I want to limit the waste on the API call front.
- Set conditions on update events to be considered
I know that this is a SFDC limitation, but maybe it can be explored in partnership with them: we should be able to apply a filter on the update events that we want to capture (down to the field level). There’s no point for anyone wasting calls on fields that aren’t part of RTS.
- Allow RTS filters on lookup fields
Currently, it’s not possible to enable RTS filters on derived mapping (lookup fields), which is forcing us to write some information that lives in the lookup object in the mapped object so we are able to filter on these values. I’m thinking about Account Type - I don’t want to sync updates on contacts whose account type is NOT customer. Can’t do that for RTS - only for scheduled, which leads to more API call wastage.
I know not everything is in your hands and it depends on Salesforce, but I’m quite hopeful that at least decoupling RTS and Scheduled filters should be doable and it would make a difference.
Thanks!