[Lasso 8.6]

I've come across a couple of Lasso issues with newer versions of
FIleMaker Server. It affects at least FM 13 but could also affect
FMS12, I haven't tested with that yet.

When Lasso sends a request to FM WPE, it defautls to sending -lop=and
even if a logical operator isn't specified in the inline.
If a logical operator is specified in the inline, there will be more
than one -lop in the request sent to FMS since Lasso still adds the
default -lop=and. There parameters are normally overridden by
parameters that follow, but not with FMS13. This is not accepted by
FMS 13 (haven't tested with 12).

Example request (captured with action_statement inside the inline
block, line breaks added for readability).
/fmi/xml/FMPXMLRESULT.xml?-db=mydatabase
&-lay=Kunder&-lop=and
&fakt_foretag.op=bw&fakt_foretag=monta
&kundkod.op=bw&kundkod=123
&-lop=or&-max&-skip=0&-find
FMS returns error 401 due to the double -lop parameters. Removing the
first -lop=and makes it work properly.


This also makes compound queries not work at all with FMS13 (possibly
also FMS12).
Compound queries are used when an -or or -not operator is specified in
the inline. These operators are the equivalent to creating a new
search record in FileMaker for a more advanced search query.
Compound queries break completely when the default -lop=and operator
is present in the request sent to FMS.

Example request
/fmi/xml/FMPXMLRESULT.xml?-db=mydatabase
&-lay=Kunder&-lop=and
&-q1=fakt_foretag&-q1.value=monta
&-q2=kundkod&-q2.value=123
&-max&-skip=0&-findquery=&-query=(q1);(q2)

FMS returns error 4 "Command is unknown" for this request. Removing
the default -lop operator makes it work.


And finally, I've come across at least two cases where a field
strangely contains an ascii 11 character (vertical tab), probably
pasted somehow by the user. This character normally appears as line
break character inside field values in text exports from FileMaker,
but shouldn't appear in these circumstances. FMS doesn't encode this
properly in the XML result, which makes the XML invalid and Lasso
can't parse it, which results in an error in the inline.


Since I don't expect the FMSA connector for Lasso 8.6 to be updated,
I'm working on a simple proxy for FMSA datasources that will clean up
the request so there are no -lop operators that shouldn't be there,
and clean up the result so no ascii 11 characters are returned to
Lasso. I'll follow up when this is finished.

--
Mvh
Johan Sölve
____________________________________
Montania System AB
Halmstad Stockholm
http://www.montania.se

Johan Sölve
Mobil +46 709-51 55 70
johan@montania.se

Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
Telefon +46 35-136800 | Fax +46 35-136801

#############################################################

This message is sent to you because you are subscribed to
the mailing list Lasso Lasso@lists.lassosoft.com
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>