Hello,

I have a strange issue with making a query in a loopback driver.

Situation:
A job issues a trigger document on an ou, which I pick up and start doing
stuff on. I go out and query for all userobjects that matches a value and
I get really interesting results. The policy looks like this:

<do-set-local-variable name="toBeWarned" scope="policy">
<arg-node-set>
<token-query class-name="shbSHBMAINAccountStd" datastore="src">
<arg-match-attr name="shbLoginExpiresClearText">
<arg-value type="string">
<token-local-variable name="warningtime1inYYYY-MM-DD"/>
</arg-value>
</arg-match-attr>
<arg-string>
<token-attr name="shbLoginExpiresClearText"/>
</arg-string>
<arg-string>
<token-attr name="Internet EMail Address"/>
</arg-string>
<arg-string>
<token-attr name="Language"/>
</arg-string>
</token-query>
</arg-node-set>
</do-set-local-variable>

The query doc in the log looks like:

<input>
<query class-name="shbSHBMAINAccountStd" scope="subtree">
<search-class class-name="shbSHBMAINAccountStd"/>
<search-attr attr-name="shbLoginExpiresClearText">
<value type="string">2007-09-11</value>
</search-attr>
<read-attr/>
</query>
</input>

Note that there are no "read-attr" in the log. Before this query doc are
submitted the engine does a bunch of queries by itself against the OU for
those attributes that I want to be returned from the matching object.

Most likely I'm doing stuff completely wrong here - please advice :-)

br
/anders