Filter your events by putting search criteria in the URL 

(Server-Powered mode only)

by following your URL with a query string, you’re able to further filter your calendar by a specific field

  • Use field=request structure. You can use as many field combinations as you want – separate them by an ampersand (&).
    • &field1=request1&field2=request2&field3=request3
    • &representative=john – limits your display to those records where “john” is in the field called “representative”
  • You can create an “or” style filter to find records matching one of several values.
    • (new for version 3.3) Using a “|” (pipe) between values, for example:
      • &rep=ken|lauren – limits your display to those records where  field 1 is EITHER ken or lauren.
      • This is the preferred method starting with v3.3, because it’s easier to read, and keeps the URL shorter.
    • Alternatively, you do this by putting square brackets after the field. For example,
      • &rep[]=ken&rep[]=lauren – limits your display to those records where  field 1 is EITHER ken or lauren.
  • You must leave “?calendar=xx” in the url (where xx is the id of the calendar)
  • The field you’re filtering on must not include a space or period. You may want to create a calculation field if this is a problem.
  • Field names are case-sensitive. Values are not.
  • The field(s) you’re filtering by must appear on the layout you defined in the Data Source.
  • Some words cannot be used as field names, such as “Calendar” and “JS”, which are used internally.

Complete list of URL parameters that can't be used for filtering

The following is a list of query parameters used by soSIMPLE calendar. These reserved words cannot be used as field names to filter event records using the URL.

  • queryid
  • feed
  • debug
  • from
  • to
  • js
  • unit
  • script
  • editing
  • calendar
  • template
  • base
  • i
  • timeshift
  • uid
  • v
  • filter_resource
  • find_parameter
  • Any URL interface adjustment parameters