Issue Summary

Different order of IQL subclauses in Import object type mapping affects synced results.

If we have 2 IQL subclauses linked by "OR" and one of these is looking objects having inbound / outbound references (inR / outR), the actual result will depend on how we order the subclauses.

Steps to Reproduce

1. Make an LDAP import definition
2. Create an object type mapping
3. For one object attribute, use IQL object type mapping that is connected with "OR" keyword, and in the subclause coming after "OR", use inbound / outbound reference check. Example:

    DN IN (${member${0}}) OR object having inR(DN IN (${member${0}}))
   

4. Synchronize the import

Expected Results

The object type mapping will be fully considered and both subclauses will be affecting the synced results.

Actual Results

Only the first subclause before "OR" will be considered, the second one where inbound / outbound reference is being used, will be ignored. This will result in a partially imported data.

Workaround

Put the second subclause (inbound / outbound reference IQL) on the first place (i.e. switch the order of subclauses):

object having inR(DN IN (${member${0}})) OR DN IN (${member${0}})