Delta Import not running when AD trigger scoped to a sub OU

[kcrosby]

If the AD trigger Base DN is set to a sub OU (OU=MyOrgUnit,DC=company,DC=com) and the partition in the MA doesn't match (DC=company,DC=com), the import request gets dropped with a "no matching run profile could be found in the management aget partition OU=MyOrgUnit,DC=company,DC=com".

Using version 1.2.6995.24206

[kcrosby]

2019-04-19 10:42:43.0139| WARN|Could not map run profile DeltaImport for partition OU=ENT__MIM__Dev,OU=DoNotTouch,OU=Test__ENT,DC=domain,DC=company,DC=com because the partition was not found
2019-04-19 10:42:43.0139| INFO|AD: Dropping DeltaImport request from 'AD/LDS change detection (OU=ENT__MIM__Dev,OU=DoNotTouch,OU=Test__ENT,DC=domain,DC=company,DC=com)' as no matching run profile could be found in the management agent partition OU=ENT__MIM__Dev,OU=DoNotTouch,OU=Test__ENT,DC=domain,DC=company,DC=com

The partition in the MA is DC=domain,DC=company,DC=com

[Identitry]

Hi Ryan!
I've installed the latest version today hoping this issue had been solved but unfortunately I get the "No matching run profile could be found..." when specifying a sub OU and that's a petty because I have approx. 3500 users I sync from an AD with ~650.000 accounts so that means I'm unable to use the AD/LDS trigger.
I really hope you'll be able to fix this soon!!!

[ryannewington]

Hi guys,

sorry this one slipped through the cracks. I have a workaround for you.

If you stop the autosync service, and open the config.xml file for editing, you can actually specify a specific run profile to associate with the trigger. This is just not available in the UI.

Locate the management agent and trigger in question, and look for the run-profile-name element.

Replace the element as follows, replacing DI with your own delta import run profile name <run-profile-name>DI</run-profile-name>

Let me know if that solves the problem for you.

Ryan

[Identitry]

Thanks Ryan, that worked fine!
//Henrik