auto fill keyword set

[George_Tarasi]

We have two auto fill keyword sets that only have one different keyword.   They have the same primary keyword, the one that kicks off the auto fill lookup.

When indexing in the thick client, One auto fill works, the other does not.  For the same primary number (member number).

[Brendan_O_Brien]

Do you have these both set up as keyword-level sets? Or are you tying one to the document? I just went through trying to configure multiple AFKSs for a single document - having an AFKS selected at the document type level prevented any keyword-level AFKS from functioning. I ended up needing to remove any document-level AFKS and to set both AFKSs at the keyword level, and both can now be triggered in indexing.

...of course, this means that AFKS importer can no longer update documents when the set changes - that seems to only work when the AFKS is tied at the doc type level...which seems a massive oversight.