It makes sense. I checked the doceumentation for contentObjectFind like you
mentioned and it had a decent amount of information on the stFilter
structure.
I decided that I need to add to the stFilter struct the following code:
stFilter.stSearchable = STRUCTNEW();
stFilter.stSearchable.myProperty = "1";
However, I'm still getting back all my objects of that type with any value
for myProperty. I'm appending to the stFilter struct in
selectInvocations.cfm.
I'm editing the correct piece of code aren't I?
-
Nate Smith,
Lead Developer
[EMAIL PROTECTED]
www.doceus.com
---------------------------------------------------------------
-----Original Message-----
From: Raymond Camden [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 16, 2001 10:37 AM
To: Spectra-Talk
Subject: RE: Filtering cfa_objectFinder
Think of stFilters as a dynamic way to pass stuff to coFind. Basically,
everything in stFilters gets translated to the Attributes scope. So, you can
do things like dynamically passing date/property/etc filters without having
to create multiple CFIF branches and multiple different calls to the tag.
So, what can you filter on? Just look at the attributes of coFind, all the
'normal' filters like dtCreatedAfter. You can filter by those _and_ by the
properties of the type you are searching on.
Does that make sense?
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
