Attribute synchronization keeps account data on a source in sync with identity data in Identity Security Cloud. It uses identity information to ensure data is consistent across multiple systems in your enterprise.
Hi Team,
We are not seeing below option. I believe this has been removed now in UI. Could you please check and correct the doc?
Hi Theja! Thank you for your input. We’ve created a Jira issue (SAASDOCS-8900) to look into this issue. We’ll update the comment thread when it’s been addressed. Thank you!
Hi @JackSparrow! Thanks for pointing this out. The documentation has been updated to note that attribute sync percentage calculation is only available for organizations that have licensed SailPoint application onboarding.
[1] At the end of the page it states…
" In the Unsynced Accounts tab, you can see a list of the accounts where the values of this attribute pair are synchronized."
… I assume this should read "un-"synchronized ?
[2] Also I find that this list of unsynchronized accounts seems to show false positives, at least for our AD source.
[a] I can pick a sample row and look at the account and identity attributes directly, and in many cases the values actually do match. Perhaps the comparison is against older cashed data which gives false mismatches ?
[b] Question: What determines which sample data is included in the “Unsynced Accounts” list ? It seems to change each time the 'Calculate Sychronization" is performed even when there has not been a change to any underlying records. Is it intended to be complete or just a small sample ?
Hi @reklawttocs! Thanks for catching that - you’re correct it should say “unsynchronized” or “out of sync.” I’ve created SAASDOCS-9029 to fix that statement.
I’m also going to check with our PM and engineering teams on the behavior you’re seeing. We’ll update this thread when they’ve finished that review.
Have a great weekend!
I will second the false positives claim - seeing exactly the same behavior with SaaS Web Services connector. All my spot checks showed that the data is already synced. Which makes me question the accuracy of synchronization percentages to begin with. I suspect there is some caching going on as well that is not getting accounted for properly. I’ve also tried running an unoptimized aggregation on the source, and that did not solve the issue - keeps showing exact same percentages on each recalculation even though data is changing.
Hi @Rockmus and @reklawttocs - I spoke with our engineering and PM teams and they shared that this behavior is due to how we store and return data.
I’ve updated the docs with the following note:
The Attribute Sync calculation capability utilizes a pseudo data lake to help users compute and visualize calculations efficiently. The data within this lake is a subset of what the full system contains, ensuring quick calculation previews. However, it’s important to note that these calculations are based on the data in the lake, which might not always be synchronized with the system’s actual data. The synchronization process between the two systems typically takes between 3 to 6 hours.
If there are additional questions about the feature, I can create a topic in ISC Discussion and Questions - SailPoint Developer Community to continue the conversation.
Thank you for the clarification.
Thank for the info. Good clarification to put in the documentation.
@Rockmus @reklawttocs I appreciate y’all’s help in improving our docs! 
