I have a source for which I have updated the manager correlation and have not been able to get the new correlation to take effect. I have tried the following steps:
Ensured the “Manager Correlation” on the source matches what is required
Ensured the “Manager Name (manager)” identity profile mapping is set to the authoritative account attribute matching the correlation config with no transform
Ensured that I have a direct match of manager identity value to account attribute for the direct report
Tried both “string” and “long” for the attribute type in the schema
Ran multiple unoptimized aggregations
Ran multiple identity refreshes
Nothing short of resetting the source seems to be working and that will not be an option as this is a live production source. Any help is appreciated.
We ran into a similar issue once before that led to us opening a support ticket. We eventually discovered that for some sources, a “default” manager correlation rule gets applied when the source is created called “Cloud Correlate Manager by AccountId”. We were advised by support to try removing this rule to see if that resolves the issue and it worked for our case. I’m not sure if this is the same issue, but if you don’t already have a custom rule, check to see if this rule is attached to your source and try removing it if it is attached (just set the managerCorrelationRule to null).
Nice to run into you here as well! Thanks a bunch, this solution worked. I speculate that it was because this was an Active Directory source, therefore a default rule was attempting to use the native manager relationship rather than the attribute we wanted.