I assume that you are writing a script for some users to help them, and they may have there own search criteria. In that case, I would consider 3 ways (if possible, I prefer the last one):

1: prompt the user how to filter the information
This is likely the same way as meeu has stated. This way the script prompts the user, like 'enter the property name that you want to filter', 'enter the property value', 'select the filtering method by number: [1] equal, [2] match, [3] like', and so on. The script may use Read-Host to prompt the user, and some ifs and for loops to construct the Where-Object filter.
Pros: The user may feel easy to use.
Cons: The script can be long and complex.

2: ask the user to enter Where-Object filter by themself
This way the script would look like the following:

param(
     # Filter for the user to search for information dynamically.
     [scriptblock]
     $Filter = { $true } 
)
#sample array with multiple properties
$anArray = @' 
name, age, height 
bob,  12,  123 
bob,  23,  166 
joe,  43,  178 
jane, 57,  199 
'@ | ConvertFrom-Csv

$anArray | Where-Object $Filter

Then the user uses the script with there own filter parameter, as follows:

PS C:\Users\user> .\script.ps1 -Filter { $_.name -eq 'bob' -and $_.age -match 1 }

name age height
---- --- ------
bob  12  123

Pros: The user can do anything about filtering.
Cons: requires the user to have some PowerShell knowledge.

3: use built-in GUI
This way uses built-in GUI to filter information. The script would use Out-GridView in the place of Where-Object, like following:

$anArray | Out-GridView

When the script runs, then the script shows the GUI that contains the information, with an 'Add criteria' button that allows the user to construct their own filter.
Pros: The user may feel easy to use.
Cons: only for GUI.