REST query on text property value with percent character results in web service internal server error

I have found a tracker item about this (133664).  It appears that there is some "special" encoding needed for some characters:

"_":        = "_u"
"%":      = "_p"
"*":       = "_a"
".":        = "_s"
"\'":       = "_q"

This has never made it to the documentation so I will look to sort that ASAP.

So it looks like your query should be "/REST/Objects.aspx?o=101&p1240=WIA+AANVULLING+20_p25".  Are you able to try that and let me know how it goes?

Regards,

Craig.

I just wanted to clarify: the logic is actually to URI-encode first, and then convert the characters above (hence "%" becomes "%25" first, then "_p25").

This is what the M-Files webclient does as well. Unfortunately

/REST/Objects.aspx?o=101&p1240=WIA+AANVULLING+20_p25

does not return a result (while one is expected)

And how would a '.' needed to be encoded in the REST request?

When the search string is "0030.1739", what would the encoded REST request be?

this?   /REST/Objects.aspx?o=101&p1240=0030_s1739

> NOPE, I just tested and the REST request is  /REST/Objects.aspx?o=101&p1240=0030.1739 and returns the one expected result.

And how would a '.' needed to be encoded in the REST request?

When the search string is "0030.1739", what would the encoded REST request be?

this?   /REST/Objects.aspx?o=101&p1240=0030_s1739

> NOPE, I just tested and the REST request is  /REST/Objects.aspx?o=101&p1240=0030.1739 and returns the one expected result.