ATD Custom Search

Hi again,

I have set up a custom ATD search, using drop down lists in the common and embedded search sections. These display a list of values for a particular attribute to search by, and by default are empty -> value="".

When searching for an attribute these work fine, however if you wish to leave an attribute blank, eg value="", the value is passed through to SQL as an '*' value, thus providing a search for objects with anything in that field.

This would be fine however not all objects created have these attributes, so the objects without them are never displayed in the search results, as in the databse these do not have that field.

Is there a way to prevent parsing these attributes to SQL or the Query String when they are left empty?

Cheers,

Also on a side note: Why is 'string.replace' not recognised as a method within <ISPECT> tags? Is there substitute to use for this in the API?

Find more posts tagged with

Comments

Christopher_Parratt

Please could you provide some more information

1. Collab version 2. Search type ie: (OTCS/IDOL/SOLR) and version

Eddy_Hutchins

Thanks Chris.

I am running Collab v8.0.2, OTCS v1.1

Christopher_Parratt

Hi Eddy,

Please confirm, have you tried to alter the search template(s) to have the option to manually disable input fields unwanted for search. Please let us know if that works?

Thanks

-Chris

Eddy_Hutchins

Hi Chris,

At the moment I am using the following code within the validateAll() method.

var p6 = document.getElementById("P6");
var p7 = document.getElementById("P7");
var f6 = document.getElementById("F6");
var f7 = document.getElementById("F7");
if(p6.value == "")
{
p6.disabled = true;
f6.disabled = true;
}
if(p7.value == "")
{
f7.disabled = true;
p7.disabled = true;
}

This seems to work when submitting from the embedded form which uses the submit button but not for the common toolbar search which uses a link submit. If I replace the link with a submit button it also works from the common toolbar form. I would prefer to keep it as a link for UI reasons.

The other problem is that this only seems to work in ie6 but not in chrome or firefox. Am unsure where exactly to go from here. Thanks for your help,

$:\$

Christopher_Parratt

Another option is to have a script that when a value equals "" it is not part of the search query.

Eddy_Hutchins

The code works in preventing the values being passed to the query string when using the 'submit' button. When the form is submitted it checks whether values have been entered via the javascript validateAll() method and if not diables them. This is working in IE6.

HOWEVER.

This does not work in chrome or firefox, OR when clicking 'show 10 more' 'show 100 more'.

Can you explain how the search forms are set up so that I could move this code to a method which is called EVERY time the search results are refreshed or another alternative? Whether from a form submit button, a javascript submit button or one of the 'show more' buttons.

Also, do you have any clue why this doesn't work in newer browsers?

Thanks for your help,