Dynamic Filters

Dynamic Filters define a query with field variables, enabling more powerful controls.

• Use Dynamic Filters when complex associations are needed for Record Selection Criteria

How it Works

• In a Technology Asset record, display a list of Technicians certified to support or repair the equipment
• For an Inventory Application, add a field to a Part Record that finds only component parts (subcomponents of the Part)
• For a Product or Service Ordering Application, add a field to a Brand Record that limits the lookup to products that belong to the brand family
• In a Candy Manufacturing Application, add a field to a Recipe Record that identifies organic ingredients only

Guidelines for building Dynamic Filters

The format of a Dynamic Filter changes, depending on the type of field:

• Lookup
• Other (text, date, other alphanumeric field)

To specify Dynamic filters in the UI, insert a derived field name in the Value field of the Record Selection Criteria builder

• To create a derived field name, include a dollar sign ($) before the internal field name (this identifies the value as a dynamic filter)
• If a Lookup field is chosen, use the $fieldname_name format
• For all other fields, use $fieldname

Where fieldname can be found in Field Name

Examples

• In a Lookup field of Object "Employee", to restrict the Employees available depending on the Location, set filter to {0} in the Location field. If the Location is any other field type, set filter to {1} in the Location field.
• An IT assets object is linked to the Service Techs object, which includes staff members who are responsible for support

• Service Techs have an Area of Responsibility that matches one of the available IT asset Types: "Laptop", "Desktop", or "Server"
• The Service Tech object is defined as follows:

File:Lookupselectorservicetech.gif

• In the IT asset object, the Lookup field to the Service Tech object includes Record Selection Criteria that limits the lookup to Service Techs with Areas of Expertise that match the Asset Type:

File:Lookuprecordselector.gif

• When assigning the asset to a user, a Service Tech is selected, and the list of Service Techs displayed in the Lookup Window shows only the techs with expertise in the required area of technology

User-specific template variables

Record data can be compared to the User object data for the current user. Those criteria have the form:

{field_name} {operator} $loggedInUser.{User_object_field}

For example:

• Owner equals $loggedInUser.id - Records owned by the current user
• Created By equals $loggedInUser.id - Records created by the current user
• Modified By equals $loggedInUser.id - Records modified by the current user
• City equals $loggedInUser.city - Records in the current user's city

Similarly, were you to add a custom hiredate field or birthday field to the User object, you select records that came before or after that date using the less than and greater than operators.

Label	Template Variable	Comment
User Id	$loggedInUser.id
First Name	$loggedInUser.firstname
Last Name	$loggedInUser.lastname
Email	$loggedInUser.email
Primary Team	$loggedInUser.primaryteamname
Primary Team Id	$loggedInUser.primaryteamid
Role Id	$loggedInUser.primaryroleid
Team Ids	$loggedInUser.teamids
Company	$loggedInUser.company
Title	$loggedInUser.title
Time Zone	$loggedInUser.time_zone	User's time zone code. For example:   80 for Pacific/Kiritimati   76 for Pacific/Enderbury   84 for Pacific/Tongatapu
Reports To	$loggedInUser.reports_to
Language	$loggedInUser.language	User's languare code. For example:   en for English
Employee Number	$loggedInUser.employee_number
Street	$loggedInUser.street
City	$loggedInUser.city
State/Province	$loggedInUser.state
Postal/Zip Code	$loggedInUser.zip
Country	$loggedInUser.country
Phone	$loggedInUser.phone
Fax	$loggedInUser.fax
Mobile Phone	$loggedInUser.mobile
All custom fields created on the User Object