@bowesmana Thanks for the reply, although when i do try the new query, as per the attached screenshot, this is what i'll get now : When i put in 1404 Bay street, I will get this as a return : CI_Number Equipment Location_within_building Price Street expr 121 TV stand first floor $29.99 1404 Bay street 1404|Bay|street 223 Wireless headset second floor $39.99 1404 Bay street 1404|Bay|street 3334 Laptop second floor $999.99 29th Bay Pl 1404|Bay|street 5552 Wireless Microphone first floor $9.99 404 Bay Street 1404|Bay|street While using this query : | inputlookup stuff.csv
| eval expr=replace("$item$"," ","|")
| where (match(Equipment,expr) OR match(Location_within_building,expr) OR match(Street,expr) OR match(Price,expr) OR match(CI_Number,expr)) a new column is created and I will get everything back as a return now.... Seems like this inserts a new field ( for whatever I've typed in be it 1404 Bay Street or 1404 Bay ) , and also when using wildcards such as * , it will not return anything back either. This is the raw xml : <form>
<label>Where are the items located within the city</label>
<description>Location of office equipment</description>
<fieldset submitButton="true">
<input type="text" token="item">
<label>Input here:</label>
<default>*</default>
</input>
</fieldset>
<row>
<panel>
<title>Where's the equipment?</title>
<table>
<title>Equipment location</title>
<search>
<query>| inputlookup stuff.csv
| eval expr=replace("$item$"," ","|")
| where (match(Equipment,expr) OR match(Location_within_building,expr) OR match(Street,expr) OR match(Price,expr) OR match(CI_Number,expr))</query>
<earliest>$earliest$</earliest>
<latest>$latest$</latest>
</search>
<option name="count">10</option>
<option name="drilldown">none</option>
<option name="refresh.display">progressbar</option>
</table>
</panel>
</row>
</form> Perhaps white spaces in an input box for a dashboard ...just like when using white spaces in a field for an eval command , isn't a feasible option for dashboards?
... View more