• You can set a Filter on a field and hereby only have the records corresponding to the specified Filter value transferred.
  • When setting the filter on the destination, you need to take extra care, as this will limit the records that RapidiOnline can see when it does a lookup in the destination to see if a record exists or not - i.e. if Rapidi should ADD the record or UPDATE an existing record. Setting a filter on the Destination will hence make Rapidi believe that certain records do not exist in the Destination and so it will ADD them to the Destination.
  • One exception to the above is, when "Delete" is selected. Rapidi will then read from the Destination and make a lookup in the Source to see if a record still exists (and hence if it should delete the record or not). When using "Delete", a filter on the Destination will limit records that Rapidi reads in the Destination and thereby what records it potentially deletes.
  • How to set the Filters depends on the DataSource that the filter is used on (for Source Filters, the Source DataSource, and for Destination Filters, the Destination DataSource).
  • In general, you will select the field name to filter on in "Field" (the left side) and set either just the filter value or write an SQL-like filter in the "Filter" (on the right side). What you write on the right side, depends on the DataSource.
  • See Filters Source delimitations for more information on how to specify filters.



Here you specify which field the Filter should be set on.



Here you specify the Filter value.



  1. Getting Started
  2. Documentation
  3. HowTo
  4. Standard Integrations


Service News can now be found on our Product Updates Blog 


Remember to Subscribe to our Product Updates Blog to receive updates and product news.





Wheeled by Wagn v. 1.9.1