Anyone knows how the notes driver decides on which published attributes it puts association-ref xml attribute values? I amsync'ing a domino address book and do not get association-ref values for a field (AddressOwner) that is flagged NAMES in the DB and contains a resolvable DN, actually exactly the same value as it is resolved to an association-ref in the Members attribute:

<modify class-name="Group" event-id="8E8D5F3CE10E13A2C12575E600502F68 - 1249650139507" src-dn="\MC-MDS-Disponenten">
<association state="associated">8E8D5F3CE10E13A2C12575E600502F6 8</association>
<modify-attr attr-name="ListDescription">
<remove-all-values/>
<add-value>
<value>In dieser Gruppe sind alle MDS (Mitarbeiter-Dispositions-System) Benutzer enthalten, die eine Disponenten Funktion wahrnehmen. </value>
</add-value>
</modify-attr>
<modify-attr attr-name="Members">
<remove-all-values/>
<add-value>
<value association-ref="9AFD6DC5C8162562C125732B0037B3E7" type="dn">CN=Lothar Haeger/O=mummert/C=de</value>
<value association-ref="CF539FD457F13B82C125708B0027F389" type="dn">Stefan Dravon</value>
<value>abronk</value>
</add-value>
</modify-attr>
<modify-attr attr-name="AddressOwner">
<remove-all-values/>
<add-value>
<value>CN=Lothar Haeger/O=mummert/C=de</value>
</add-value>
</modify-attr>
</modify>

Alos note that the value "abronk" is not resolved, even though it maps to a secondary, nevertheless unique and resolvable notes name (even the sametime status icon next to it reflects the user's current status when viewing the document in a notes client)

So what are the exact rules on which fields and DN values get resolved and which not? Is that configurable somewhere?

Cheers, Lothar
--