[mapguide-users] MGOS 2.0 search functionality limited?
jonathan.manafi at cctechnol.com
Thu Feb 14 16:16:03 EST 2008
We figured out that the format for the filter string was wrong; there should
not be quotes around the data property. So, 'RACRE' > '$USER_VARIABLE'
should really be RACRE > '$USER_VARIABLE'.
Also, the RACRE property is a string value, instead of a numeric one, so the
' are necessary around the $USER_VARIABLE/concrete value. If it were a
numeric comparison, like RSQFT <> 100000, the ' cannot be used around
J Manafi wrote:
> I've been messing around with the Search widget in MGOS 2.0 rc3 in the
> Sheboygan samples, and it seems that the search functionality doesn't
> change. What I mean is that the initial search was done by acreage, and it
> returned the same results no matter what value you entered. So, I tried
> changing the the search string...first from
> 'RACRE' > '$USER_VARIABLE' to 'RSQFT' > '$USER_VARIABLE'. (with html
> special characters)
> It returned the same results regardless of the number I input. So, instead
> of the $USER_VARIABLE, I tried a set value, like 450000 sq.ft., and it
> returned the same values. I tried changing it to recognize string
> comparisons, like
> 'RNAME' LIKE 'AUTO%' for Autozone in District 1
> and it didn't even return a result, it just said 'NO MATCHES'.
> The only thing I have been able to do with the search is reduce the
> matches from the default, or change the column data printed out.
> Has anyone else had this kind of issue with using the default search
View this message in context: http://www.nabble.com/MGOS-2.0-search-functionality-limited--tp15484119s16610p15489383.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mapguide-users