Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sync engine attribute flow aggregated #9

Closed
elling opened this issue Jun 8, 2017 · 2 comments
Closed

Sync engine attribute flow aggregated #9

elling opened this issue Jun 8, 2017 · 2 comments

Comments

@elling
Copy link

elling commented Jun 8, 2017

We have a setup with 14 separate import sync rules for Active Directory, all importing users with the same attribute flows (mostly), separated on OU filtering.

In the report, all the fields that are common between the 14 import sync rules appears 14 times PER rule, so I get 196 listings of AccountName, Email and so on.

Title is imported in 13 of the rules, and gives me 169 listings.. and so on and so on 👎

The sync rules have inbound system scoping filter on DN.

connectedSystemScope,"dnENDSWITHOU=Users,OU=_DK,DC=testlab,DC=local",FIM Service,string,16.11.2015 12:34:22
@NileshGhodekar
Copy link
Contributor

Thanks! We'll display the rule scope when documenting the attribute flows for sync engine. You'll still get as many rows though.

NileshGhodekar added a commit that referenced this issue Jun 10, 2017
@NileshGhodekar
Issue #9 - Print scoping information for Inbound Sync Rules. Fix for …
2ea04f9 
…import flows getting duplicated when scoped rules are defined.

Fix - Unlike classic projection rules, sync rules allow you to create multiple project rules for a data source object type.
Fix - Query Resources Expressions messing up with Value Expressions configuration.
Fix - Inbound Scoping Filter configuration  getting printed in Outbound Scoping Filter section.
@NileshGhodekar
Copy link
Contributor

Try the latest release v1.17.0610.0. Closing for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elling @NileshGhodekar